MCP server
Connect Claude, Cursor or any MCP client to SetFork.
SetFork ships a remote MCP server (Streamable HTTP), so AI agents can work with lists as first-class tools.
Endpoint
https://setfork.com/api/mcp
Authorization: Bearer sf_…Create a token in Settings → API & MCP access — see API tokens.
Connect from Claude Code
claude mcp add --transport http setfork https://setfork.com/api/mcp \
--header "Authorization: Bearer sf_YOUR_TOKEN"Or in any MCP client that supports remote servers: URL
https://setfork.com/api/mcp, header Authorization: Bearer sf_….
Tools
| Tool | What it does |
|---|---|
search_lists | Search public lists by keywords |
get_list | Fetch a list with all steps of its current version |
create_list | Create a new list — it appears as a private draft |
update_list | Update a list you own |
The same safety model as the UI applies: agents create drafts, humans publish; only the owner (or a collaborator) can modify a list.
Why this matters
Agents can both consume canonical checklists ("fetch the team's deploy runbook and follow it") and produce them ("turn this incident post-mortem into a reusable checklist and save it as a draft for review").