About AI Integrations

Eon AI integrations let you work with your Eon account through natural language in the AI tools your team already uses. Whether you add an MCP plugin in your IDE or register an agent, you get access to the same Eon AI capabilities.

Eon offers two kinds of integrations:

Plugins connect through the Model Context Protocol (MCP) in tools such as Claude Code, Cursor, and Codex.
Agents connect through Agent-to-Agent (A2A) in Google Gemini Enterprise.

What you can do

Through any supported integration, the Eon AI agent can help you with tasks such as:

Onboard cloud accounts and run resource discovery.
Connect, activate, and deactivate GCP organizations, folders, and projects.
View backup jobs, policies, schedules, and retention settings.
View restore jobs, including status, progress, and errors.
Browse discovered cloud resources and their protection status.
Explore snapshots for a resource, including creation time, size, and status.

For a full list of actions, ask your AI tool to list the skills and tools available to it.

Choose your integration

Claude Code

Add the Eon plugin in Claude Code.

Cursor

Add the Eon plugin in Cursor.

Gemini Enterprise

Add the Eon agent in Google Gemini Enterprise.

Local MCP Server

Run the Eon MCP server yourself, without a browser sign-in.

If your AI tool isn’t listed here, you can configure it to connect to an Eon MCP server directly: the remote server at https://mcp.eon.io/mcp, or the local server described below.

Remote and local MCP servers

Eon offers two MCP servers, and the difference between them is how they sign in. The remote server is hosted by Eon and signs you in through your browser, so it acts as you, with the permissions of your own role. The local server, eon-mcp-local, runs as a process on your own machine and signs in with an API credential, so it needs no browser and acts as that credential.

	Remote MCP server	Local MCP server
Address or command	`https://mcp.eon.io/mcp`	`uvx eon-mcp-local serve`
Transport	Hosted HTTP	Local process over stdio
Sign-in	OAuth 2.0 authorization code with Proof Key for Code Exchange (PKCE), through a browser	OAuth 2.0 client credentials, no browser
Acts as	The person who signed in	The API credential
Permissions come from	That person’s role	The role assigned to the credential
Use it for	Interactive use in Claude Code, Cursor, and Claude Desktop	CI pipelines, scripts, agent frameworks, headless containers, and running the server yourself

The remote server is the default for interactive use, and every integration on this page uses it. Choose the local server when a browser sign-in isn’t possible, or when you want to run the server process yourself. To set it up, see Add the Eon Local MCP Server.