Getting Started

This server speaks the Model Context Protocol over the Streamable HTTP transport at:

POST https://mcp.suralink.ai/mcp

The sections below show how to register it with the clients we support most often.

Authentication

Deployed environments authenticate every request with an OAuth bearer token. You do not paste a token by hand — MCP clients discover how to sign in on their own:

1. The server publishes an RFC 9728 OAuth Protected Resource metadata document at /.well-known/oauth-protected-resource.
2. On the first request without a token, the server responds with 401 Unauthorized and a WWW-Authenticate challenge pointing at that document.
3. The client reads the document, learns which identity provider to use, and starts a standard PKCE sign-in flow. No out-of-band configuration is needed.

Once you sign in, the client attaches your bearer token to every request automatically.

Access requirements

• Your firm must have Suralink MCP access enabled. If it does not, the server returns a clear message telling you to contact your firm administrator or Suralink sales.
• Individual tools appear only when your account holds the access they require. See the Tools reference for the requirement on each tool.

Claude Desktop

Claude Desktop loads MCP servers from claude_desktop_config.json:

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json

If your build supports native HTTP MCP servers:

{
  "mcpServers": {
    "suralink-mcp": {
      "type": "http",
      "url": "https://mcp.suralink.ai/mcp"
    }
  }
}

Otherwise, use the mcp-remote bridge, which proxies stdio to HTTP:

{
  "mcpServers": {
    "suralink-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.suralink.ai/mcp"]
    }
  }
}

Quit Claude Desktop completely and reopen it — the config is only read on startup. The tools icon should then list suralink-mcp.

Claude custom connector

On claude.ai, Cowork, and Claude Desktop you can also add this server as a custom connector (remote MCP). Claude reaches the server from Anthropic's cloud, so the endpoint must be publicly reachable. See Anthropic's guide: Get started with custom connectors using remote MCP.

Use this remote MCP URL:

https://mcp.suralink.ai/mcp

Pro and Max plans

1. Open Customize > Connectors.
2. Click +, then Add custom connector.
3. Paste the URL above.
4. Optionally open Advanced settings if you need to set an OAuth Client ID and Client Secret (most setups can leave these blank; the server publishes OAuth metadata for automatic discovery).
5. Click Add, then Connect to sign in with Suralink.

Team and Enterprise plans

Only an Owner (or Primary Owner) can add the connector for the organization:

1. Open Organization settings > Connectors.
2. Click Add, hover Custom, then select Web.
3. Paste the URL above (and optionally set Advanced OAuth settings).
4. Click Add.

After the Owner has added it, each member opens Customize > Connectors, finds the connector labeled Custom, and clicks Connect to authenticate.

Enable for a conversation

In a chat, use the + button (lower left) → Connectors, then toggle the Suralink connector on for that conversation. Ask the model to call ping to confirm the connection.

GitHub Copilot (VS Code)

GitHub Copilot Chat in VS Code (1.99+) can use this server in Agent mode. Official guide: Extending Copilot Chat with MCP.

If your Copilot seat comes from an organization or enterprise, an admin must enable the MCP servers in Copilot policy first.

Configuration

Add a workspace config at .vscode/mcp.json, or open the Command Palette and run MCP: Open User Configuration for a user-wide file:

{
  "servers": {
    "suralink-mcp": {
      "type": "http",
      "url": "https://mcp.suralink.ai/mcp",
      "oauth": {
        "clientId": "https://mcp.suralink.ai/.well-known/cimd.json"
      }
    }
  }
}

The oauth.clientId value is our published OAuth client metadata URL. VS Code uses it as a static client ID so you do not rely on dynamic client registration. Save the file, then use the Start control above the server entry (or click Auth if prompted) and complete the Suralink sign-in in the browser.

Use in chat

1. Open Copilot Chat and select Agent from the mode menu.
2. Click the tools icon and enable tools from suralink-mcp.
3. Ask the model to call ping to confirm the connection.

For other Copilot IDEs (Visual Studio, JetBrains, and so on), see the same GitHub guide linked above — configuration shapes differ by IDE.

Claude Code (CLI)

The easiest path is to let the CLI write the entry for you:

claude mcp add --transport http suralink-mcp https://mcp.suralink.ai/mcp

Add --scope user to make it available across all projects, or --scope project to commit it to .mcp.json in the current repo. To verify, run /mcp in a Claude Code session — you should see suralink-mcp as connected.

Verify the connection

Every client ships a ping tool for end-to-end checks:

Field	Value
Name	ping
Input	{ "message"?: string } (optional)
Output	Text content: pong or pong: <your message>
Purpose	Verify end-to-end connectivity to this server

Ask the model to call ping, or invoke it directly (for example /mcp__suralink-mcp__ping in Claude Code).