cycles-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port to use for HTTP transport (optional). | |
| CYCLES_MOCK | No | Enables mock mode when set to 'true', which allows running the server without an API key. | |
| CYCLES_API_KEY | No | Your API key for Cycles. Required unless CYCLES_MOCK is set to true. | |
| CYCLES_BASE_URL | No | The base URL for the Cycles API (optional). | https://api.runcycles.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cycles_reserveA | Reserve budget before a costly operation (LLM call, tool invocation, external action). Returns a reservation_id to commit or release later. If decision is not ALLOW, do not proceed with the operation. For lightweight preflight checks without reserving, use cycles_decide instead. |
| cycles_commitA | Commit actual usage after an operation completes. Always call this after cycles_reserve whether the operation succeeded or failed. Finalizes the budget charge and releases any unused reserved amount back to the pool. |
| cycles_releaseA | Release a reservation without committing. Use when an operation is cancelled, skipped, or fails before execution. Returns the released budget amount back to the pool. |
| cycles_extendA | Extend the TTL of an active reservation. Use as a heartbeat for long-running operations to prevent the reservation from expiring. Does not change the reserved amount. |
| cycles_decideA | Lightweight preflight check — ask whether an action would be allowed without reserving budget. Does not create a reservation. Use at workflow start to decide strategy. For concurrency-safe budget locking, use cycles_reserve instead. |
| cycles_check_balanceA | Check current budget balance for a scope. Returns remaining, reserved, spent, allocated, and debt amounts. At least one subject filter (tenant, workspace, app, workflow, agent, or toolset) is required. Do not use as a substitute for cycles_reserve — balances can change between check and action. |
| cycles_list_reservationsA | List reservations, optionally filtered by status (ACTIVE, COMMITTED, RELEASED, EXPIRED) or subject fields. Useful for debugging stuck reservations or auditing budget usage. |
| cycles_get_reservationA | Get details of a specific reservation by ID. Returns status, subject, action, reserved amount, timestamps, and affected scopes. Useful for debugging and monitoring long-running operations. |
| cycles_create_eventA | Record a usage event directly without the reserve/commit lifecycle. Use for fire-and-forget metering of completed operations where pre-estimation is not available. The event is applied atomically to all derived scopes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| integrate_cycles | Generate Cycles integration code for an existing agentic workflow. Produces reserve/commit/release patterns for the specified language and use case. |
| diagnose_overrun | Analyze budget exhaustion or a stopped run. Guides through checking balances, listing reservations, and identifying the root cause of budget issues. |
| design_budget_strategy | Given a workflow description, recommend scope hierarchy, budget limits, units, TTL settings, and degradation strategy for Cycles integration. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cycles-docs-quickstart | Getting started with Cycles MCP server |
| cycles-docs-patterns | Cycles integration patterns and best practices |
TDQS
Scored across 9 tools
Each tool maps to a distinct lifecycle stage or query: reserve, commit, release, extend, decide, check_balance, list/get reservations, and create_event. Even the preflight tools are clearly differentiated: cycles_decide checks allowability without reserving, while cycles_check_balance reports current balances.
All tools share the cycles_ prefix and follow a consistent verb-first snake_case pattern (reserve, commit, release, extend, decide, check_balance, list_reservations, get_reservation, create_event). The naming makes the lifecycle action immediately identifiable.
Nine tools is well-scoped for a budget reservation system: the core reserve/commit/release/extend lifecycle, preflight decision, balance checking, reservation inspection, and direct event recording. No redundant tools; each serves a clear purpose.
The toolset covers the full budget reservation lifecycle, including creation, commit, release, TTL extension, preflight checks, balance inspection, reservation listing/detail queries, and usage-event recording. There are no obvious dead ends or missing operations for the stated domain.