Integrations
Editor-specific setup for using Cadence with Claude Code, Cursor, OpenAI Codex, Gemini, Antigravity, and OpenCode.
Configure your AI coding agent to understand Cadence smart contracts. Each integration uses the same two building blocks:
- Project context — point your agent at
/llms-full.txt(or/llms.txtfor a leaner index) so it has the full Cadence reference loaded. - MCP server — register the Cadence MCP server (built into the Flow CLI as
flow mcp) for code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution.
For Claude Code specifically, the flow-ai-tools marketplace bundles the full Cadence + Flow skill suite under one plugin install.
Editors
| Editor | Project context | Skills | MCP |
|---|---|---|---|
| Claude Code | via flow-ai-tools skills | ✓ full suite | ✓ stdio |
| Cursor | .cursor/rules/cadence.mdc | — | ✓ stdio (deeplink) |
| OpenAI Codex | AGENTS.md | — | — |
| Gemini | GEMINI.md | — | — |
| Antigravity | CADENCE.md / AGENTS.md | — | ✓ stdio |
| OpenCode | AGENTS.md | — | ✓ stdio |
For Claude Desktop and Claude API setup, see the Claude page.
Don't see your editor?
Any MCP-aware editor can use the Cadence MCP server — point it at flow mcp as a stdio command (Flow CLI ≥ v2.16.0). Any agent that reads project-level context files (AGENTS.md, etc.) can use the LLM endpoints for the full Cadence reference. Open an issue if you'd like first-class instructions for a specific editor.