elastic.io Model Context Protocol (MCP) Server

An MCP server that connects AI assistants to the elastic.io iPaaS platform — letting them discover, build, modify, and debug integration flows directly.

Terms of Use

The elastic.io MCP server is optional. By connecting an AI agent to elastic.io through it, you agree to the elastic.io Terms of Use, in particular the MCP Interface and AI agents section.

In short:

• Your agent acts as you. Everything your AI agent does through MCP is done on behalf of your elastic.io account.
• Limit its permissions. The agent can read, change and delete data within the permissions of the user account you connect. Use a dedicated user with only the permissions the agent needs, and read-only access wherever possible.
• Your data goes to your AI provider. Data the agent reads is sent to the AI provider you use. You are responsible for your agreement with that provider.
• We don't control your agent. elastic.io does not provide or control your AI agent and is not responsible for its actions or outputs.
• We don't access your secrets. elastic.io does not read, view, store, or otherwise access your sensitive data such as tokens or credential passwords through the MCP server.
• We don't use AI on your data. elastic.io does not use AI to process your data and does not use it to train AI models.

Quick Start

Prerequisites

1. Node.js 22+ — download from nodejs.org

2. A desktop AI client — install one of the supported clients (see below)

3. elastic.io credentials — log in to your elastic.io account, go to your profile page, and click the example to copy the curl command to clipboard. The setup wizard accepts this command directly — just paste it when prompted.

   

One-Command Setup

Run this in your terminal — it will detect your installed AI clients and configure them automatically:

macOS / Linux:

npx -y @elastic.io/mcp@beta setup

Windows (PowerShell):

npx -y "@elastic.io/mcp@beta" setup

Windows notes:

• Always wrap the package name in quotes ("@elastic.io/mcp") — PowerShell misinterprets the @ symbol without them.
• If you get a PSSecurityException error, allow script execution for your user first:

  Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
  

Works on macOS, Linux, and Windows. The setup wizard will:

1. Check your Node.js version (22+ required)
2. Accept the curl command from your profile page (or ask for email and API key manually)
3. Detect which AI clients are installed on your machine
4. Resolve the full path to node/npx (handles NVM, fnm, Homebrew, etc.)
5. Write the MCP config files with correct paths for each client

After setup, restart your AI client — the elastic.io tools will appear in the chat.

Supported Clients (Auto-Setup)

The setup wizard automatically detects and configures these clients:

Claude Desktop, Claude Code, ChatGPT / Codex, Cursor, VS Code (Copilot), Windsurf, Gemini CLI / Gemini IDE, Zed, Cline, Trae, Qwen Code, Kimi Code, DeepSeek, etc.

Manual Configuration

If you prefer to configure manually or use a client not listed above, add the following to your client's MCP config file:

{
  "mcpServers": {
    "elasticio": {
      "command": "npx",
      "args": ["-y", "@elastic.io/mcp"],
      "env": {
        "ELASTICIO_API_EMAIL": "[email protected]",
        "ELASTICIO_API_KEY": "your_api_key",
        "ELASTICIO_API_BASE_URL": "https://api.elastic.io"
      }
    }
  }
}

Note: ChatGPT / Codex uses TOML format — use npx -y @elastic.io/mcp@beta setup for automatic configuration.

Local LLM Agents (Ollama, LM Studio, etc.)

Local LLM-based agents can connect to the elastic.io MCP server using the manual configuration above. However, please note:

• Setup is manual only — the setup wizard does not auto-detect local LLM runtimes.
• No official support — elastic.io does not test against or provide support for local LLM agents. Your experience will depend on the model's capabilities.
• MCP client compatibility required — your local agent must support the MCP protocol (stdio transport) to connect.

Environment Variables

Update

To update to the latest version, clear the npx cache first, then run setup again:

# macOS / Linux
npx -y clear-npx-cache && npx -y @elastic.io/mcp@beta setup

# Windows (PowerShell)
npx -y clear-npx-cache; npx -y "@elastic.io/mcp@beta" setup

This ensures npx fetches the latest version from npm. Your credentials will be re-prompted. Restart your AI clients after the update.

Uninstall

To completely remove the elastic.io MCP server and its credentials from your machine:

1. Remove the elasticio entry from your AI client configs

Open the config file for each client you configured and delete the elasticio section. Config file locations:

For other clients (Cursor, Windsurf, Zed, Cline, Trae, Qwen Code, Kimi Code, DeepSeek, etc.), check your client's documentation for the MCP config file location and remove the elasticio entry.

2. Clear the npx cache

The MCP server binary is cached by npx. To remove it:

# macOS / Linux
npx -y clear-npx-cache
# or manually:
rm -rf ~/.npm/_npx

# Windows (PowerShell)
Remove-Item -Recurse -Force "$env:USERPROFILE\.npm\_npx"

3. Revoke your API key

Your elastic.io API key is stored in plain text in each config file listed above. After removing the config entries:

1. Log in to your elastic.io account
2. Go to your profile page
3. Regenerate your API key

This invalidates the old key even if a copy remains on disk.

Security note: Keep your MCP credentials secret and revoke them without delay if you suspect they may have been compromised.

4. Restart your AI clients

Restart any AI clients that were configured to pick up the changes.

Licence

This package is open-source under the Apache 2.0 licence. Connecting it to the elastic.io platform is subject to the Terms of Use above.