Skip to main content
Glama
FelipeVergaraChico

GovBR-DS MCP

by FelipeVergaraChico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GovBR-DS MCP

No user-submitted related servers found.

    Related Servers

    • Godot MCP Documentation Server

      banned104
      A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with direct access to the complete Godot Engine documentation, including classes, tutorials, and features. It enables developers to retrieve and analyze official documentation through natural language interfaces using the Model Context Protocol.
      2
      MIT

    • MCP Brasil API

      lucianfialho
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to query Brazilian public data such as CEP, CNPJ, DDD, exchange rates, banks, and holidays via the Model Context Protocol.
      12
      MIT

    • PortOne Global MCP Server

      iamport-intl
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and reading of PortOne documentation, including OpenAPI schemas and product guides, through the Model Context Protocol. It allows AI agents to easily access and integrate payment-related technical specifications into their workflows.
      11 npm
      ISC

    • DevDocs MCP

      llmian-space
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol implementation that enables AI-powered access to documentation resources, featuring URI-based navigation, template matching, and structured documentation management.
      9
      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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_components is for discovery, get_component is for retrieving full docs of a known component, and search_docs is for answering arbitrary questions across the documentation. Their usage guidance avoids ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: list_components, get_component, and search_docs. The naming clearly signals the operation being performed, and any plural/singular variation follows conventional API naming.

    Tool Count5/5

    With three tools, the server is lean but well-scoped for its purpose of querying GovBR-DS documentation. Each tool earns its place by covering a distinct access mode: browsing, direct retrieval, and searching.

    Completeness5/5

    For a read-only documentation server, the surface is complete: users can discover available components, fetch complete documentation for a known component, and search for behavioral or accessibility guidance. No obvious dead ends or missing operations exist for the stated domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources