Developer · Remote MCP server
Builderforce
Run tickets, boards, OKRs and cloud coding agents in your Builderforce workspace.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.SeanHogg/builderforce- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-09
- Updated
- 2026-08-09
- Publisher
- SeanHogg (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/SeanHogg) · how
- Website
- builderforce.ai
- Repository
- github.com/SeanHogg/Builderforce.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.builderforce.ai/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Builderforce
Builderforce is a remote MCP server: there is nothing to install. Its endpoint is https://api.builderforce.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from SeanHogg (GitHub)
| Server | Runs |
|---|---|
| Builderforce MemoryToken-saving persistent memory for AI agents: recall durable facts instead of re-reading files. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| BugfenderAccess Bugfender logs, crashes, devices, and user feedback from MCP-enabled clients. | Local · stdio |
| Bugherd MCPBugHerd API v2 integration - 37 tools for projects, tasks, comments, and webhooks. | Local · stdio |
| BugProofCapture, replay, and debug failures with portable, executable bug artifacts. | Local · stdio |
| BuildStart a NorthernGo cloud build from Cursor, Claude or Codex. EU database included. | Remote · HTTPLive check: sign-in required |
| Buildkite MCP ServerMCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors. | Local · stdio |
| BuildPulseBuildPulse CI test analytics for AI agents - flaky tests, CI failures, flakiness, and code coverage. | Remote & Local · HTTP, stdioLive check: sign-in required |
| BuildtreeUpload Android and iOS builds to buildtree and get install links, QR codes and tester feedback. | Local · stdio |
| Buildutilities MCPDeterministic dev utilities: UUIDs, hashes, encoding, JWT, cron, regex. No network, no API key. | Local · stdio |