MCP Server

Copy page

MCP Server

link.sc ships a hosted Model Context Protocol server so AI assistants like Claude can fetch web pages and search Google directly, using your link.sc API key. No local install: it is a remote MCP endpoint over HTTP.

Endpoint: https://mcp.link.sc/

Get your key at link.sc/dashboard/keys. It starts with lsc_. Then pick your client below.

Configure it in Claude

Claude Desktop

Edit claude_desktop_config.json and add the server under mcpServers, then fully quit and reopen Claude Desktop:

Code
 
{
  "mcpServers": {
    "linksc": {
      "url": "https://mcp.link.sc/",
      "transport": "http",
      "headers": {
        "x-api-key": "lsc_your_api_key"
      }
    }
  }
}

Config file locations:

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

If the file already has other servers, add "linksc" as another key inside the existing mcpServers object rather than creating a second one. After restarting, you should see linksc with a tools icon in the chat box.

Claude Code

Add it with one command (project scope by default; use -s user to make it available in every project):

Code
 
claude mcp add --transport http linksc https://mcp.link.sc/ \
  --header "x-api-key: lsc_your_api_key"

Confirm it registered and is reachable:

Code
 
claude mcp list
# linksc  ✓ connected

To remove it later: claude mcp remove linksc.

Claude.ai (web, Pro / Max / Team / Enterprise)

Go to Settings → Connectors → Add custom connector, give it a name (linksc), and enter the URL https://mcp.link.sc/. Enable it for your chats.

Verify it works

Ask Claude a question that needs the live web, naming the tool so it reaches for it:

"Using linksc, search for the latest Claude model releases and list the top three results with links."

Claude should call the search tool and answer from the results. For a specific page:

"Using linksc, fetch https://example.com and summarize it."

Tools

Tool	Description	Required args
fetch	Fetch a URL and return clean markdown. Renders JavaScript and parses Google/Bing result pages.	url
search	Search Google; returns organic results, People Also Ask, and shopping results as markdown.	q

fetch also accepts render_js, wait_for, wait_for_selector, timeout, headers, and cookies.

Protocol

The server speaks JSON-RPC 2.0 over the Streamable HTTP transport. It supports initialize, tools/list, tools/call, and ping. Authentication is the same x-api-key header as the REST API, and calls count toward the same quota.

Try it with curl

List the available tools (no key required for discovery):

Code
 
curl -X POST https://mcp.link.sc/ \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Call the search tool:

Code
 
curl -X POST https://mcp.link.sc/ \
  -H "Content-Type: application/json" \
  -H "x-api-key: lsc_your_api_key" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": { "name": "search", "arguments": { "q": "anthropic claude" } }
  }'

Billing

MCP tool calls are billed exactly like REST API requests: one request per fetch or search. Track usage at link.sc/dashboard/usage.