Azion MCP servers: Connect Your Coding Agent to Azion

Ask a coding agent to configure cache on Azion, and it answers from what it learned in training. If that knowledge is out of date, the agent guesses endpoints, CLI flags, and API fields.

So you paste documentation into the chat, or the agent writes a configuration that someone rebuilds by hand in Azion Console. An agent that calls the API with curl has no schema for the operations and no preview step, and you find the mistake after the call.

Today, Azion MCP servers are generally available. They connect your coding agent to the Azion documentation and to your Azion account. The agent looks up answers and changes resources through the Azion API, and you can preview every write before it runs. Every Azion plan includes them.

What Azion MCP servers are

The Model Context Protocol (MCP) is an open standard for how an agent finds and calls the tools a server offers. Azion MCP servers are five hosted servers, one for each area of the Azion Platform:

Azion hosts the servers, so you have nothing to install or maintain. Each request carries your personal token, and the agent acts with that token’s permissions. The servers use streamable HTTP at the /mcp path and accept only TLS 1.3.

The MCP servers are a platform resource, like the Azion API, the Azion CLI, and the Terraform Provider. The four servers that act on your account follow the areas of the platform: build for Build, secure for Secure, observe for Observe, and storage for Store.

What your agent can do with Azion MCP servers

Answer from the current docs

The docs server searches the Azion documentation, code samples, and the references for the Azion API, the Azion CLI, and the Terraform Provider. Each result carries its source page, so you can check what the agent read before you act on its answer.

Manage your account from the agent

The build, secure, observe, and storage servers expose 207 tools. Your agent lists, creates, changes, and deletes applications, rules, WAF, DNS records, certificates, data streams, buckets, and SQL databases through the Azion API. It can also purge cache, reorder rules, and generate GraphQL queries that run against your account.

Preview every write

Each tool that creates, changes, or deletes accepts dry_run. With it, the tool returns the exact API request (method, URL, headers, and body) without sending it. Write tools also accept an idempotency_key.

You ask for a change, read the request the agent shows you, and then tell it to run the call. The agent acts with the permissions of your personal token, and you add only the servers it needs. The docs server only reads.

Work with the agent you already use

Claude Code, Cursor, GitHub Copilot, Windsurf, Codex, Gemini CLI, OpenCode, Claude Desktop, Warp, and Kiro each have a setup page in Agent Setup. Claude Code connects with one command. Claude Desktop and Windsurf reach the servers through the mcp-remote bridge.

Who uses the MCP servers

• Developers who already work with a coding agent ship without leaving the editor or the terminal, and spend less time in Azion Console.
• Infrastructure and SRE teams run repetitive tasks by prompt: cache purges, rules, deployments, and data streams.
• Security analysts review and adjust WAF, Firewall rules, and network lists with a preview before anything changes.
• Engineering leaders get speed with control: dry_run on every write, a separate server for each area, and tokens that expire on the date you set.

Prompts to try first

Each of these prompts comes from the quickstart and reaches a different server.

The docs server answers from the documentation:

Search the Azion documentation: how to configure cache

The build server writes Rules Engine rules, and dry_run shows them to you first:

Create Rules Engine rules to add security headers including HSTS, X-Frame-Options, and CSP for my application. Preview them with dry_run first.

The observe server writes a GraphQL query and runs it against your account:

Generate a query to analyze cache hit rates for my images.

What the servers do not cover

• There are no KV Store tools.
• Build and deploy stay with the Azion CLI. The docs server returns the deploy guide, and you or your agent run the commands.
• Search ranks results by word proximity, so the first result can miss the topic. Check the source page when an answer looks off.
• create_graphql_query, on the observe server, uses a language model to write the query, and it can fail. A failure comes back as text inside a successful result, so read what the tool returns.

For every tool and its inputs, see Tools and resources.

Connect Azion MCP servers in one command

Create a personal token in Azion Console. The agent acts with the permissions of that token, so give it a short expiration. Then register the docs server in Claude Code, replacing [TOKEN VALUE] with your token:

claude mcp add "azion-docs" "https://docs-mcp.azion.com/mcp" -t http -s user -H "Authorization: Token [TOKEN VALUE]"

To add the build, secure, observe, or storage server, run the same command with its name and URL, such as azion-build and https://build-mcp.azion.com/mcp. These four servers change your account, so add only the ones your agent needs.

The quickstart walks through the token, the connection check, and your first question. For Cursor, GitHub Copilot, and the other clients, follow Agent Setup.

Start with Azion MCP servers

Every Azion plan includes Azion MCP servers at no additional cost, so there is nothing to buy before you connect. Read the MCP server documentation to see how the servers work, follow the quickstart to connect in one command, or start free to create your account.