Skip to content

MCP Setup

Connect Chronary to your MCP client. You’ll need an API key from the Chronary console before starting.

Chronary is listed on Smithery, the MCP registry — add it to any supported client without hand-editing config files:

  • From the web: open the Chronary listing and click Add to toolbox, then choose your client.
  • From the terminal:
    Terminal window
    npx -y @smithery/cli@latest mcp add chronary/agent-calendar --client claude
    Swap --client for cursor, vscode, claude-code, windsurf, cline, goose, and others. You’ll be prompted for your Chronary API key.

Prefer to wire it up yourself? Use the manual per-client config below.

Add Chronary to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp",
"headers": {
"Authorization": "Bearer chr_sk_your_key_here"
}
}
}
}

Restart Claude Desktop after saving. You should see a hammer icon indicating MCP tools are available.

After setup, test that everything is working. Ask your AI client:

“List my agents”

The AI should call the list_agents tool and return results. If you haven’t registered any agents yet, you’ll see an empty list — that’s expected.

In Claude Desktop, click the hammer icon to see all available tools. You should see 50 Chronary tools listed.

In Cursor, check the agent tool list in the MCP settings panel.

For custom agents, call client.listTools() (TypeScript) or session.list_tools() (Python) and verify 54 tools are returned.

Ask: “Register an AI agent called Test Agent”

The AI should call create_agent and return an agent with an agt_ prefixed ID.

Ask: “Create a calendar called ‘Demo Calendar’ in UTC for that agent, then add a meeting tomorrow at 2pm”

The AI should call create_calendar followed by create_event.

Confirm the data is shared by querying the REST API:

Terminal window
curl https://api.chronary.ai/v1/agents \
-H "Authorization: Bearer chr_sk_your_key_here"

You should see the same agent and calendar created via MCP.

ProblemSolution
Tools not appearingRestart your client after editing the config file. Check for JSON syntax errors.
401 UnauthorizedVerify your API key is correct and includes the Bearer prefix.
403 ForbiddenYour API key may be deactivated. Check the console.
Connection timeoutEnsure you can reach api.chronary.ai from your network. Check firewall/proxy settings.
Tool call returns errorCheck the error message — it follows the same error format as the REST API.