Skip to main content
Glama
muhammad1azmi

google-meridian-mcp

by muhammad1azmi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to google-meridian-mcp

No user-submitted related servers found.

    Related Servers

    • Gemini Docs MCP Server

      LeomaiaJr
      F
      license
      A
      quality
      D
      maintenance
      Enables users to search and fetch Google's Gemini API documentation directly within an MCP-compliant environment. It provides structured access to guides and references for features like function calling, embeddings, and text generation.
      2
      -

    • Google Ads MCP Server

      PradeepGontupuli
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs and AI agents to query and explore Google Ads accounts and API resources through MCP tools and resources, including account information, resource metadata, metrics, segments, and release notes.
      3
      Apache 2.0

    • official-docs

      pittzhang20260507
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to query upstream documentation through a single search tool, backed by a bundled sample corpus, Vertex AI Search, or an SSH endpoint, returning cited source passages and refusing when nothing relevant is found.
      1
      Apache 2.0

    • Documentation Fetcher & RAG

      mikkelkrogsholm
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to fetch, index, and perform semantic RAG-based searches on API documentation from various sources. It provides tools for hybrid search and collection management, allowing users to access up-to-date documentation from projects like Gemini and FastMCP.
      -
    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.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Documentation tools (fetch, list, search) are separated by action, guides target different aspects (control points vs workflow), and remaining tools cover calculation, auditing, code synthesis, and schema generation without overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, e.g., fetch_docs, get_control_point_guide, calculate_bayesian_prior, list_doc_sources. The verbs are varied but predictable, and there is no mixing of conventions.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a domain-specific MCP server. It covers documentation, guides, prior calculation, auditing, code synthesis, and schema generation without being overloaded or too sparse.

    Completeness4/5

    The tool surface covers core documentation, guides, prior calculation, and auditing. Minor gaps exist: missing tools for directly running models or retrieving results, but these may be handled by synthesized code. Overall, it's fairly complete for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources