A hosted backlog coding agents claim work from: one ticket per agent, finished work back to review.
Connect Remote server
claude mcp add --transport http my-fordyce https://myfordyce.fordycecg.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"my-fordyce": {
"url": "https://myfordyce.fordycecg.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"my-fordyce": {
"type": "http",
"url": "https://myfordyce.fordycecg.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://myfordyce.fordycecg.com/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. OAuth sign-in is the default: connect with the URL alone and sign in when asked. To use an API key instead, send it here as 'Bearer fdy_...'. Mint one on the Connect page at https://myfordyce.fordycecg.com/connect. Keys are accepted in this header only, never in the URL. |
Details
| Endpoint | https://myfordyce.fordycecg.com/mcp (Streamable HTTP) |
| First published | 4 Nov 2026 |
| Last updated | 4 Nov 2026 |
| Registry name | com.fordycecg/my-fordyce |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
