MCP server for Cycles — runtime budget authority for autonomous agents
MCP server for Cycles — runtime budget authority for autonomous agents. Exposed over MCP by the cycles mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Autonomous AI agents (Claude, GPT, custom agents) call LLMs, invoke tools, and hit external APIs — but have no built-in way to cap how much they spend. A single agent loop can burn through hundreds of dollars before anyone notices. Multiply that across tenants and teams, and cost control becomes a real problem.
Everything the assistant can do here goes through one of these:
cycles_reserve — POST /v1/reservationscycles_commit — POST /v1/reservations/{id}/commitcycles_release — POST /v1/reservations/{id}/releasecycles_extend — POST /v1/reservations/{id}/extendcycles_decide — POST /v1/decidecycles_check_balance — GET /v1/balancescycles_list_reservations — GET /v1/reservationscycles_get_reservation — GET /v1/reservations/{id}cycles_create_event — POST /v1/eventsBeing 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 8 environment variables: CYCLES_BASE_URL, CYCLES_API_KEY, CYCLES_MOCK, CYCLES_ALLOW_MOCK_IN_PRODUCTION, PORT, HOST, MCP_HTTP_AUTH_TOKEN, CYCLES_DEFAULT_TENANT. 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.
Plenty of team communication 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. Cycles's toolset — cycles_reserve, cycles_commit, cycles_release and 6 more — is a fair guide to whether it matches your workflow. It is maintained by runcycles; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| cycles_reserve | POST /v1/reservations |
| cycles_commit | POST /v1/reservations/{id}/commit |
| cycles_release | POST /v1/reservations/{id}/release |
| cycles_extend | POST /v1/reservations/{id}/extend |
| cycles_decide | POST /v1/decide |
| cycles_check_balance | GET /v1/balances |
| cycles_list_reservations | GET /v1/reservations |
| cycles_get_reservation | GET /v1/reservations/{id} |
| cycles_create_event | POST /v1/events |
{
"mcpServers": {
"cycles": {
"command": "npx",
"args": ["-y", "@runcycles/mcp-server"],
"env": {
"CYCLES_BASE_URL": "your-value",
"CYCLES_API_KEY": "your-value",
"CYCLES_MOCK": "your-value",
"CYCLES_ALLOW_MOCK_IN_PRODUCTION": "your-value",
"PORT": "your-value",
"HOST": "your-value",
"MCP_HTTP_AUTH_TOKEN": "your-value",
"CYCLES_DEFAULT_TENANT": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CYCLES_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| CYCLES_API_KEY | Credential the server authenticates with. | Yes |
| CYCLES_MOCK | Configuration value read at startup. | Optional |
| CYCLES_ALLOW_MOCK_IN_PRODUCTION | Configuration value read at startup. | Optional |
| PORT | Configuration value read at startup. | Optional |
| HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_HTTP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| CYCLES_DEFAULT_TENANT | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.