Onboard your agent to Caly
Copy one sentence, paste it into your coding agent, and it sets itself up: it asks you for an API key once, stores it as CALY_API_KEY, teaches itself the API from our OpenAPI spec, and proves the key works against https://api.trycaly.com/v2/me.
Fetch and execute the appropriate instructions to set me up for Caly from https://trycaly.com/agent-setup/prompt.md
The sentence points at /agent-setup/prompt.md, a plain-markdown file your agent fetches and executes. Read it yourself first if you like — it never embeds a key.
Claude Code
Stores the key in .env, connects the MCP server, adds a Caly section to CLAUDE.md, then verifies.
Codex
Stores the key in .env, connects the MCP server, adds a Caly section to AGENTS.md, then verifies.
Cursor
Stores the key in .env, connects the MCP server, adds a Caly section to .cursor/rules/caly.mdc, then verifies.
OpenCode
Stores the key in .env, connects the MCP server, adds a Caly section to AGENTS.md, then verifies.
What you get
- The full REST API: bookings, event types, schedules, availability slots, calendars and webhooks — everything the app can do.
- The Caly MCP server at
https://mcp.trycaly.com/mcp: event types, free slots and bookings as tools, with a confirmation step before anything is cancelled. - An agent that reads the OpenAPI spec instead of guessing endpoints.
- A key that lives in a git-ignored env file and is never printed back.
The verify step
curl -s -H "Authorization: Bearer $CALY_API_KEY" https://api.trycaly.com/v2/me
Success is the profile of the key's owner. A 401 means the key is missing or mistyped.