govera-mcp-server

Official Model Context Protocol (MCP) server for Govera, the governance platform for public agencies. It exposes Govera's public, read-only, zero-auth product API as four AI-callable tools over stdio, so any MCP client (Claude Desktop, Claude Code, and other MCP-compatible agents) can look up Govera's status, product metadata, capabilities, and guides.

This server contains no agency, tenant, or user data — it only surfaces static, public information.

Install / run

No installation step is required. Any MCP client that can launch a stdio subprocess can run this server directly via npx:

npx -y govera-mcp-server

The server communicates over stdio using the MCP protocol; it is not meant to be run interactively from a terminal.

Claude Desktop / MCP client configuration

Add this to your MCP client's server configuration (for Claude Desktop, claude_desktop_config.json):

{
  "mcpServers": {
    "govera": {
      "command": "npx",
      "args": ["-y", "govera-mcp-server"]
    }
  }
}

Tools

| Tool | Description | |---|---| | get_status | Get the operational status, version, and current timestamp of the Govera Public API. | | get_product | Get public metadata about Govera: name, description, the categories of public agency it serves, and its home URL. | | list_capabilities | List Govera's product capabilities, each with a stable id, name, and description. | | list_guides | List the public Govera platform guides, each with a title and URL. |

None of the tools take any input — every inputSchema is {"type":"object","properties":{},"additionalProperties":false}. Each tool call performs a single unauthenticated GET against the Govera public API and returns the JSON response as MCP text content. A network error, non-2xx HTTP status, or invalid JSON body produces an MCP error result (isError: true) with a descriptive message instead of throwing.

Configuration

| Env var | Default | Purpose | |---|---|---| | GOVERA_API_BASE | https://www.govera.co/api/v1 | Override the base URL the server calls. Useful for pointing the server at a local or staging deployment during development. |

Public manifest and API docs

• MCP manifest: https://www.govera.co/.well-known/mcp.json
• Developer docs: https://www.govera.co/developers

Development

npm install
npm test

The tool logic lives in src/tools.js as plain, dependency-free async functions (one per tool) plus a TOOLS registry consumed by the server wiring in src/index.js. src/tools.js has no dependency on the MCP SDK, so tests/tools.test.js exercises it directly with a mocked global.fetch. src/index.js wires the same TOOLS registry into an MCP Server over StdioServerTransport.

License

MIT