Image to Text OCR

io.github.sumitrmardyPublished by GitHub account sumitrmardyv1.0.0Updated Oct 26, 2026

OCR text from image URLs, 30 languages, lines with boxes. One flat row per image. Billed on text.

VerifiedStreamable HTTPWeb executableData & AnalyticsMedia & Design

Overview

AI-generated overview

Apify-hosted OCR server that lets an assistant extract text from image URLs in 30 languages, returning lines with bounding boxes.

What you can do
  • Extract text from images supplied as URLs, with recognition across 30 languages.
  • Return recognized lines together with their bounding boxes.
  • Deliver results as one flat row per image, suited to batch processing of many images.
When to use it
Useful when an assistant needs to read text out of images it can reference by URL, such as screenshots, scans or photos, and when per-line positions matter for layout-aware work.
Requirements
Remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is needed; authentication uses OAuth sign-in or a bearer Apify API token in the Authorization header. Network access is required.
Before you install
Usage is billed by the amount of text processed, so costs scale with image volume. The Apify API token is a secret sent in the Authorization header. Image URLs are sent to Apify's hosted service for processing.

Installation

In SourceWeft

  1. Open Image to Text OCR in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sumitrmardy%2Fimage-to-text-ocr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "image-to-text-ocr": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=sumitr_mardy/image-to-text-ocr",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.