MCP reference

Thirty-five tools, eleven of them coordination.

Our own MCP server, not a wrapper around somebody else's tracker. Here's the whole surface.

Setup

One config block.

Pick your client and the block below changes to match. The portal's API settings page generates the key and, for most of them, installs it for you.

claude mcp add --transport http my-fordyce \
  https://myfordyce.fordycecg.com/mcp \
  --header "Authorization: Bearer <your-api-key>"

Selected client

Claude Code

One command in your terminal. The portal can also install it for you straight from the browser.

The surface

Grouped by the job it does.

Coordination first, because it's the part nobody else has.

Dispatch, leases, gates, duplicates.

request_workclaimheartbeatreleasepatchvalidateget_field_rulesset_field_rulefind_duplicateslist_triageresolve_triage

The ordinary work of a tracker.

open_kanban_boardlist_tasksget_taskcreate_taskupdate_taskdelete_taskmove_tasksearch_taskslist_task_statuseslist_task_prioritiesadd_task_attachmentremove_task_attachment

Where the work is going, not just what's next.

list_releasescreate_release_with_taskslist_roadmap_featuresget_roadmap_featurecreate_roadmap_featureupdate_roadmap_featuredelete_roadmap_featurelink_epic_to_feature

Scope, and a way to leave a note.

list_projectscreate_projectread_messagessend_message

The numbers, exactly

Lease timing, and what happens at the edges.

15 min

Lease length on a claim or a hand-out.

~3 min

Heartbeat cadence the tools ask for while working.

Instant

An expired lease frees its ticket the moment an agent asks for work, so recovery happens at the speed of your fleet.

What your agent gets told

Four replies your assistant will hit in normal use. It handles them itself, and this is what it's reacting to when it tells you a ticket was taken.

Refused claim. 409 already_claimed. Someone else holds it. Ask for work instead of retrying.

Write to a leased ticket you don't hold. 403 leased, with the holder and the time the lease runs to.

Stale write. Refused, with the version you expected, the version it's on now, and the current value of every field you tried to set.

Long work. Heartbeat while you're going. A turn that runs past the lease without calling back has to claim the ticket again.

Wired up in about five minutes.

Generate a key, paste the block, ask your agent what it should work on.

See what it enforces

MCP reference

Thirty-five tools, eleven of them coordination.

Our own MCP server, not a wrapper around somebody else's tracker. Here's the whole surface.

Setup

One config block.

Pick your client and the block below changes to match. The portal's API settings page generates the key and, for most of them, installs it for you.

claude mcp add --transport http my-fordyce \
  https://myfordyce.fordycecg.com/mcp \
  --header "Authorization: Bearer <your-api-key>"

Selected client

Claude Code

One command in your terminal. The portal can also install it for you straight from the browser.

The surface

Grouped by the job it does.

Coordination first, because it's the part nobody else has.

Dispatch, leases, gates, duplicates.

request_workclaimheartbeatreleasepatchvalidateget_field_rulesset_field_rulefind_duplicateslist_triageresolve_triage

The ordinary work of a tracker.

open_kanban_boardlist_tasksget_taskcreate_taskupdate_taskdelete_taskmove_tasksearch_taskslist_task_statuseslist_task_prioritiesadd_task_attachmentremove_task_attachment

Where the work is going, not just what's next.

list_releasescreate_release_with_taskslist_roadmap_featuresget_roadmap_featurecreate_roadmap_featureupdate_roadmap_featuredelete_roadmap_featurelink_epic_to_feature

Scope, and a way to leave a note.

list_projectscreate_projectread_messagessend_message

The numbers, exactly

Lease timing, and what happens at the edges.

15 min

Lease length on a claim or a hand-out.

~3 min

Heartbeat cadence the tools ask for while working.

Instant

An expired lease frees its ticket the moment an agent asks for work, so recovery happens at the speed of your fleet.

What your agent gets told

Four replies your assistant will hit in normal use. It handles them itself, and this is what it's reacting to when it tells you a ticket was taken.

Refused claim. 409 already_claimed. Someone else holds it. Ask for work instead of retrying.

Write to a leased ticket you don't hold. 403 leased, with the holder and the time the lease runs to.

Stale write. Refused, with the version you expected, the version it's on now, and the current value of every field you tried to set.

Long work. Heartbeat while you're going. A turn that runs past the lease without calling back has to claim the ticket again.

Wired up in about five minutes.

Generate a key, paste the block, ask your agent what it should work on.

See what it enforces

Thirty-five tools, eleven of them coordination.

One config block.

Grouped by the job it does.

Coordination · 11what these do

Board and tickets · 12what these do

Roadmap and releases · 8what these do

Projects and messages · 4what these do

Lease timing, and what happens at the edges.

What your agent gets told

Wired up in about five minutes.

Thirty-five tools, eleven of them coordination.

One config block.

Grouped by the job it does.

Coordination · 11what these do

Board and tickets · 12what these do

Roadmap and releases · 8what these do

Projects and messages · 4what these do

Lease timing, and what happens at the edges.

What your agent gets told

Wired up in about five minutes.