CrossingKey MCP

# Install the MCP server CrossingKey MCP (`com.crossingkeyintelligence/crossingkey-mcp`)

Its page: https://plug.directory/servers/com.crossingkeyintelligence/crossingkey-mcp

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://mcp.crossingkeyintelligence.com/mcp
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http crossingkey-mcp https://mcp.crossingkeyintelligence.com/mcp
```

## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "crossingkey-mcp": {
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "crossingkey-mcp": {
      "type": "http",
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "crossingkey-mcp": {
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## Cline

Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):

```json
{
  "mcpServers": {
    "crossingkey-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "crossingkey-mcp"
    type: streamable-http
    url: "https://mcp.crossingkeyintelligence.com/mcp"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "crossingkey-mcp":
    type: streamable_http
    name: "crossingkey-mcp"
    enabled: true
    uri: "https://mcp.crossingkeyintelligence.com/mcp"
    headers: {}
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "crossingkey-mcp": {
      "httpUrl": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## Codex

Run in a terminal:

```sh
codex mcp add crossingkey-mcp --url https://mcp.crossingkeyintelligence.com/mcp
```

## mcp-client-cli, TUUI, BoltAI

This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "crossingkey-mcp": {
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "crossingkey-mcp": {
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## AnythingLLM

Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

```json
{
  "mcpServers": {
    "crossingkey-mcp": {
      "type": "streamable",
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

## Augment Code

Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):

```json
{
  "mcpServers": {
    "crossingkey-mcp": {
      "type": "http",
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.