Developer · Remote MCP server
Build
Start a NorthernGo cloud build from Cursor, Claude or Codex. EU database included.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.northerngo/build- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- com.northerngo
- Namespace
- Namespace verified by the MCP Registry via the domain northerngo.com · how
- Website
- northerngo.com/resources/build-with-claude-cursor-chatgpt/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://northerngo-backend.onrender.com/api/ng-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
- Checked on
- 2026-10-05
How to connect Build
Build is a remote MCP server: there is nothing to install. Its endpoint is https://northerngo-backend.onrender.com/api/ng-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 developer servers
| Server | Runs |
|---|---|
| bugbrain.techBugBrain QA platform for AI coding tools: autonomous exploratory testing, test plans, a11y audits. | Local · stdio |
| 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 |
| BuilderforceRun tickets, boards, OKRs and cloud coding agents in your Builderforce workspace. | 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 |