MCP server

An MCP server gives a coding agent tools it can call to look facts up instead of recalling them from training, and to act on a system on your behalf. The Model Context Protocol (MCP) is an open standard, developed by Anthropic, that uses JSON-RPC to define how an agent lists the tools of a server, calls them, and reads its resources. The agent asks the server when a question needs a fact or a task needs an action, and reads the answer as context, so you do not paste documentation into the conversation yourself.

Azion MCP servers are five hosted MCP servers, one per area of the Azion Platform, each at its own URL. They authenticate every request with your Azion personal token. The docs server answers questions from the Azion documentation, code samples, and the references of the Azion CLI, the Azion API, and the Azion Terraform Provider. The build, secure, observe, and storage servers read and change the resources of your account through the Azion API. Use the Azion MCP servers to find a CLI command or an API operation, pull a code sample, create a Rules Engine rule, purge cache, or write a GraphQL query for the metrics of your account.

Connect your agent to the MCP servers

Hand the setup to your coding agent, or follow the steps for your client yourself.

Tool call

A coding agent reaches a tool with a JSON-RPC tools/call request. The request below asks search_azion_docs_and_site on the docs server for two documents about cache. It is a POST to https://docs-mcp.azion.com/mcp with the headers Authorization: Token [TOKEN VALUE], Content-Type: application/json, and Accept: application/json, text/event-stream, and this body:

The result holds one text item, cut below at …; the full value holds the two documents that docsAmount asks for:

• params.name selects the tool, and params.arguments carries its inputs: the query, and docsAmount for the number of documents.
• result.content holds one item of type text. For a search tool, that text is a JSON object whose results array holds the documents, each with its title, content, and source, and the similarity, search_type, and relevance_score of the match.
• The Authorization header travels with every request.

If you know JSON-RPC 2.0, you know the message format. You rarely write these requests by hand: the MCP client of your agent writes them when you ask in natural language, such as with one of these prompts:

• Configure Rules Engine to cache static assets for 1 year and API responses for 5 minutes.
• Optimize my site's Core Web Vitals scores

Request path

The docs server only reads. The build, secure, observe, and storage servers can create, change, and delete resources, within what your personal token allows. Each of their write tools takes dry_run, which returns the API request without sending it.

1. You add each server you need to the configuration of your coding agent, with your personal token in the Authorization header.
2. When a question needs a fact or a task needs an action, the MCP client of the agent sends a JSON-RPC request to the URL of the server that owns it, as an HTTP POST.
3. The server checks the token.
4. A search tool of the docs server runs the query against a corpus of Azion documents.
5. A tool of the other four servers sends a request to the Azion API with your token. A write tool called with dry_run returns that request instead of sending it. create_graphql_query, on the observe server, asks a language model to write a query from the goal you state, and runs it against the GraphQL API of your account.
6. The server returns the result as text, and the agent uses it to answer you.

For the transport and the authentication schemes, refer to How the MCP server works.

What the servers cover

The Azion MCP servers answer questions and act on your account. These are their tools, their limits, and the ways to reach them:

• Tools: the docs server exposes seven tools. Six search the Azion documentation and website, code samples, Azion CLI commands, the Azion API v4 and v3 references, and the Azion Terraform Provider documentation, and deploy_azion_static_site returns guides to deploy a static site and test its cache. The other four servers expose tools to list, read, create, change, and delete the resources of their area. Tools and resources lists them by server.
• Resources: the docs server serves seven Markdown resources under azion://guides/deploy/ and azion://guides/test-cache/, the same guides that deploy_azion_static_site returns.
• Writes: the build, secure, observe, and storage tools change your account through the Azion API, with your token. Ask the agent to call a write tool with dry_run first, and review the request it returns. The preview shows your token in the Authorization header, so remove it before you share a preview. The docs server does not deploy: the static site guides name the Azion CLI commands that you or your agent run.
• Answers: search ranking is loose, so the top match can miss the topic. Each search document carries its source, the page to check it against. create_graphql_query reports a failure as text inside a successful result.
• Credential: every request carries a personal token as Authorization: Token [TOKEN VALUE]. A personal token sent with the Bearer scheme fails with 401. A request without the header gets 401 with the message No authentication provided. You create the token in Azion Console.
• Connection: each server uses the streamable HTTP transport at the /mcp path of its host, and accepts only TLS 1.3.
• Clients: Agent Setup connects Claude Code, Cursor, GitHub Copilot, Windsurf, Codex, Gemini CLI, OpenCode, Claude Desktop, Warp, and Kiro. Claude Desktop and Windsurf reach the servers through the mcp-remote bridge. MCP server quickstart connects Claude Code with one command.
• Your own server: to build and deploy an MCP server of your own as an Azion function, refer to Run an MCP server on Azion.
• Help: Troubleshoot the MCP server lists each error with its cause and fix, Test cache behavior with the MCP server uses the cache guides on a deployed site, and the Glossary defines the terms of the servers.

Next steps