io.github.titus-civic/mcp-gateway
Identity, authorization, audit trails, and revocable permissions for AI agents accessing MCP tools.
Open source Repository Open in the app JSON README (API)
About
Identity, authorization, audit trails, and revocable permissions for AI agents accessing MCP tools.
Details
- Kind
- MCP servers
- Topic
- Security & identity
- Publisher
- titus-civic
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 1.0.0
- Last push
- 2026-03-19T23:20:33Z
- Repository state
- ativo
- License
- MIT
- Added
- 2026-08-29 04:01:33
- Updated
- 2026-08-29 04:01:33
- Origin id
io.github.titus-civic/mcp-gateway
README
# Civic MCP Gateway
Connecting AI Agents to tools and data via the Civic MCP Gateway gives builders access to guardrails, scoped permissions, audit trails, and revocable access when calling MCP tools. Civic separates the permission layer from the AI agent so they can't get around restrictions.
This repository contains integration metadata, configuration files, and client examples. The gateway itself runs at **[app.civic.com](https://app.civic.com)**.
---
## What it does
Without an identity layer, any AI agent can call any MCP tool with no record of who authorized it, what it accessed, or how to revoke its access. Civic fixes that:
- **Agent identity** — agents authenticate with a Civic-issued bearer token
- **Scoped permissions** — grant agents access to specific tools only
- **Audit trail** — every tool call is logged with agent identity and timestamp
- **Revocable access** — revoke a token and the agent loses access immediately
- **Guardrails** — rate limits, approval workflows, and deny lists via the configurator
---
## MCP Endpoint
```
https://app.civic.com/hub/mcp
```
**Transport:** Streamable HTTP
**Auth:** Bearer token (generated at [app.civic.com](https://app.civic.com))
---
## Quickstart
### 1. Get a token
Sign in at [app.civic.com](https://app.civic.com) and generate a bearer token from the onboarding flow.
### 2. Configure your MCP client
**Claude Desktop** — native Streamable HTTP:
Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:
```json
{
"mcpServers": {
"civic": {
"url": "https://app.civic.com/hub/mcp"
}
}
}
```
**Claude Code** — native HTTP transport (no bridge needed):
```bash
claude mcp add --transport http civic https://app.civic.com/hub/mcp
```
Or for stdio via Hub Bridge:
```bash
claude mcp add civic "npx @civic/hub-bridge"
```
**Cursor** — native Streamable HTTP:
Add to your Cursor MCP config:
```json
{
"mcpServers": {
"civic": {
"url": "https://app.civic.com/hub/mcp"
}
}
}
```
**Cline** (VS Code) — add to `cline_mcp_settings.json`:
```json
{
"mcpServers": {
"civic": {
"url": "https://app.civic.com/hub/mcp",
"headers": {
"Authorization": "Bearer YOUR_CIVIC_TOKEN"
}
}
}
}
```
**Windsurf** — native Streamable HTTP, no bridge required:
Add to `~/.codeium/windsurf/mcp_config.json`:
```json
{
"mcpServers": {
"civic": {
"serverUrl": "https://app.civic.com/hub/mcp"
}
}
}
```
Windsurf handles OAuth automatically on first connection.
### 3. Optional: lock to a profile
Append `?profile=your-toolkit` to scope the gateway to a specific configuration:
```
https://app.civic.com/hub/mcp?profile=your-toolkit
```
### Automated agents (token-based auth)
For non-interactive agents that can't complete an OAuth flow, generate a bearer token at [app.civic.com](https://app.civic.com) and pass it directly:
```bash
curl -X POST https://app.civic.com/hub/mcp \
-H "Authorization: Bearer $CIVIC_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
```
---
## Install from a registry
| Registry | Link |
|---|---|
| Smithery | [smithery.ai/servers/@civic/civic-mcp-gateway](https://smithery.ai/servers/@civic/civic-mcp-gateway) |
| ClawHub | [clawhub.ai/civictechuser/openclaw-civic-skill](https://clawhub.ai/civictechuser/openclaw-civic-skill) |
## Example use cases
| Use case | What Civic adds |
|---|---|
| [Gmail guardrails & audit](examples/use-cases/gmail-guardrails.md) | Block outbound sends with secrets, redact PII from email content, log every send |
| [Google Calendar guardrails & audit](examples/use-cases/google-calendar-guardrails.md) | Prevent event deletion, restrict to business hours, block external attendees |
| [PostgreSQL guardrails & audit](examples/use-cases/postgresql-guardrails.md) | Block destructive queries, enforce read-only access, redact sensitive columns |
## Documentation
Full documentation at **[docs.civic.com](https://docs.civic.com/civic/quickstart)**
---
## Working example
See [civicteam/nexus-demo](https://github.com/civicteam/nexus-demo) for a full client integration using Next.js, federated auth, and MCP tool visualization.
---
## License
MIT