Skip to main content
Glama
geoffwhittington

SD Elements MCP Server

Related Servers

Alternatives to SD Elements MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      15 npm
      14
      ISC
    • A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and various API operations including record management.
      14
      126 PyPI
      177
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables real-time communication using Server-Sent Events (SSE), providing standardized model management and resource templating capabilities.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.
      -
    • A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that provides access to MongoDB databases. This server enables LLMs to inspect collection schemas and execute read-only queries.
      8
      230 npm
      282
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A toolkit for building Model Context Protocol servers and clients that provide standardized context for LLMs, allowing applications to expose resources, tools, and prompts through stdio or Streamable HTTP transports.
      64,725,178 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions in the SD Elements domain. The tools are well-organized around entities like applications, projects, countermeasures, business units, and users, with clear CRUD operations that prevent confusion. No overlapping functionality exists that would cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as create_application, list_projects, get_user, and update_countermeasure. This predictable naming convention makes it easy for agents to understand and use the tools without ambiguity or mixed styles.

    Tool Count4/5

    With 19 tools, the count is slightly high but reasonable for a comprehensive SD Elements API server covering multiple entities. It includes core operations for applications, projects, countermeasures, business units, and users, plus utility tools like test_connection and api_request, which justifies the scope without being excessive.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the SD Elements domain, including create, get, update, list, and delete operations for key resources. It also covers authentication (get_current_user), connection testing, and a flexible api_request tool, leaving no obvious gaps for agent workflows.