# How to connect Mathpix to OpenClaw (paste one key, 28 tools) > Connect Mathpix to OpenClaw with ClawLink: paste your Mathpix key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/mathpix The usual route to Mathpix access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Mathpix setup: install one ClawHub skill, connect Mathpix in the browser, and OpenClaw can call real Mathpix actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Mathpix. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Mathpix** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect mathpix # connect Mathpix (browser OAuth) npx -y @useclawlink/cli actions mathpix # list available actions npx -y @useclawlink/cli run mathpix --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Mathpix in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Mathpix API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Mathpix, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Mathpix is connected in the dashboard, that agent calls the same 28 Mathpix tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Mathpix MCP for OpenClaw Looking for a Mathpix MCP server for OpenClaw? ClawLink connects Mathpix to OpenClaw and exposes 28 Mathpix tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Mathpix integration](https://claw-link.dev/hermes/mathpix) works the same way. ## What the OpenClaw Mathpix integration can do 28 Mathpix tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 28. ### 25 of 28 Mathpix tools for OpenClaw | Tool | What it does | |---|---| | **Get app token** `mathpix_get_app_token` | Get expiry and ownership metadata for a specific short-lived Mathpix app token | | **Get conversion result** `mathpix_get_conversion_result` | Wait for an existing Mathpix Markdown conversion and requested format to finish, then return | | **Get document result** `mathpix_get_document_result` | Wait for an existing Mathpix document job and requested format to finish, then return its | | **Get file job** `mathpix_get_file_job` | Get aggregate status, file and page counters, and timestamps for one Files API job | | **Get file result** `mathpix_get_file_result` | Wait for an existing Files API file and selected format to finish, then return its status and | | **Get job file by custom ID** `mathpix_get_job_file_by_custom_id` | Get the complete Files API processing status for one job member using the exact caller-defined | | **Get ocr usage** `mathpix_get_ocr_usage` | Return one page of aggregated Mathpix OCR usage for a date range, optionally grouped by usage | | **List conversions** `mathpix_list_conversions` | List one page of retained Mathpix Markdown conversion records, optionally filtered by date, and | | **List data sources** `mathpix_list_data_sources` | List cloud-storage data sources registered with Mathpix, returning only allowlisted non-secret | | **List documents** `mathpix_list_documents` | List retained document OCR jobs for the connected account, optionally filtered by date or | | **List file job files** `mathpix_list_file_job_files` | List one cursor-paginated page of files in a Mathpix Files API job, optionally filtered by | | **List file jobs** `mathpix_list_file_jobs` | List one cursor-paginated page of Files API jobs newest first, optionally bounded by inclusive | | **Search ocr results** `mathpix_search_ocr_results` | Search retained image and stroke OCR history by date, identifiers, content, tags, or detected | | **Convert mathpix markdown** `mathpix_convert_mathpix_markdown` | Submit Mathpix Markdown, wait for one requested format to finish, then return the conversion ID | | **Create app token** `mathpix_create_app_token` | Mint a short-lived client OCR credential, optionally with a live ink strokes session | | **Get storage onboarding identities** `mathpix_get_storage_onboarding_identities` | Get the Mathpix AWS, Azure, and GCP identities needed to grant cloud-storage access | | **Ocr document** `mathpix_ocr_document` | Submit a PDF, office document, or ebook URL, wait for OCR and the requested conversion to | | **Ocr image** `mathpix_ocr_image` | Extract text, math, tables, diagrams, or chemistry from one image URL or base64 data URI and | | **Recognize strokes** `mathpix_recognize_strokes` | Recognize handwritten math or text from aligned x/y digital-ink stroke arrays and return OCR | | **Finalize file job** `mathpix_finalize_file_job` | Permanently close one Files API job to new file additions and arm its completion webhook | | **Process file uri** `mathpix_process_file_uri` | Submit one public or registered-cloud document URI to the paid Files API, wait for OCR and one | | **Process image batch** `mathpix_process_image_batch` | Submit a paid asynchronous batch of 1-100 named public image URLs, wait until every key has a | | **Revoke app token** `mathpix_revoke_app_token` | Irreversibly revoke one short-lived app token immediately | | **Submit file job** `mathpix_submit_file_job` | Submit 1 to 200,000 remote documents as one paid asynchronous Mathpix Files job | | **Upload and process file** `mathpix_upload_and_process_file` | Upload one local document to the paid Mathpix Files API, wait until OCR and one requested | ## Example prompts **Get App Token** > Pull the relevant data from Mathpix, summarize it in plain English, and point out anything that needs attention. **Get Conversion Result** > Pull the relevant data from Mathpix, summarize it in plain English, and point out anything that needs attention. **Get Document Result** > Pull the relevant data from Mathpix, summarize it in plain English, and point out anything that needs attention. **Get File Job** > Pull the relevant data from Mathpix, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mathpix working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Mathpix API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mathpix account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mathpix. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Mathpix actions to the runtime in a format your agent can reliably use. | 28 tools for Mathpix are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Mathpix to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Mathpix in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the Mathpix key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Mathpix skill but can't call the tools The ClawHub skill teaches OpenClaw about Mathpix, but the calls run through the ClawLink plugin and your connected account. Make sure Mathpix is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Mathpix from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Mathpix tools Mathpix tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Mathpix call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Mathpix returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Mathpix has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Mathpix integration? Yes. ClawLink is the fastest way to connect OpenClaw to Mathpix: link your Mathpix account once in the browser and OpenClaw can call the Mathpix API through 28 ready-made tools — no custom code or token handling. ### How do I add Mathpix to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mathpix skill from ClawHub, then you click Connect in the dashboard to authorize Mathpix. OpenClaw calls the tools from the next message — no config files, and the Mathpix key you paste is stored server-side instead of in your environment. ### How long does it take to connect Mathpix to OpenClaw? About two minutes. Sign in, click Connect next to Mathpix in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Mathpix up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mathpix working from chat. ### OpenClaw installed the Mathpix skill but can't call the tools The ClawHub skill teaches OpenClaw about Mathpix, but the calls run through the ClawLink plugin and your connected account. Make sure Mathpix is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.