Developers / MCP server
MCP server
SLINK speaks the Model Context Protocol in both directions.
SLINK as an MCP server#
Expose SLINK's actions to Claude, Cursor or your own agent:
claude mcp add --transport http slink https://api.slink.w9li.dev/mcp \
--header "Authorization: Bearer slk_…"Tools include chat with the user's context, creating and activating automations, reading the catalog and integrations, and the owner's platform tools when the token belongs to an admin.
SLINK as an MCP client#
Any user can link an MCP server from the app: paste its URL, SLINK connects, lists its tools, opens the server's OAuth consent if it asks for one, and the assistant can use those tools in chat. Cloudflare's hosted MCP was linked this way in production.
MCP servers that require OAuth get SLINK's public callback; the consent screen shows the SLINK identity.
Tools reference#
| Tool | Arguments | Notes |
|---|---|---|
chat | message | Answers with the user's context, memory and integrations |
create_automation | text | Same path as /assist → /confirm |
list_automations | — | |
catalog | — | Services and states |
integrations | — | What is linked |
platform_* | various | Owner only: status, people, errors, gaps |