# Mesmer's MCP is ready for your agents

_Published June 12, 2026_

**By [Eugenio Sanchez](https://mesmer.co/resources/author/eugenio)**

**Section:** Feature release

---

Point any MCP-compatible client at our MCP and you can query your
Mesmer engineering data right from the chat.

With it you can:

- Stay up to date on ongoing projects.
- Get metrics and insights on engineering performance.
- Use this data alongside any other tools your client has.

### To install: pick your client

One click install:

- [Install in Cursor](https://cursor.com/install-mcp?name=mesmer&config=eyJ1cmwiOiJodHRwczovL21jcC5tZXNtZXIuY28vbWNwIn0)
- [Install in VS Code](https://insiders.vscode.dev/redirect/mcp/install?name=mesmer&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.mesmer.co%2Fmcp%22%7D)

Snippets for manual installation:

**Claude Desktop**

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mesmer": {
      "type": "http",
      "url": "https://mcp.mesmer.co/mcp"
    }
  }
}
```

Quit and reopen Claude Desktop. The first time you invoke a Mesmer tool, a browser tab opens for OAuth — sign in to your workspace to authorize.

**Claude Code**

- CLI: `any shell`

```shell
claude mcp add --transport http mesmer https://mcp.mesmer.co/mcp
```

OAuth flow runs in your terminal on first tool use. Inspect or remove with `claude mcp list` / `claude mcp remove mesmer`.

**Cursor**

- Global: `~/.cursor/mcp.json`
- Project: `.cursor/mcp.json`

```json
{
  "mcpServers": {
    "mesmer": {
      "url": "https://mcp.mesmer.co/mcp"
    }
  }
}
```

Or use the one-click button above — it opens Cursor's install dialog with the URL prefilled. Browser sign-in runs on first tool call.

**VS Code**

- Workspace: `.vscode/mcp.json`
- User: `settings.json → "mcp"`

```json
{
  "servers": {
    "mesmer": {
      "type": "http",
      "url": "https://mcp.mesmer.co/mcp"
    }
  }
}
```

Note the key is `servers`, not `mcpServers` — VS Code's schema diverges. The one-click button above writes it for you.

**Codex**

- Config: `~/.codex/config.toml`

```toml
[mcp_servers.mesmer]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.mesmer.co/mcp"]
```

Codex doesn't speak OAuth on HTTP MCPs natively, so we bridge through `mcp-remote` — it runs locally as stdio and handles the browser sign-in.

**Other**

- Any client: `Streamable-HTTP MCP support`

```shell
# Use these values in any client that supports HTTP MCP transport:
URL        = https://mcp.mesmer.co/mcp
Transport  = http (streamable)
Auth       = OAuth 2.0 (browser sign-in on first request)

# Stdio-only client? Use the OAuth shim:
npx -y mcp-remote https://mcp.mesmer.co/mcp
```

Works in Windsurf, Zed, Continue, and most agent frameworks — the stdio shim covers anything that can't speak streamable HTTP directly.


### If something's off

- **VS Code uses `servers`, not `mcpServers`.** Pasting a Claude or
  Cursor config into VS Code silently produces no tools and no error —
  the schemas diverged early and never reconciled.
- **Quit and reopen after editing the config.** Claude Desktop and
  Cursor don't hot-reload `mcp.json`. A fully fresh launch is what
  picks up the change.
- **Session expired?** The browser tab reopens automatically.
  Re-authenticate there — no token to rotate locally.
- **Older client version?** Wrap the URL with the stdio shim:
  `npx -y mcp-remote https://mcp.mesmer.co/mcp`.
- **Still stuck?** Email `support@mesmer.co` with the client name,
  version, and the config block you pasted. We'll get it.

---

Canonical: https://mesmer.co/resources/mesmer-mcp