Glossary
Definitions of the terms the Azion MCP servers use, from tools and resources to personal tokens, dry_run, mcp-remote, and streamable HTTP.
This glossary defines the terms that the Azion MCP servers use in its answers, in the configuration of a coding agent, and across its documentation.
| Term | Definition |
|---|---|
dry_run | The input that makes a write tool of the build, secure, observe, or storage server return the Azion API request it would send, without sending it. The preview carries the method, URL, headers, and body, including your personal token in the Authorization header. Create Rules Engine rules with the MCP server uses it before every write. |
| MCP server | One of the five hosted Model Context Protocol servers that Azion runs, each at the /mcp path of its own host: docs-mcp.azion.com, build-mcp.azion.com, secure-mcp.azion.com, observe-mcp.azion.com, and storage-mcp.azion.com. The docs server searches Azion documentation, code samples, CLI commands, API operations, and Terraform resources, and the other four read and change the resources of your account. MCP server describes what they offer, and Agent Setup connects each coding agent to them. |
mcp-remote | The package that bridges a client that starts its servers as local processes to an MCP server over HTTP. npx downloads and runs it with the server URL and the Authorization header, as in npx -y mcp-remote@latest https://docs-mcp.azion.com/mcp --header "Authorization: Token [TOKEN VALUE]". MCP server quickstart shows the clients that use it. |
| personal token | The Azion credential that authenticates every request to the MCP servers: azion followed by 35 letters and digits, 40 characters in all. A client sends it as Authorization: Token [TOKEN VALUE]. A personal token sent with the Bearer scheme fails with 401. A request without the header gets 401 No authentication provided, and a request with an invalid token gets 403 Authentication failed. Personal Tokens describes how a token is created and when it expires. |
Pragma: azion-debug-cache | The request header that makes an Azion response carry its cache debug headers, such as x-cache, x-cache-key, and x-cache-expires-in. Test cache behavior with the MCP server uses it to read the cache state of a deployed site, and Cache quickstart explains x-cache and x-cache-key. |
| prompt | A message template that a Model Context Protocol server can offer to its clients. Run an MCP server on Azion shows how to add prompts to a server of your own. |
| resource | A document that a client reads from an MCP server by its URI, the way it reads a file, without calling a tool. The Azion docs server serves seven Markdown resources, under azion://guides/deploy/ and azion://guides/test-cache/. Tools and resources lists each URI. |
| streamable HTTP | The Model Context Protocol transport that the MCP servers use: a client sends each message as an HTTP POST to the /mcp path of the server, such as https://docs-mcp.azion.com/mcp. The servers require TLS 1.3. Client configurations name this transport http or streamable-http, and How the MCP server works describes the request flow. |
| tool | A function that an MCP server offers and a coding agent calls by name with JSON arguments, such as search_azion_docs_and_site with a query. The docs server tools only read. The build, secure, observe, and storage tools also create, change, and delete resources, and each write tool takes dry_run. Tools and resources lists the tools of each server. |