Skip to main content
Glama
progress-all

ACOMO MCP Server

by progress-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ACOMO MCP Server

No user-submitted related servers found.

    Related Servers

    • Bruno MCP Server

      brianconway
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables API development directly from MCP clients by creating and editing collections, running requests through the real CLI, generating documentation, and starting mock servers.
      52 npm
      MIT

    • yellow-pages

      ethank64
      F
      license
      A
      quality
      D
      maintenance
      Exposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.
      2
      -

    • openapi-mcp-server

      wr5912
      F
      license
      Not graded
      quality
      D
      maintenance
      Dynamically creates MCP tools and resources from OpenAPI specifications, with a React admin panel for managing configurations, monitoring, and invoking resources.
      -

    • api-testing-agent

      SHREELASYABEZAWADA
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.
      1
      -
    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.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: list_apis and list_components provide overviews, describe_api and describe_component give detailed information, api_schemas extracts specific parts, generate_request_template creates templates, call_api executes calls, and health checks server status. The descriptions make it easy to differentiate between listing, describing, extracting, generating, calling, and checking operations.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_apis, describe_api, call_api). The verbs (list, describe, generate, call, health) are clear and appropriately paired with nouns (apis, components, request_template, api), creating a predictable and readable naming convention throughout the set.

    Tool Count5/5

    With 8 tools, this server is well-scoped for its purpose of interacting with an API documentation system (acomo). Each tool serves a specific function in the workflow (listing, describing, extracting, generating, calling, and health checking), and none appear redundant or unnecessary, making the count appropriate for the domain.

    Completeness5/5

    The tool set provides complete coverage for the domain of API documentation exploration and interaction: it allows listing APIs and components, describing them in detail, extracting schemas, generating request templates, calling APIs, and checking server health. There are no obvious gaps, as it supports the full lifecycle from discovery to execution.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources