Skip to main content
Glama

Related Servers

Alternatives to meridian-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes internal company services as LLM-callable MCP tools, enabling AI agents to perform business operations like customer management, order processing, and support ticketing through natural language.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      7 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Exposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.
      10
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.
      4 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents such as ChatGPT, Claude, and local LLMs to operate an enterprise digital-operations platform through MCP, exposing 19 model tools and 3 app-only tools for identity, data, workflow, files, and PII-controlled operations with role-based permissions and two-phase confirmations.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Sphere is an exchange where AI agents list services and post requests for other agents. Registration is one request, free, with no human approval. The first order is free: sphere_receipt_trial, one per agent per 24 hours, returns a signed receipt you can verify yourself. Contracts with escrow, payouts and signed receipts work; pay-per-call over x402 is paused.
      MIT

    TDQS

    A3.5/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools target distinct resources, but there is notable overlap between update_request_status and advance_step, and between get_workflow_status, list_request_steps, and get_service_request (all expose step/phase data). The descriptions help clarify intent, but an agent could still select the wrong tool for workflow inspection or transition.

    Naming Consistency4/5

    The set mostly follows a clear verb_noun pattern: list_*, get_*, create_*, update_*, verify_*. Minor deviations like meridian_status (no verb) and advance_step (imperative without the request object) break the pattern slightly, but the style is generally predictable.

    Tool Count4/5

    With 16 tools, the server is slightly above the ideal 3-15 range, but the count is justified by the broad domain covering service catalog, requests, workflow state, payments, and meetings. Each tool addresses a meaningful operation, so the size feels reasonable rather than bloated.

    Completeness4/5

    The tool surface covers the main service request lifecycle: listing services, creating requests, advancing workflow, checking payments, and managing meetings. Minor gaps exist such as no dedicated cancel/delete operation, no way to update service request answers, and limited meeting management beyond RSVP, but agents can work around these with existing tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues