mathpix-mcp

A Model Context Protocol server for Mathpix OCR, over stdio or Streamable HTTP (bearer-token auth). It exposes Mathpix conversion as MCP tools so an LLM/agent can turn images and PDF/DOCX/PPTX documents into LaTeX and Markdown.

OCR results (LaTeX/text/MathML/etc.) are always written to files rather than returned inline; tools return a file path, a short preview, and metadata. The destination follows the tool's output_path/output_dir argument, else MATHPIX_OUTPUT_DIR, else the system temp dir.

• Ruby >= 3.2 (CI runs 3.3 and 3.4)
• Mathpix API credentials (MATHPIX_APP_ID, MATHPIX_APP_KEY)

From RubyGems (provides the mathpix-mcp / mathpix-mcp-http executables):

gem install mathpix-mcp

Or straight from GitHub (in a Gemfile):

gem 'mathpix-mcp', git: 'https://github.com/georgedouzas/mathpix-mcp'

Or build locally from a clone:

gem build mathpix-mcp.gemspec
gem install ./mathpix-mcp-*.gem

Or run from a clone with Bundler:

bundle install
cp .env.example .env                 # add your MATHPIX_APP_ID / MATHPIX_APP_KEY

All configuration is via environment variables (loaded from .env when launched from the project directory, or from the process environment). Copy .env.example to .env as a starting point.

mathpix-mcp            # if installed as a gem
# or
bundle exec mathpix-mcp

It speaks MCP over stdio. Credentials are read from .env (when launched from the project directory) or the process environment.

The HTTP transport requires a bearer token (MATHPIX_MCP_TOKEN) — every request must send Authorization: Bearer <token>. It binds to 127.0.0.1:3000 by default (MATHPIX_MCP_HOST / MATHPIX_MCP_PORT).

export MATHPIX_MCP_TOKEN=$(openssl rand -hex 32)
mathpix-mcp-http                 # if installed as a gem
# or
bundle exec mathpix-mcp-http
# or, with a Rack server of your choice:
bundle exec puma config.ru -b tcp://127.0.0.1:3000

Example request:

curl -s http://127.0.0.1:3000/ \
  -H "Authorization: Bearer $MATHPIX_MCP_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Don't expose it on a public interface without a TLS-terminating reverse proxy.

This server speaks MCP over stdio (mathpix-mcp) and Streamable HTTP (mathpix-mcp-http, bearer-token auth). Replace credentials with your own and prefer a real secret for MATHPIX_MCP_TOKEN (e.g. openssl rand -hex 32). Config schemas vary slightly between client versions — check your client's docs if a key is rejected. Examples assume the gem is installed (mathpix-mcp on PATH); to run from a clone, use bundle as the command with args: ["exec", "mathpix-mcp"] and set BUNDLE_GEMFILE to the project's Gemfile.

stdio — keep secrets in the project .env and let the launcher cd in:

claude mcp add mathpix -- \
  bash -lc 'cd /path/to/mathpix-mcp && exec bundle exec mathpix-mcp'

or, if installed as a gem, pass creds inline:

claude mcp add mathpix -e MATHPIX_APP_ID=... -e MATHPIX_APP_KEY=... -- mathpix-mcp

HTTP — point at a running mathpix-mcp-http:

claude mcp add --transport http mathpix http://127.0.0.1:3000/ \
  --header "Authorization: Bearer $MATHPIX_MCP_TOKEN"

List/verify: claude mcp list.

Edit the config file (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "mathpix": {
      "command": "mathpix-mcp",
      "env": { "MATHPIX_APP_ID": "your_app_id", "MATHPIX_APP_KEY": "your_app_key" }
    }
  }
}

Claude Desktop talks to local servers over stdio, so for HTTP bridge with mcp-remote:

{
  "mcpServers": {
    "mathpix": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://127.0.0.1:3000/",
               "--header", "Authorization: Bearer YOUR_TOKEN"]
    }
  }
}

Restart Claude Desktop after editing.

Edit ~/.codex/config.toml:

[mcp_servers.mathpix]
command = "mathpix-mcp"
env = { MATHPIX_APP_ID = "your_app_id", MATHPIX_APP_KEY = "your_app_key" }

For HTTP, bridge with mcp-remote:

[mcp_servers.mathpix]
command = "npx"
args = ["-y", "mcp-remote", "http://127.0.0.1:3000/", "--header", "Authorization: Bearer YOUR_TOKEN"]

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "mathpix": {
      "command": "mathpix-mcp",
      "env": { "MATHPIX_APP_ID": "your_app_id", "MATHPIX_APP_KEY": "your_app_key" }
    }
  }
}

HTTP (Cursor supports remote URLs with headers):

{
  "mcpServers": {
    "mathpix": {
      "url": "http://127.0.0.1:3000/",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Edit ~/.gemini/settings.json:

{
  "mcpServers": {
    "mathpix": {
      "command": "mathpix-mcp",
      "env": { "MATHPIX_APP_ID": "your_app_id", "MATHPIX_APP_KEY": "your_app_key" }
    }
  }
}

HTTP (Gemini CLI uses httpUrl for Streamable HTTP; url for SSE):

{
  "mcpServers": {
    "mathpix": {
      "httpUrl": "http://127.0.0.1:3000/",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Create .vscode/mcp.json in the workspace (top-level key is servers):

{
  "servers": {
    "mathpix": {
      "type": "stdio",
      "command": "mathpix-mcp",
      "env": { "MATHPIX_APP_ID": "your_app_id", "MATHPIX_APP_KEY": "your_app_key" }
    }
  }
}

HTTP — use "type": "http", "url": "http://127.0.0.1:3000/", and a headers object with the bearer token.

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "mathpix": {
      "command": "mathpix-mcp",
      "env": { "MATHPIX_APP_ID": "your_app_id", "MATHPIX_APP_KEY": "your_app_key" }
    }
  }
}

HTTP uses serverUrl: { "mcpServers": { "mathpix": { "serverUrl": "http://127.0.0.1:3000/" } } }. If your version can't attach the bearer header, use the mcp-remote bridge as the command.

Edit settings.json (Cmd/Ctrl+,) under context_servers:

{
  "context_servers": {
    "mathpix": {
      "command": {
        "path": "mathpix-mcp",
        "args": [],
        "env": { "MATHPIX_APP_ID": "your_app_id", "MATHPIX_APP_KEY": "your_app_key" }
      }
    }
  }
}

Continue (~/.continue/config.yaml):

mcpServers:
  - name: Mathpix
    command: mathpix-mcp
    env:
      MATHPIX_APP_ID: your_app_id
      MATHPIX_APP_KEY: your_app_key

Cline (MCP Servers panel → "Configure MCP Servers" → cline_mcp_settings.json): same mcpServers JSON shape as Cursor.

Goose (~/.config/goose/config.yaml):

extensions:
  mathpix:
    enabled: true
    type: stdio
    cmd: mathpix-mcp
    args: []
    envs:
      MATHPIX_APP_ID: your_app_id
      MATHPIX_APP_KEY: your_app_key

For HTTP, point any MCP-capable SDK at http://<host>:3000/ with an Authorization: Bearer <token> header — e.g. the Anthropic Claude Agent SDK MCP connector, the OpenAI Agents SDK (MCPServerStreamableHttp), or LangChain's MCP adapters. For stdio, spawn mathpix-mcp with MATHPIX_APP_ID / MATHPIX_APP_KEY in its environment.

Most clients use one of two shapes: stdio (command + args + env) or HTTP (a URL field — url/httpUrl/serverUrl, name varies — plus headers). If a stdio-only client can't reach the HTTP server, bridge with mcp-remote:

npx -y mcp-remote http://127.0.0.1:3000/ --header "Authorization: Bearer YOUR_TOKEN"

Production deployment — TLS reverse proxy (Caddy/nginx), systemd, Docker / docker-compose, and the security checklist — is in docs/DEPLOYMENT.md. A Dockerfile is included:

docker build -t mathpix-mcp .
docker run --rm -p 3000:3000 \
  -e MATHPIX_APP_ID=... -e MATHPIX_APP_KEY=... \
  -e MATHPIX_MCP_TOKEN=$(openssl rand -hex 32) mathpix-mcp

• If Mathpix's backend rejects a malformed PDF (e.g. a pdftoppm crash), the tool returns a descriptive error; repairing the PDF first (gs -o fixed.pdf -sDEVICE=pdfwrite in.pdf) usually resolves it.

MIT — see LICENSE.