Skip to main content
Glama
nohikomiso

mcp-server-saxo-openapi

by nohikomiso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-server-saxo-openapi

No user-submitted related servers found.

    Related Servers

    • swagger-api-mcp-server

      NekoTarou
      A
      license
      A
      quality
      C
      maintenance
      Parses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.
      11
      5 npm
      1
      MIT

    • openapi-mcp

      ceski23
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.
      8 npm
      3
      MIT

    • swagger-mcp

      hanzc0106
      A
      license
      A
      quality
      C
      maintenance
      A stdio MCP server that caches Swagger/OpenAPI documents for multiple backend services and provides offline API search, retrieval, and request example generation. It only contacts remote servers when explicitly refreshing the cache.
      11
      9 npm
      MIT

    • swagger-mcp

      emreycolakoglu
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.
      9
      5 npm
      MIT

    • Swagger MCP

      yangyaofei
      A
      license
      Not graded
      quality
      D
      maintenance
      Loads and queries OpenAPI/Swagger documents, providing tools to list APIs, get details, search endpoints, and manage schemas for efficient API exploration.
      4
      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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: endpoint specs, schema specs, workflow guides, and search. There is no overlap in functionality.

    Naming Consistency4/5

    Three tools use 'get_saxo_' prefix while one uses 'search_saxo_'. The pattern is mostly consistent, with a minor deviation.

    Tool Count5/5

    Four tools are well-suited for this niche API documentation server, providing essential operations without unnecessary clutter.

    Completeness4/5

    The set covers endpoint specs, schema details, workflow guidance, and search. A minor gap could be a tool for listing all endpoints, but search largely compensates.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources