Skip to content
Try the API

Elastio MCP server

The Elastio MCP server lets AI agents that speak the Model Context Protocol query your Elastio tenant. Once connected, an agent can answer questions about your findings, assets, lateral movement and policies without you writing any API calls.

  • The MCP endpoint issued by your CSM. The Elastio MCP server is at https://mcp.elastio.com; use the exact endpoint your CSM gives you.
  • A scoped, read-only API token. Create a personal access token that grants only read access, only to the categories the agent should see, and give it an expiry. Don’t use a token with all_scopes or any write grant for an agent.
  • An MCP-compatible client, such as Claude Code, Claude Desktop, Cursor, VS Code or Windsurf.
  1. Export the read-only token:

    Terminal window
    export ELASTIO_TOKEN="…"
  2. Add the server:

    Terminal window
    claude mcp add elastio --url https://mcp.elastio.com --token $ELASTIO_TOKEN
  3. Check that it’s registered:

    Terminal window
    claude mcp list

Then ask questions in plain language, for example “Which assets have open critical findings?” or “Which policies cover this account?”.

Elastio’s console integration docs list Claude Desktop, Cursor, VS Code and Windsurf as supported clients. Each one configures remote MCP servers in its own settings file or UI, and the details change between releases, so follow your client’s documentation for adding a remote (HTTP) MCP server. Every MCP-compatible client needs the same two values:

Setting Value
Server URL The endpoint from your CSM, for example https://mcp.elastio.com
Authentication Bearer token: your read-only Elastio API token, sent as Authorization: Bearer <token>

Give the server a recognizable name such as elastio, and reference the token from an environment variable or your client’s secret store rather than pasting it into a shared configuration file.

The set of tools is defined by the server and can change. Your client shows the tools it discovered after connecting (in Claude Code, run /mcp). This site doesn’t document individual tool names.

  • Server not listed or not connecting. Confirm the endpoint with your CSM; the server must be enabled for your tenant.
  • Authentication errors. Check that the token hasn’t expired or been revoked, and that it was issued for the same tenant. See Authentication.
  • Answers are missing data. The agent sees only what the token’s grants allow. Add read access for the category you need, or issue a new token.