
Wraps the OCR.space API to extract text from images and PDFs directly in your MCP client. The source documentation is light on tool specifics, but this is a straightforward gateway to OCR.space's optical character recognition service through Pipeworx's hosted MCP infrastructure. You can either add this individual server or connect to the full Pipeworx gateway for access to 748+ data sources. Includes an ask_pipeworx tool that lets you make plain English queries instead of calling structured APIs directly. Useful when you need to pull text from screenshots, scanned documents, or PDFs without leaving your AI workflow.
OCR.space MCP — wraps the OCR.space API (ocr.space) for image/PDF → text OCR.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
extract_text | Extract text from an image or PDF via OCR — pass an image/PDF URL, get the recognized text. Useful for reading screenshots, scanned documents, receipts, signs. Engine 2 is best for most cases. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ocrspace": {
"url": "https://gateway.pipeworx.io/ocrspace/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/ocrspace/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Ocrspace data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/extract_text \
-H 'Content-Type: application/json' \
-d '{"image_url":"https://example.com/receipt.jpg"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/extract_text. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.