Run tickets, boards, OKRs and cloud coding agents in your Builderforce workspace
Connect Remote server
claude mcp add --transport http builderforce https://api.builderforce.ai/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"builderforce": {
"url": "https://api.builderforce.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"builderforce": {
"type": "http",
"url": "https://api.builderforce.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.builderforce.ai/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 |
|---|---|
AuthorizationRequired, secret | Bearer <your Builderforce tenant API key>. Create one at https://builderforce.ai/settings/api-keys — the key's tenant is the scope of every tool call. |
Details
| Endpoint | https://api.builderforce.ai/mcp (Streamable HTTP) |
| First published | 9 Aug 2026 |
| Last updated | 9 Aug 2026 |
| Registry name | io.github.SeanHogg/builderforce |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
