Skip to main content
Glama
rossumai

Rossum MCP Server

Official
by rossumai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Rossum MCP Server

No user-submitted related servers found.

    Related Servers

    • Productive Simple MCP

      druellan
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for accessing Productive.io API endpoints (projects, tasks, comments, todos), tailored for read-only operations, providing streamlined access to essential data while minimizing token consumption
      18
      MIT

    • Airflow MCP

      zamax14
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that exposes Apache Airflow's REST API to AI agents, enabling them to inspect and operate on DAGs, DAG runs, task instances, and logs.
      9
      2
      MIT

    • Schwab MCP

      JackGuan99
      A
      license
      A
      quality
      C
      maintenance
      A read-only Model Context Protocol server that lets AI agents query brokerage account holdings, balances, real-time quotes, price history, options chains, orders, and transactions, with account masking and LLM-friendly output.
      14
      MIT

    • Swagger/OpenAPI MCP Server

      gulbaki
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.
      4
      20 npm
      14
      ISC

    • MCP OpenAPI Server

      ReAPI-com
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that loads multiple OpenAPI specifications and exposes them to LLM-powered IDE integrations, enabling AI to understand and work with your APIs directly in development tools like Cursor.
      7
      37 npm
      90
      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

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different Rossum resources: hooks, queues, schemas, and workspaces. The singular vs. plural naming (e.g., get_hook vs. get_hooks) further clarifies whether the tool retrieves a specific item or all items, eliminating any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent 'rossum_get_' prefix with snake_case, followed by the resource name (e.g., hook, hooks, queues, schema, workspace, workspaces). This predictable pattern makes it easy to understand what each tool does at a glance.

    Tool Count4/5

    With 6 tools, the count is reasonable for a Rossum API server, covering key resources like hooks, queues, schemas, and workspaces. It's slightly lean but functional; adding a few more tools (e.g., for creating or updating resources) could enhance completeness without being excessive.

    Completeness2/5

    The toolset is severely incomplete as it only provides read operations (get) for resources. There are no tools for creating, updating, or deleting hooks, queues, schemas, or workspaces, which are essential for full CRUD coverage in a document processing platform like Rossum. This will cause significant agent failures when trying to modify data.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources