LinkList — Connect · Cursor

Connect LinkList to Cursor.

Cursor speaks streamable HTTP directly, so the endpoint needs no bridge. Drop the URL and your key into mcp.json and the tools are available to the agent.

Verified against the live endpoint on 2026-07-27.

01 — Get a key

One key per agent or machine. It reads every collection in your account, and can add sources unless you turn that off.

Free · 100 queries/day · no card

No account yet? The demo collection publishes a live read-only key you can paste in place of your own. Query the demo collection first

02 — Add the endpoint

The global file covers every project. Create it if it is not there, then approve the server when Cursor asks — editing the file resets that approval.

FILE ~/.cursor/mcp.json

{
"mcpServers": {
"linklist": {
"url": "https://linklist.io/mcp",
"headers": {
"Authorization": "Bearer llk_YOUR_KEY"
}
}
}
}

03 — Check it connected

Cursor lists the server under Settings, then MCP. The command-line agent reports the same state.

$ cursor-agent mcp list

EXPECTED OUTPUT

linklist: ready

Also works

A project-level file keeps the endpoint with the repository. Your key is in it literally, so add .cursor/mcp.json to .gitignore before you commit anything. Cursor's documentation shows ${env:VAR} interpolation for header values; it did not expand when tested on 2026-07-27, and the unexpanded string was sent as the token.

FILE .cursor/mcp.json

{
"mcpServers": {
"linklist": {
"url": "https://linklist.io/mcp",
"headers": {
"Authorization": "Bearer llk_YOUR_KEY"
}
}
}
}

04 — Ask your agent

Ask something your sources cover. Every passage comes back with its URL and the date it was fetched, so the answer is checkable.

> which payroll APIs handle contractor payments?
  search_sources → 8 citations
  [1] highline.co · fetched 2026-07-27 · link_id 7
  [2] atomic.financial · fetched 2026-07-27 · link_id 1
  [3] truv.com · fetched 2026-07-27 · link_id 3

What your agent can call

Five tools, three of them read-only.

Every key lists all five. A read-only key still sees the two write tools and refuses the call, so an agent that tries to add a source gets an error rather than silently writing.

  • search_sources Search vetted sources
  • list_collections List available collections
  • get_source Get full source text
  • add_source Add a source to a collection
  • create_collection Create a collection

Protocol 2025-11-25, negotiated down to 2025-06-18 and 2025-03-26 for older clients.

When it does not work

Invalid OAuth error response: SyntaxError: Unexpected token '<'
This is a rejected key, not an OAuth problem. The endpoint returns 401, Cursor reads that as a challenge to start OAuth, and then fails on the response it gets while looking for the metadata. Fix the token and the message goes away.
MCP server has not been approved
Approve it in Settings, then MCP, or run cursor-agent mcp enable linklist. Approval is tied to the file contents, so it has to be given again after any edit.
The key is sitting in a file I want to commit
Keep it out of the repository and use the global file at ~/.cursor/mcp.json instead. Environment interpolation in headers is not a working substitute — see above. A key you have already committed should be revoked and replaced.

Other clients

The endpoint is the same for every client that speaks MCP over streamable HTTP. Only the file it goes in changes.

MCP starter pack

Verified setup configs for every client.

Copy-paste configuration for Claude Code, Claude Desktop and Cursor, plus the eval harness so you can measure your own retrieval.

One email with the pack. No sequence.

Point your agent at sources you trust.

Free tier, no card. The endpoint is live now.