Connect your agent
Add the hosted Starkscan MCP server to Claude, Cursor, Claude Desktop, Cline, or Codex.
Connect your agent
The launcher @starkscan/mcp connects any MCP client to Starkscan. It runs the bundled CLI underneath and forwards your API key from the environment. Get a key first with Get your first API key, then pick your client below. After connecting, see the MCP tools reference.
Shared environment
export STARKSCAN_BASE_URL="https://starkscan.co/api"
export STARKSCAN_CHAIN="SN_MAIN"
export STARKSCAN_API_KEY="<your key>"The launcher injects the default base URL if unset and reads STARKSCAN_API_KEY from the environment — never put the key in a config file you commit.
Generate a config
@starkscan/mcp can print a ready-to-paste config for your client, so the docs never drift from the launcher:
npx -y @starkscan/mcp@alpha print-configClient recipes
All recipes use command: "npx", args: ["-y", "@starkscan/mcp@alpha"], and pass the three STARKSCAN_* env vars (with the key as ${STARKSCAN_API_KEY}).
Cursor
Add .cursor/mcp.json in your project:
{
"mcpServers": {
"starkscan": {
"command": "npx",
"args": ["-y", "@starkscan/mcp@alpha"],
"env": {
"STARKSCAN_BASE_URL": "https://starkscan.co/api",
"STARKSCAN_CHAIN": "SN_MAIN",
"STARKSCAN_API_KEY": "${STARKSCAN_API_KEY}"
}
}
}
}Open Cursor Settings → MCP and refresh the starkscan server.
Claude Desktop
Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"starkscan": {
"command": "npx",
"args": ["-y", "@starkscan/mcp@alpha"],
"env": {
"STARKSCAN_BASE_URL": "https://starkscan.co/api",
"STARKSCAN_CHAIN": "SN_MAIN",
"STARKSCAN_API_KEY": "${STARKSCAN_API_KEY}"
}
}
}
}Restart Claude Desktop, then look for starkscan under the connectors menu.
Cline
Add .cline/mcp.json with the same mcpServers block as above, then reload Cline's MCP servers.
Claude Code and Codex
These have first-class CLI commands — see the one-line claude mcp add and codex mcp add recipes in the MCP quickstart.
Transports
| Transport | When | Notes |
|---|---|---|
| stdio (local) | Local clients spawning the launcher | JSON-RPC over stdio; the launcher runs the bundled binary. |
| Hosted HTTP | Remote/server clients | POST https://starkscan.co/api/mcp with X-Starkscan-Api-Key. A single JSON-RPC request returns 200 with application/json; notifications return 202; GET/DELETE return 405. |
The hosted /api/mcp endpoint is authenticated with X-Starkscan-Api-Key and is origin-allowlisted: a request that sends a browser Origin must be on the allowlist or it is rejected with 403. Server-to-server calls without an Origin header pass through.
Agent discovery
Agents can bootstrap from machine-readable context:
| Artifact | URL | Auth |
|---|---|---|
| Agent memory | /.well-known/starkscan-agent.json | Public |
| llms.txt / llms-full.txt | /llms.txt, /llms-full.txt | Public |
| Agent context | /api/v1/meta/agent-context | API key |
| Capabilities | /api/v1/meta/capabilities | API key |
| Chains | /api/v1/meta/chains | API key |
These advertise the auth header, the /api/v1 external base, the default chain, and the recommended first calls.