Give your agent native Linky access

What this is

Linky speaks the Model Context Protocol over the Streamable-HTTP transport. Authentication is a standard bearer API key, so the same key that works with the CLI or SDK works with every MCP harness. Scopes ship from access control: links:readis safe to drop into an agent's context; links:write lets an agent create and edit bundles; keys:admin can manage keys (rare).

Self-hosters get the same endpoint at /api/mcp on their deployment. No separate service.

1 · Create a read-only key

Go to /dashboard/api-keys, pick Read-only, set a rate limit (default 1000/hr is fine — it's a per-key cap on throughput), and copy the raw key. Read-only is the right starting scope for any agent that's just summarizing or linking to existing bundles — it can't delete, patch, or mint new keys.

Use links:write if you want the agent to create or update Linkies. Every key has its own rate-limit bucket so a runaway agent burns its own quota, not yours.

2 · Paste into your agent

Five snippets. Every snippet lists the default config path for the harness so you know where to drop it. Replace lkyu_YOUR_PREFIX.YOUR_SECRET with the key you just minted.

{
  "mcpServers": {
    "linky": {
      "url": "https://getalinky.com/api/mcp",
      "headers": {
        "Authorization": "Bearer lkyu_YOUR_PREFIX.YOUR_SECRET"
      }
    }
  }
}

{
  "mcpServers": {
    "linky": {
      "command": "npx",
      "args": ["-y", "getalinky", "mcp"],
      "env": {
        "LINKY_API_KEY": "lkyu_YOUR_PREFIX.YOUR_SECRET",
        "LINKY_BASE_URL": "https://getalinky.com"
      }
    }
  }
}

[mcp_servers.linky]
command = "npx"
args = ["-y", "getalinky", "mcp"]

[mcp_servers.linky.env]
LINKY_API_KEY = "lkyu_YOUR_PREFIX.YOUR_SECRET"
LINKY_BASE_URL = "https://getalinky.com"

{
  "mcpServers": [
    {
      "name": "linky",
      "transport": {
        "type": "streamable-http",
        "url": "https://getalinky.com/api/mcp",
        "headers": { "Authorization": "Bearer lkyu_YOUR_PREFIX.YOUR_SECRET" }
      }
    }
  ]
}

{
  "mcpServers": {
    "linky": {
      "url": "https://getalinky.com/api/mcp",
      "headers": { "Authorization": "Bearer lkyu_YOUR_PREFIX.YOUR_SECRET" }
    }
  }
}

3 · Verify with mcp-inspector

Before wiring an agent harness, confirm the endpoint is reachable and your key works. The official @modelcontextprotocol/inspector lists every tool and lets you call each one interactively.

npx @modelcontextprotocol/inspector \
  --url https://getalinky.com/api/mcp \
  --header "Authorization: Bearer lkyu_YOUR_PREFIX.YOUR_SECRET"

4 · Self-host

Replace https://getalinky.comwith your deployment's URL anywhere it appears above. No separate config, no extra service — /api/mcp ships in the same Next.js app that serves the dashboard. You can also kill the surface at runtime by setting LINKY_MCP_ENABLED=false (the route returns 503 with a clear message).

Tool reference (11)

Every tool mirrors one authed HTTP route. Scopes + roles are enforced server-side; an agent holding a links:read key will see all 11 tools but get a-32002 Forbidden error if it tries one that requires write or admin.

Troubleshooting

• 401 on connect — the bearer header is missing or the key was revoked. Mint a new one at /dashboard/api-keys.
• -32002 Forbidden on a tool call — the key lacks the required scope. Mint a new key with the scope the error message names, or use a higher-scope key.
• -32004 Rate limited— the per-key hourly bucket is spent. The error's data block carries retryAfterSeconds. Either wait it out or raise the limit by revoking and re-minting.
• 503 MCP_DISABLED — the operator flipped LINKY_MCP_ENABLED=false. Not a client-side bug; contact the operator.