Skip to main content
Glama

Related Servers

Alternatives to OnePlatform MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search public documentation, retrieve SDK snippets with verification status, and access published pricing and an llms.txt resource in a read-only, credential-free way.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents and chat clients to inspect proxy tokens, usage, pools, geo targeting, and build ready-to-use proxy connection URLs via the Litport account API, while remaining read-only.
      374 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables a coding agent to get short, token-efficient answers about a project through grouped searches, focused symbol or section reads, and bounded read-only script output, with safety limits on paths, secrets, commands, and response size.
      3
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Gives coding agents read-only access to an AI-SPM backend's flagged issues, inventory, and remediation guidance so they can fix the affected code, along with guardrail policies, LLM-interaction analytics, cost-optimization analyses, and red-teaming evaluation results.
      37
      17 PyPI
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to explore org-wide context across domains, repositories, and data sources; read and participate in GitHub Discussions; and run read-only SQL queries over public GCS parquet datasets.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, outline, read, and patch living documentation sections across multiple linked repos, check drift status, review recent changes, and query a cross-repo code graph. Writes respect per-user API key permissions and configurable trust modes, keeping shared docs in sync with code.
      214,897 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools occupy clearly separate niches: free-text documentation search, direct documentation page retrieval by path/URL, and exact API operation contract lookup by operationId. Search vs. fetch is a well-understood pair, and the API-reference tool is a distinct resource entirely. No two tools could plausibly be confused for one another.

    Naming Consistency5/5

    All names follow a strict {domain}_{action} snake_case pattern (docs_search, docs_get_page, api_get_operation), with clear domain prefixes distinguishing documentation from API concerns. Verb choice is consistent and readable throughout.

    Tool Count4/5

    Three tools is a tight, purposeful surface with no redundancy, and each covers a genuinely different retrieval need. It sits at the low end of comfortable scope, leaving some room for additional reference operations, but nothing feels padded.

    Completeness3/5

    Documentation search, page fetch, and operation lookup cover the core reference workflow, but there is no way to enumerate or list available API operations, so api_get_operation depends entirely on the caller already knowing an operationId (or the docs surfacing it). No listing/browsing or discovery operation is a notable gap for an API-reference server.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive