Parsedoc

fr.custom-digital-servicesPublished by custom-digital-services.frOfficial publisherv1.0.0Updated Oct 25, 2026

Agent-native document parsing: PDF, scans and FR/EU invoices to structured JSON or Markdown.

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Parsedoc is a remote MCP server that turns PDFs, scans and French/EU invoices into structured JSON or Markdown for an assistant.

What you can do
Parse PDF documents into structured JSON or Markdown output for an assistant to work with. Convert scanned documents through the same parsing flow. Extract French and EU invoice content into structured data. Access is authenticated per request with a bearer API key.
When to use it
Useful when an assistant needs to read PDFs, scanned paperwork or French/EU invoices and get back structured JSON or Markdown instead of raw text.
Requirements
Remote streamable HTTP endpoint; no local install. Requires an OAuth bearer API key sent in the Authorization header, obtained from the signup endpoint; the free tier covers 100 parse pages per month.
Before you install
The API key is a secret sent in the Authorization header, so keep it out of shared logs. Documents are uploaded to a third-party service for parsing, so avoid sending confidential or regulated content unless that is acceptable. Usage beyond the free monthly page allowance may involve payment.

Installation

In SourceWeft

  1. Open Parsedoc 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/fr.custom-digital-services%2Fparsedoc/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": {
    "parsedoc": {
      "type": "http",
      "url": "https://parsedoc.custom-digital-services.fr/api/mcp"
    }
  }
}

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

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.

Other Custom-Digital-Services integrations