Docspeed

ai.docspeedPublished by docspeed.aiOfficial publisherv0.2.0Updated Oct 24, 2026

Extract, ask, compare and parse PDFs/images with source evidence. OAuth sign-in or API keys.

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Docspeed is a remote MCP server that lets an assistant extract, ask about, compare and parse PDFs and images with source evidence.

What you can do
  • Extract content from PDFs and images
  • Ask questions about documents and get answers tied to source evidence
  • Compare documents against each other
  • Parse PDFs and images into structured output
When to use it
Useful when an assistant needs to work through PDFs or scanned images — pulling out content, answering questions grounded in the source, or comparing documents — without building your own extraction pipeline.
Requirements
A remote MCP endpoint at api.docspeed.ai over streamable HTTP. Authentication is required via OAuth sign-in or an API key. No environment variables or headers are declared in the manifest.
Before you install
You must sign in with OAuth or supply an API key, so account credentials are involved. Documents you submit are sent to a third-party service for processing, so avoid confidential material unless that is acceptable.

Installation

In SourceWeft

  1. Open Docspeed 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/ai.docspeed%2Fdocspeed/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": {
    "docspeed": {
      "type": "http",
      "url": "https://api.docspeed.ai/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

2
  1. v0.2.0LatestOct 12, 2026
  2. v0.1.0Oct 11, 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.