Lattice: CVE, MITRE ATT&CK and detection graph for security agents

# Install the MCP server Lattice: CVE, MITRE ATT&CK and detection graph for security agents (`io.namiq/lattice`)

Its page: https://plug.directory/servers/io.namiq/lattice

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

Ask the person for `YOUR_X_API_KEY` and put it in place of the placeholder; never invent a value.

Use the section for the person's client.

## Claude Desktop

This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http lattice https://lattice.namiq.io/mcp --header 'X-API-Key: YOUR_X_API_KEY'
```

## 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": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "lattice": {
      "type": "http",
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## Zed

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

```json
{
  "context_servers": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## Cline

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

```json
{
  "mcpServers": {
    "lattice": {
      "type": "streamableHttp",
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## Continue

This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.

## Goose

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

```yaml
extensions:
  "lattice":
    type: streamable_http
    name: "lattice"
    enabled: true
    uri: "https://lattice.namiq.io/mcp"
    headers: { "X-API-Key": "YOUR_X_API_KEY" }
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "lattice": {
      "httpUrl": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## Codex

Add to ~/.codex/config.toml:

```toml
[mcp_servers.lattice]
url = "https://lattice.namiq.io/mcp"
http_headers = { "X-API-Key" = "YOUR_X_API_KEY" }
```

## 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": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## Amp

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

```json
{
  "amp.mcpServers": {
    "lattice": {
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## AnythingLLM

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

```json
{
  "mcpServers": {
    "lattice": {
      "type": "streamable",
      "url": "https://lattice.namiq.io/mcp",
      "headers": { "X-API-Key": "YOUR_X_API_KEY" }
    }
  }
}
```

## Augment Code

This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.

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