Structured deliberation for AI agent coordination. Submit positions, vote, get analysis of cruxes, clusters, bridging statements, and consensus —
Connect Gemot to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Structured deliberation for AI agent coordination. Submit positions, vote, get analysis of cruxes, clusters, bridging statements, and consensus — then compromise proposals optimized for cross-cluster endorsement, with a tamper-evident. The gemot mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
deliberation — The deliberation tool exposed by this serverparticipate — The participate tool exposed by this serveranalyze — The analyze tool exposed by this serverdecide — The decide tool exposed by this servercoordinate — The coordinate tool exposed by this serveradmin — The admin tool exposed by this serverPrivacy — All data stays in your Postgres database. The only external call is to the Anthropic API for LLM analysis. No telemetry, no data collection, noPlatform — The Platform tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: ANTHROPIC_API_KEY, DATABASE_URL, GEMOT_API_SECRET, GEMOT_BASE_URL, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Gemot's toolset — deliberation, participate, analyze and 5 more — is a fair guide to whether it matches your workflow. It is maintained by justinstimatze; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| deliberation | The deliberation tool exposed by this server. |
| participate | The participate tool exposed by this server. |
| analyze | The analyze tool exposed by this server. |
| decide | The decide tool exposed by this server. |
| coordinate | The coordinate tool exposed by this server. |
| admin | The admin tool exposed by this server. |
| Privacy | All data stays in your Postgres database. The only external call is to the Anthropic API for LLM analysis. No telemetry, no data collection, no phone-home. See [THREAT_MODEL.md](THREAT_MODEL.md). |
| Platform | The Platform tool exposed by this server. |
{
"mcpServers": {
"gemot": {
"type": "sse",
"url": "https://gemot.dev/mcp",
"headers": {
"Authorization": "Bearer gmt_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
| GEMOT_API_SECRET | Credential the server authenticates with. | Yes |
| GEMOT_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| STRIPE_SECRET_KEY | Credential the server authenticates with. | Yes |
| STRIPE_WEBHOOK_SECRET | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.