The Civic MCP Gateway connects AI agents to tools and data while providing identity verification, scoped permissions, audit trails, and revocable access. It ensures that AI agents cannot bypass restrictions when accessing MCP tools.
From the registry: Identity, authorization, audit trails, and revocable permissions for AI agents accessing MCP tools.
Please install the `mcp-gateway-civicteam` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Civic bearer token** — Sign in at app.civic.com and generate a bearer token from the onboarding flow. (https://app.civic.com)
Canonical MCP server config (HTTP transport):
- url: `https://app.civic.com/hub/mcp`
- headers:
- `Authorization`: `Bearer <your-civic-token>`
Note: Civic MCP Gateway — identity/permission layer for MCP tools. Hosted at app.civic.com/hub/mcp. Optional ?profile=your-toolkit scoping. Some clients (Windsurf, Claude Desktop) handle OAuth automatically.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CIVIC_TOKENrequiredBearer token for authenticating agents with the Civic MCP Gateway.Dead code, security, secrets detection and code quality for Python, TypeScript, Go.