Skip to content

API-317: follow up on the retired Cursor deep link in the MCP README #529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gulshngill wants to merge 2 commits into
base: main
Choose a base branch
from
Open

API-317: follow up on the retired Cursor deep link in the MCP README #529

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45b8584
docs: follow up on the retired Cursor deep link (API-317)
gulshngill Aug 27, 2026
33ec046
Pin mcp-remote to 0.2.1 with an honest justification
gulshngill Aug 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .changeset/mcp-readme-cursor-followup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
"nansen-cli": patch
---

Docs: stop pointing at the retired Cursor install deep link, pin the
`mcp-remote` bridge to the version `mcp install` writes, and correct the
header-formatting note (whitespace after the colon is trimmed; the key belongs
in `env`, not in the argument list).
8 changes: 5 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Connect any MCP client to Nansen's streamable HTTP server:
- **Authentication:** `NANSEN-API-KEY` header
- **API key:** [app.nansen.ai/auth/agent-setup](https://app.nansen.ai/auth/agent-setup)

**Claude Desktop and Cursor:** setup instructions for both — the Claude Desktop `.dxt` bundle and the Cursor install deep link — are in the connection docs: [docs.nansen.ai/mcp/connecting](https://docs.nansen.ai/mcp/connecting).
**Claude Desktop and Cursor:** setup instructions for both are in the connection docs: [docs.nansen.ai/mcp/connecting](https://docs.nansen.ai/mcp/connecting).

**One-command (Claude Code):**

Expand All @@ -82,7 +82,7 @@ claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NA
}
```

**Manual (stdio-only clients):** use `mcp-remote` as a bridge. Keep the header as one argument with no space after the colon:
**Manual (stdio-only clients):** use `mcp-remote` as a bridge. Keep the header name and value in a single `args` entry, and keep the key in `env` rather than in the argument list — `mcp-remote` substitutes `${NANSEN_API_KEY}` from the environment:

```json
{
Expand All @@ -91,7 +91,7 @@ claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NA
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"mcp-remote@0.2.1",
"https://mcp.nansen.ai/ra/mcp",
"--header",
"NANSEN-API-KEY:${NANSEN_API_KEY}"
Expand All @@ -104,6 +104,8 @@ claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NA
}
```

`mcp-remote` is pinned to an exact version rather than `@latest` because the bridge handles your API key on every request, and `npx` would otherwise pull a new release automatically. `0.2.1` is the current release and the version this config is tested against; bumping it is safe — review the release and update the pin.

**Claude Tag (Claude in Slack):** an admin must attach a plugin whose `.mcp.json` points at `https://mcp.nansen.ai/ra/mcp` and add a custom credential allowing the host `mcp.nansen.ai`. See the [Claude Tag custom-connections documentation](https://claude.com/docs/claude-tag/admins/connections/custom). Per-user fallback: use Claude Code or Claude Desktop.

## Trading
Expand Down
Loading