Skip to main content
Glama
ParserBee

parserbee-mcp

Official
by ParserBee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to parserbee-mcp

No user-submitted related servers found.

    Related Servers

    • DocumentPro MCP by documentpro

      DocumentPro MCPofficial

      documentpro
      A
      license
      Not graded
      quality
      D
      maintenance
      Extract structured, schema-typed data from invoices, purchase orders, receipts, and tax forms, and classify documents into custom label sets — via a hosted MCP server. Free tier included.
      MIT

    • Invoice Parser MCP

      knportal
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to extract structured JSON from invoices and receipts in PDF and image formats using Claude Vision. Supports full document parsing, line item extraction, validation, and batch CSV export with API key or cryptocurrency payment options.
      MIT

    • SheetShift

      baby-zack-agent
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables converting PDFs and CSV/spreadsheet files into spreadsheets, extracting bank statement or receipt data into clean CSV, cleaning messy CSV, and generating client-ready reports through an open MCP endpoint.
      -
    • bankstatemently by bankstatemently

      bankstatementlyofficial

      bankstatemently
      A
      license
      A
      quality
      A
      maintenance
      Parse and query bank statements — turn PDF statements into structured transactions, accounts, and balances, with balance-reconciliation checks. A deterministic financial memory for AI agents, served as a hosted streamable-HTTP endpoint (API key or OAuth).
      18
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: listing/getting templates, extracting a document, checking credits, and listing/getting extraction records. The only potentially confusable pair (extract_document vs get_extraction) is clearly separated by the descriptions, which distinguish initiating an extraction from retrieving an existing request.

    Naming Consistency5/5

    All six tools follow a consistent snake_case verb_noun pattern (list_templates, get_template, extract_document, get_credits, list_recent_extractions, get_extraction). Verbs map predictably to actions (list/get/extract).

    Tool Count5/5

    Six tools is well within the ideal 3-15 range and each earns its place: template discovery, extraction, credit check, and extraction history/retrieval. Nothing feels redundant or missing at the count level.

    Completeness4/5

    The core workflow (find template, extract document, check credits, review past extractions) is fully covered. Minor gaps exist—templates are read-only (no create/update/delete), extraction history is capped at the last 10 with no pagination, and there is no retry/cancel for failed extractions—but agents can work around these via the ParserBee UI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources