Skip to content
Fredrin
Documentation

Build on Fredrin

MCP server

Point any MCP-compatible client at your board and it can manage tickets directly, without you switching windows to file one.

Connect

  • Endpoint: https://www.fredrin.com/api/mcp
  • Transport: Streamable HTTP, stateless, one POST per call.
  • Auth: Authorization: Bearer fredrin_live_… from Settings → API keys.

Add it to ~/.claude.json, or your project's .mcp.json:

{
  "mcpServers": {
    "fredrin": {
      "type": "http",
      "url": "https://www.fredrin.com/api/mcp",
      "headers": {
        "Authorization": "Bearer fredrin_live_xxxxxxxxxxxx"
      }
    }
  }
}

Tell your agent to use it

Worth one paragraph in your AGENTS.md, because otherwise an agent will reach for gh issue create out of habit:

## Tickets

Use the `fredrin` MCP server for all ticket management: listing, creating,
updating and moving tickets across the board. Call the tools directly rather
than asking me to do it by hand.

A Fredrin ticket runs an AI Worker in its own branch and worktree. It is not
a GitHub Issue. When I say "make a ticket" or "add this to the board", create
it through the fredrin tools, never with gh issue create, unless I explicitly
say "GitHub issue".

That is the whole integration.

Tools

ToolPurpose
list_workspacesWorkspaces the key can reach.
list_projectsProjects in a workspace.
create_project · update_project · delete_projectManage projects.
list_statusesThe board's columns.
list_ticketsTickets in a project, filterable.
get_ticketOne ticket.
create_ticketCreate under a project and status.
update_ticketPatch title, description, priority, assignee, due date, labels.
set_ticket_planWrite the ticket's structured plan. Distinct from its description.
move_ticketMove across columns, with ordering anchors.
list_comments · create_comment · update_comment · delete_commentTicket comments.
upload_attachmentAttach a file to a ticket.

Note that set_ticket_plan and update_ticket write different fields. The plan is its own structured document, not part of the description.

Security

  • Keys are SHA-256 hashed at rest and compared in constant time.
  • A workspace-scoped key can only see and touch its workspace.
  • Every tool call re-authenticates, because the server is stateless.

Next steps

  • REST API - the full surface.
  • Skills - a different way to teach an agent your procedures.