Invoice & Receipt OCR Extractor to Excel

com.ranovamPublished by ranovam.comv0.1.1Updated Oct 27, 2026

Invoice and receipt extractor: reads PDF and image invoices/receipts with AI, pulling date…

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that uses AI to read PDF and image invoices and receipts and extract their fields, such as dates.

What you can do
  • Extract structured fields from invoice and receipt files
  • Process PDF and image documents with AI-based OCR
  • Pull details such as dates and other invoice data for downstream use
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when an assistant needs to turn scanned or PDF invoices and receipts into structured data, for example to feed bookkeeping, expense tracking or spreadsheet workflows.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: an Apify API token sent as an Authorization bearer header, or OAuth if the MCP client supports it. An Apify account is implied.
Before you install
The server requires an Apify API token, which is a billable account credential; keep it secret and expect Apify usage charges. Uploaded invoices and receipts are sent to a third-party service for processing, so avoid sensitive financial documents unless that is acceptable.

Installation

In SourceWeft

  1. Open Invoice & Receipt OCR Extractor to Excel in the dashboard and add it to a workspace.
  2. Connect the required 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/com.ranovam%2Finvoice-to-excel/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "invoice-receipt-ocr-extractor-to-excel": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=enezli/invoice-to-excel"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.1LatestSep 28, 2026
  2. v0.1Sep 16, 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.