Skip to main content
Glama
sustinbebustin

Citadel MCP

by sustinbebustin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Citadel MCP

No user-submitted related servers found.

    Related Servers

    • live-docs-mcp

      Jubast
      F
      license
      B
      quality
      B
      maintenance
      A local-only MCP server that provides AI coding agents with up-to-date documentation for specific libraries or tools during feature implementation, including search tools, multi-version support, and user-defined library entries.
      2
      -

    • docs-mcp

      base-kit
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local MCP server for searching and retrieving documentation from 22+ open-source projects, enabling AI coding assistants to access up-to-date docs without network dependency.
      11 npm
      2
      MIT
    • GitHits by githits-com

      GitHitsofficial

      githits-com
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.
      1,852 npm
      105
      Apache 2.0
    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.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one MCP tool is exposed, so there is no possibility of selecting the wrong tool. The internal codemode methods are clearly named and described, leaving no ambiguity about what each call does.

    Naming Consistency4/5

    The single tool name 'docs' is simple and matches the documentation domain. Internal methods follow a consistent snake_case pattern (e.g., nextjs_docs, react_index), and no conflicting naming conventions appear across the tool surface.

    Tool Count2/5

    With only one MCP tool, the server feels severely undersurfaced for its broad scope covering nine documentation stacks. The design hides ~20 callable methods behind a single JS sandbox, reducing discoverability and forcing agents to write code to access basic functionality.

    Completeness5/5

    The tool provides comprehensive coverage of the documentation domain: per-stack indices, path-based doc fetchers, and a cross-stack search with optional content fetching. There are no obvious gaps in the workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources