<picture> <source media="(prefers-color-scheme: dark)" srcset="docs/logo/dark.svg" /> <source media="(prefers-color-scheme: light)"
Beeminder MCP server exists for a simple reason — assistants are far more useful when they can act on Beeminder directly instead of describing what you should do. .
Once Beeminder is connected, these are the calls the assistant has available:
Primitive — Use it whenAction — You need one typed, reusable unit of workAgent — The path is open-ended and the model should decide what to doWorkflow — The steps are known and should run durably and predictablyTrigger — Work should start from a schedule, webhook, poll, or app eventStart — keystroke deployBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need one environment variable: OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Beeminder's toolset — Primitive, Action, Agent and 3 more — is a fair guide to whether it matches your workflow. It is maintained by wells-keystroke; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Beeminder's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Primitive | Use it when |
| Action | You need one typed, reusable unit of work. |
| Agent | The path is open-ended and the model should decide what to do. |
| Workflow | The steps are known and should run durably and predictably. |
| Trigger | Work should start from a schedule, webhook, poll, or app event. |
| Start | keystroke deploy |
{
"mcpServers": {
"beeminder": {
"command": "npx",
"args": ["-y", "@keystrokehq/cli"],
"env": {
"OPENAI_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.