Installation

Choose your preferred installation method and IDE below.

Get Your Intercom Access Token

Before configuring any IDE, you need an Intercom access token:

1. Go to Settings > Integrations > Developer Hub in your Intercom workspace
2. Create or select an app, then go to Authentication
3. Copy the Access Token (starts with dG9rO... or similar)
4. Ensure the token has scopes for reading contacts and conversations

caution

Never commit your Intercom access token to version control. Always use environment variables or IDE-specific secret management.

OAuth Authentication (Alternative)

Instead of a static access token, you can use OAuth 2.0 for automatic token management:

1. Create an OAuth app in your Intercom Developer Hub > Your Apps
2. Set the environment variables:

   export INTERCOM_CLIENT_ID=your-client-id
   export INTERCOM_CLIENT_SECRET=your-client-secret

3. Run the login command:

   intercom-mcp auth login

4. A browser window opens for authorization. After approving, tokens are stored at ~/.mcp-pool/intercom/tokens.json
5. The server auto-refreshes tokens — no manual intervention needed

Other auth CLI commands:

intercom-mcp auth logout  # Clear stored tokens
intercom-mcp auth status  # Show current auth state

Environment Variables

Variable	Required	Description
INTERCOM_ACCESS_TOKEN	Yes*	Intercom access token with read permissions
INTERCOM_CLIENT_ID	Alt	OAuth 2.0 client ID
INTERCOM_CLIENT_SECRET	Alt	OAuth 2.0 client secret

*Either the static token OR the OAuth client credentials are required.

---

Option A: Via npx (Recommended)

No installation needed. Your IDE will run the server on demand:

npx -y @vineethnkrishnan/intercom-mcp

This is the simplest method — just reference it in your IDE config below.

Option B: Global Install

npm install -g @vineethnkrishnan/intercom-mcp

Then use intercom-mcp as the command in your IDE config (instead of npx).

Option C: From Source

git clone https://github.com/vineethkrishnan/mcp-pool.git
cd mcp-pool
npm install
npm run build

Then use node /absolute/path/to/mcp-pool/packages/intercom/build/index.js as the command.

---

IDE Configuration

Claude Desktop

Config file location:

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json

Quick access: Settings > Developer > Edit Config

Using npx:

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

Using global install:

{
  "mcpServers": {
    "intercom": {
      "command": "intercom-mcp",
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

From source:

{
  "mcpServers": {
    "intercom": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-pool/packages/intercom/build/index.js"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

tip

Restart Claude Desktop completely after editing the config. Changes are not picked up automatically.

---

VS Code (GitHub Copilot)

Config file location:

Scope	Path
Workspace	.vscode/mcp.json (in your project root)
User (macOS)	~/Library/Application Support/Code/User/mcp.json
User (Windows)	%APPDATA%\Code\User\mcp.json
User (Linux)	~/.config/Code/User/mcp.json

Quick access: Command Palette (Cmd+Shift+P) > MCP: Open User Configuration

warning

VS Code uses "servers" as the root key, not "mcpServers".

Workspace config (.vscode/mcp.json):

{
  "servers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "${input:intercom-token}"
      }
    }
  },
  "inputs": [
    {
      "id": "intercom-token",
      "description": "Intercom Access Token",
      "type": "password"
    }
  ]
}

The inputs feature prompts you for the token securely — it never gets stored in the file.

User config (without inputs):

{
  "servers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

---

Cursor

Config file location:

Scope	Path
Global	~/.cursor/mcp.json
Project	.cursor/mcp.json (in your project root)

Quick access: Settings > Cursor Settings > MCP

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

Project-level config (.cursor/mcp.json) takes precedence over global config.

---

Windsurf (Codeium)

Config file location:

OS	Path
macOS / Linux	~/.codeium/windsurf/mcp_config.json
Windows	%USERPROFILE%\.codeium\windsurf\mcp_config.json

Quick access: Settings > Advanced Settings > Cascade section

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

tip

Make sure MCP is enabled in Windsurf: Settings > Advanced > Cascade > Enable MCP.

---

JetBrains IDEs (IntelliJ, WebStorm, PyCharm, etc.)

JetBrains IDEs (2025.2+) support MCP servers through the settings UI.

Setup:

1. Open Settings/Preferences > Tools > AI Assistant > MCP Servers
2. Click + Add to add a new server
3. Configure:
   • Name: intercom
   • Command: npx
   • Arguments: -y @vineethnkrishnan/intercom-mcp
   • Environment Variables: INTERCOM_ACCESS_TOKEN=dG9rOi...
4. Click OK and restart the AI Assistant

Alternative — manual config file:

Create or edit ~/.config/JetBrains/mcp.json:

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

---

Claude Code (CLI)

Option 1 — CLI command (recommended):

claude mcp add intercom \
  --scope user \
  -e INTERCOM_ACCESS_TOKEN=dG9rOi... \
  -- npx -y @vineethnkrishnan/intercom-mcp

Scope options:

• --scope user — available in all your projects
• --scope local — current project only (default)
• --scope project — shared with team via .mcp.json

Option 2 — manual config:

Edit ~/.claude.json (user scope) or .mcp.json (project scope):

{
  "mcpServers": {
    "intercom": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/intercom-mcp"],
      "env": {
        "INTERCOM_ACCESS_TOKEN": "dG9rOi..."
      }
    }
  }
}

Verify it's working:

claude mcp list

---

Uninstallation

Claude Code (CLI)

claude mcp remove intercom

To check which servers are configured:

claude mcp list

Claude Desktop / Cursor / Windsurf / JetBrains

Remove the "intercom" entry from the "mcpServers" block in the relevant config file, then restart the IDE.

VS Code (GitHub Copilot)

Remove the "intercom" entry from the "servers" block in .vscode/mcp.json or user-level mcp.json, then reload the window.

Global npm install

If you installed globally, also run:

npm uninstall -g @vineethnkrishnan/intercom-mcp

---

Verify Installation

After configuring your IDE, test the connection by asking your AI assistant:

"List my most recent Intercom conversations."

If the server is working, you'll get a response with your recent conversations. If not, check:

1. Access token is valid — test with curl -H "Authorization: Bearer dG9rOi..." -H "Intercom-Version: 2.11" https://api.intercom.io/me
2. Node.js >= 20 — run node --version
3. Config file syntax — validate your JSON (no trailing commas)
4. Restart your IDE — most IDEs require a full restart after config changes

Security Recommendations

• Use tokens with minimal scopes — only read access to contacts and conversations
• Never share config files containing access tokens
• Add config files with secrets to .gitignore
• Rotate tokens periodically via your Intercom Developer Hub