Skip to main content
Glama
gghez

mcp-gouv-fr

by gghez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-gouv-fr

No user-submitted related servers found.

    Related Servers

    • mcp-datagouv-fr

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the French open-data catalogue data.gouv.fr, enabling dataset search and retrieval, organization lookup, and reuse discovery via natural language queries.
      234 npm
      MIT

    • mcp-service-public

      OneNicolas
      A
      license
      Not graded
      quality
      F
      maintenance
      This MCP server provides access to over 38 French public data sources. It enables queries on legal, fiscal, real estate, educational, and other administrative information.
      6
      MIT

    • Data Gouv MCP Server

      csonigo
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Datagouv APIs, primarily allowing users to search for up-to-date information about companies registered in France.
      11
      -

    • mcp-data-strasbourg

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for accessing Strasbourg Open Data (data.strasbourg.eu). Allows searching datasets, retrieving metadata, and querying records with ODSQL.
      245 npm
      MIT

    • mcp-data-issy

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for querying and exploring Issy-les-Moulineaux open data datasets (city services, mobility, environment) via OpenDataSoft API.
      249 npm
      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.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: datasets, communes, departements, regions, legal units, establishments, and a generic GraphQL access point are all cleanly separated. Search vs. get operations are unambiguous within each domain, and no two tools appear to overlap in purpose.

    Naming Consistency5/5

    Tool names follow a consistent domain_verb_noun pattern: datagouv_search/get, geo_search/get, insee_get, and radiofrance_graphql. snake_case is used uniformly, and the verbs search/get clearly indicate whether a tool lists/filters or fetches a single entity.

    Tool Count4/5

    11 tools is a reasonable, well-scoped count for a public-data server covering datasets, administrative geography, and company records. The radiofrance_graphql tool is a broad catch-all that slightly expands the server's scope, but it is still a single coherent integration point.

    Completeness4/5

    The dataset and geography domains have solid search/get coverage for their core entities, and INSEE identifiers map directly to legal units and establishments. Missing search-by-name for INSEE and some administrative geography depth (e.g., arrondissements) are minor gaps for a read-only public-data server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources