Skip to main content
Glama
h0ck3ystyx

Synergy/DE MCP Server

by h0ck3ystyx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Synergy/DE MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Knowledge Assistant

      channico
      F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI clients to search a knowledge base and retrieve complete source documents via narrow search and fetch tools.
      2
      -

    • docs-mcp

      artemartemov
      A
      license
      Not graded
      quality
      D
      maintenance
      A secure MCP server providing intelligent documentation search across multiple frameworks using ChromaDB vector storage, enabling semantic search and integration with AI tools.
      MIT

    • Shelby docs MCP

      Jr-kenny
      A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server that provides searchable access to the Shelby documentation bundle for MCP-compatible clients. It enables users to search, list, and read documentation pages directly within AI tools and IDEs.
      4
      MIT

    • File AI

      flyfish-dev
      A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server that provides document awareness for agents by parsing local files into structured profiles, blocks, chunks, and search results, enabling agents to understand and cite document content without dealing with raw file formats.
      5
      24 npm
      3
      Apache 2.0
    • doc-search by SodaShikenn

      doc-searchofficial

      SodaShikenn
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for hybrid documentation search (keyword + vector) and RAG chat, enabling natural language queries with cited answers from indexed repositories.
      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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: describe_docs for metadata, get_related_topics for topic relationships, get_topic for fetching specific content, list_section_topics for section overviews, and search_docs for full-text search. An agent can easily distinguish between them based on their names and descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case: describe_docs, get_related_topics, get_topic, list_section_topics, and search_docs. The verbs (describe, get, list, search) are appropriate and predictable, making the set easy to navigate and understand.

    Tool Count5/5

    With 5 tools, the server is well-scoped for documentation access, covering metadata retrieval, topic fetching, section listing, relationship discovery, and search. Each tool earns its place without redundancy, aligning with typical MCP server sizes of 3-15 tools for focused domains.

    Completeness5/5

    The tool set provides complete coverage for documentation interaction: describe_docs for overview, list_section_topics and search_docs for discovery, get_topic for content retrieval, and get_related_topics for navigation. There are no obvious gaps, enabling agents to perform full documentation workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources