> This page is for Data Protection. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.eon.io/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.eon.io/_mcp/server. # Add the Eon Local MCP Server This article explains how to run the Eon local MCP server, so an AI tool can work with your Eon account without an interactive browser sign-in. `eon-mcp-local` is a Python package that runs as a local process and communicates using the Model Context Protocol (MCP) over stdio. It signs in to the Eon API with API credentials instead of a browser, so it works where an interactive sign-in isn't possible: CI pipelines, scripts, headless containers, and agent frameworks. It's also the option to choose when you want to run the server process yourself. ## Add the Eon local MCP server ### Before you start Before you start, make sure: * Python 3.12 or later is installed. * Either [`uv`](https://docs.astral.sh/uv/) or [`pipx`](https://pipx.pypa.io/stable/) is installed. The examples here use `uvx`, which comes with `uv`. * You've decided which Eon role the AI tool should act with. An API client receives its permissions from the role assigned to its credentials, so the role has to cover everything you'll ask the AI tool to do. #### Create API credentials in Eon 1. On the API credentials page, create a set of credentials and assign them the role you chose. 2. Copy the client ID and the client secret. The client secret is shown only once, when you create the credentials. If you lose it, rotate the secret from the same page to get a new one. > **Warning** > > The server acts as the API client rather than as you, and the role assigned to its credentials can let it start an on-demand snapshot, connect a source account, create a backup policy, or open an action request. > Assign a role with only the permissions the AI tool needs. #### Configure and start the server Register `eon-mcp-local` with your AI tool as a stdio MCP server, and pass the Eon credentials to it as environment variables. The command is `uvx eon-mcp-local serve`, which fetches and caches the package on first run, so there's nothing to install up front. `serve` is the only subcommand and it takes no flags, so all configuration comes from the environment. #### Claude Code Add the server with `claude mcp add`, passing the variables inline: ```shell claude mcp add eon-local \ --env EON_CLIENT_ID= \ --env EON_CLIENT_SECRET= \ --env EON_ACCOUNT_DOMAIN= \ -- uvx eon-mcp-local serve ``` #### Other MCP clients In Cursor, Codex, or any other tool that communicates using MCP over stdio, add a stdio MCP server that runs this command: ```shell uvx eon-mcp-local serve ``` Set the same environment variables wherever that tool keeps a server's environment. These are the environment variables the server reads: **`EON_CLIENT_ID`** `string` — required The client ID from the API credentials. --- **`EON_CLIENT_SECRET`** `string` — required The client secret from the API credentials. --- **`EON_ACCOUNT_DOMAIN`** `string` — required Your Eon subdomain on its own, not a full URL. For an account hosted at `acme.console.eon.io`, the value is `acme`. --- **`EON_LOG_LEVEL`** `string` — default: INFO How much the server logs: `DEBUG`, `INFO`, `WARNING`, `ERROR`, or `CRITICAL`. The value isn't case sensitive. --- **`EON_JSON_LOGGING`** `boolean` — default: false Set to `true` to write logs as JSON. --- The server also reads a `.env` file from the directory it starts in, so you can keep these variables in that file instead of exporting them. If you'd rather install the package than fetch it on each run, install it with `uv tool install eon-mcp-local` or `pipx install eon-mcp-local`, then use `eon-mcp-local serve` as the command. Your AI tool now starts the server as a local process and signs in to Eon with the API credentials. An access token is valid for 12 hours, and the server keeps it in memory only, so it's never written to disk. To check that the connection works, ask your AI tool to list the tools available to it, then ask it something small, such as which backup jobs ran most recently. In Claude Code, you can also run `/mcp` to see the server's status. ## Troubleshooting #### The server exits with an error about missing environment variables The server reports `error: missing required environment variables` when `EON_CLIENT_ID`, `EON_CLIENT_SECRET`, and `EON_ACCOUNT_DOMAIN` aren't all set. Set all three in the AI tool's server configuration, or in a `.env` file in the directory the server starts in. #### Every call fails with HTTP 401 Either the credentials are no longer active, or they belong to a different Eon account than the one in `EON_ACCOUNT_DOMAIN`. Check both on the API credentials page, and rotate the secret if you're not sure the one you copied is still valid. #### The server can't resolve or reach the Eon API `EON_ACCOUNT_DOMAIN` takes your subdomain on its own, so a full URL such as `https://acme.console.eon.io` produces a name that doesn't resolve. Set it to just the subdomain, such as `acme`. #### Log lines show up in the server's output The server writes all logs to stderr, because stdout carries the MCP protocol frames. Capture stderr separately from stdout, and set `EON_LOG_LEVEL` to `WARNING` or `ERROR` if you want fewer logs. ## See also * [About AI Integrations] * [Add the Eon Plugin for Claude Code] [About AI Integrations]: /data-protection/integrations/ai-integrations/about-ai-integrations [Add the Eon Plugin for Claude Code]: /data-protection/integrations/ai-integrations/add-ai-integrations/claude-code