ParseHub.dev (documents to records)

dev.parsehubPublished by parsehub.devOfficial publisherv0.1.0Updated Oct 27, 2026

Turn your CSV, PDF and Word files into searchable records, meeting notes and Q&A. Not parsehub.com.

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Remote ParseHub.dev server that lets an assistant turn CSV, PDF and Word files into searchable records, meeting notes and Q&A.

What you can do
  • Convert CSV, PDF and Word documents into structured, searchable records.
  • Produce meeting notes and question-and-answer content from uploaded files.
  • Make the resulting records searchable for later lookup.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you have CSV, PDF or Word documents that you want an assistant to convert into searchable records, meeting notes or Q&A without building your own extraction pipeline.
Requirements
A remote endpoint at parsehub.dev over streamable HTTP; no local package or runtime is needed. A ParseHub.dev API key starting with mcp_, sent in the X-API-Key header, is required and can be created after signing in.
Before you install
The API key is a secret sent in the X-API-Key header; keep it out of shared logs. Documents you submit are processed by a third-party service, so avoid sending confidential material you cannot share. This is parsehub.dev, not parsehub.com.

Installation

In SourceWeft

  1. Open ParseHub.dev (documents to records) in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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/dev.parsehub%2Fparsehub/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": {
    "parsehub-dev-documents-to-records": {
      "type": "http",
      "url": "https://parsehub.dev/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

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. v0.1.0LatestOct 26, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.