Uselink MCP — Setup & Usage Guide

Connect Uselink to your AI coding assistant (Claude Code, Cursor, Windsurf, etc.) through the Model Context Protocol (MCP). Once connected, your AI can publish documents, manage projects, and share links — directly from your editor.

Uselink Developer settings — API key created with the Claude MCP install command ready to copy

The Uselink MCP server exposes Uselink’s document, project, and folder APIs as tools your AI assistant can call. Instead of copy-pasting content into a browser, you tell the AI: “publish this as a doc” — and it does.

Typical use cases:

Prerequisites

Step 1 — Generate a Personal Access Token (PAT)

  1. Sign in to uselink.app
  2. Open Settings → Developer → API Keys
  3. Click Create new key
  4. Give it a name (e.g. claude-code-mcp) and select the scopes you need:
    • documents:read, documents:write — required
    • projects:read, projects:write — required for project/folder management
    • folders:write — required to create folders
    • comments:read, comments:write — optional, for reading/replying to comments
  5. Copy the token (starts with ulk_pat_…). Store it somewhere safe — you can’t view it again.

The Developer page surfaces a ready-to-copy install command the moment a token is created — see the screenshot above. Both the claude mcp add snippet and a curl smoke test are pre-filled with your token.

Step 2 — Install the MCP Server

Claude Code

Run this in your terminal (replace the token with yours):

claude mcp add uselink \
  --env USELINK_API_KEY=ulk_pat_your_token_here \
  -- npx -y @uselink/mcp

That’s it. Restart Claude Code — the uselink server should now appear in your MCP server list.

Cursor / Windsurf / Claude Desktop

Edit your MCP config file (location varies by editor — usually ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, or ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "uselink": {
      "command": "npx",
      "args": ["-y", "@uselink/mcp"],
      "env": {
        "USELINK_API_KEY": "ulk_pat_your_token_here"
      }
    }
  }
}

Save and restart your editor.

Step 3 — Verify the Connection

In your AI client, ask:

“List my Uselink projects.”

If the connection works, the AI will call uselink_list_projects and return your project list. If you get an authentication error, double-check the token and its scopes.

You can also smoke-test with curl using the snippet shown on the Developer page:

curl -H "Authorization: Bearer ulk_pat_your_token_here" \
  https://api.uselink.app/api/v1/external/documents/list

Available Tools

The MCP server exposes ~40 tools. The most common ones:

Documents

Projects & Folders

Comments

Assets

Common Workflows

1. Publish an architecture note

“Take the contents of docs/architecture.md and publish it to my Uselink as ‘API Architecture v2’.”

The AI reads the file, calls uselink_create_document with the Markdown content, then calls uselink_publish_document. You get back a shareable URL.

2. Share a code review report with PMs

“Publish the review summary I just wrote into the Engineering project, folder ‘reviews’, titled ‘Q2 Auth Refactor Review’.”

The AI finds the project and folder, creates the doc inside, and publishes it.

3. Triage comments

“Show me unresolved comments on my last 3 published docs.”

The AI lists recent docs, calls uselink_list_comments on each, filters by status, and reports back.

Troubleshooting

Symptom Fix
Insufficient scopes The PAT is missing a scope. Regenerate with the scopes listed above.
Unauthorized Token is wrong or expired. Verify USELINK_API_KEY is set correctly.
Tools don’t appear after install Restart your AI client. MCP servers load at startup.
Token change doesn’t take effect MCP reads USELINK_API_KEY at startup. Restart the client after updating the token.
npx hangs on first run First run downloads the package. Subsequent runs are fast. Allow ~30s.

Security Notes

Resources

Happy publishing.