Agent Setup
Azion ships MCP servers, agent-ready documentation, and a CLI, so your coding agent can build on the platform from your editor or terminal.
Last updated
View as MarkdownPick your agent
Select an agent to get step-by-step setup instructions.
AnthropicClaude Code Terminal agent that reads your codebase, runs commands, and edits files. One CLI command connects each Azion MCP server.CursorCursor AI-first IDE built on VS Code, with multi-file Composer edits and background agents. Azion plugs into its MCP settings.GitHubGitHub Copilot Agent mode inside VS Code, with workspace context and native pull-request integration. A file in the project connects Azion.CognitionWindsurf Agentic IDE built around Cascade for multi-step tasks. Connects to Azion through mcp-remote.OpenAICodex Terminal agent that runs commands in a sandbox and reads AGENTS.md natively. Azion goes in config.toml.GoogleGemini CLI Open source terminal agent with a free tier. Declare Azion once in settings.json and verify with /mcp.SSTOpenCode Open source, provider-agnostic terminal agent. Azion is one entry in its MCP block, whichever model you point it at.AnthropicClaude Desktop Desktop app for chatting with Claude on macOS and Windows. Connects to Azion through mcp-remote.WarpWarp Open source agentic terminal with a free tier and a choice of models. Azion goes in its MCP servers settings.AWSKiro Agentic IDE with a free tier and models from several providers. Azion goes in .kiro/settings/mcp.json.
Using something else that speaks MCP? Each server is one HTTP endpoint — point your client at https://docs-mcp.azion.com/mcp, or another of the five servers, with your Personal Token in an Authorization: Token header, and its tools show up.
Compare agents
Understanding agents
Common types, concepts, and tradeoffs.
Workflow
TerminalRuns in a shell. Best for automation, scripting, and CI pipelines.
IDEA full editor with the agent first-class: visual diffs and multi-file edits.
ExtensionPlugs into the editor you already use. Lightest install, keeps your setup.
DesktopA chat app installed on your computer, outside the editor and the terminal. Connects to the MCP servers like any other client.
CloudHosted, with no local install. Ideal for asynchronous, long-running work — and the shape the AI Assistant in the Console takes.
Key concepts
MCPThe Model Context Protocol — the standard that lets an agent call external tools. Azion ships five MCP servers, one per area of the platform, and every agent on this page speaks to them.
Agent contextThe files an agent reads before it answers: llms.txt for the documentation index, AGENTS.md for your project’s own conventions.
Model flexibilityLocked ties you to the maker’s own models. BYOK takes your provider key. Multi-provider switches between several.
ContextSession forgets at the end of a conversation. Project memory persists in a file you commit. Indexed codebase keeps a searchable index of the whole repository.
Common tradeoffs
Cloud vs. localCloud runs long tasks without holding your machine, and sends your code somewhere. Local keeps everything on disk, and stops when your laptop does.
Proprietary vs. open sourceOpen source can be audited, forked and self-hosted. Proprietary tends to ship the newest capability first.
Locked model vs. BYOKA locked model is tuned for its own agent and priced as one subscription. BYOK lets you choose the model per task and pay per token.
Session vs. indexed codebaseAn index answers questions about code nobody opened, at the cost of a copy of the repository. A session only knows what it was shown.