Developer · Remote MCP server

Build

Start a NorthernGo cloud build from Cursor, Claude or Codex. EU database included.

Visit Build's website

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

TransportURLHeaders declared
Streamable HTTPhttps://northerngo-backend.onrender.com/api/ng-mcpAuthorization (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 the live check works

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

All 5,152 →
ServerRunsEndpoint or package
bugbrain.techBugBrain QA platform for AI coding tools: autonomous exploratory testing, test plans, a11y audits.Local · stdionpm: @bugbrain/mcp
BugfenderAccess Bugfender logs, crashes, devices, and user feedback from MCP-enabled clients.Local · stdionpm: @bugfender/mcp
Bugherd MCPBugHerd API v2 integration - 37 tools for projects, tasks, comments, and webhooks.Local · stdionpm: bugherd-mcp
BugProofCapture, replay, and debug failures with portable, executable bug artifacts.Local · stdionpm: bugproof
BuilderforceRun tickets, boards, OKRs and cloud coding agents in your Builderforce workspace.Remote · HTTPLive check: sign-in requiredapi.builderforce.ai
Buildkite MCP ServerMCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.Local · stdioOCI image (Docker): ghcr.io/buildkite/buildkite-mcp-server:0.7.0
BuildPulseBuildPulse CI test analytics for AI agents - flaky tests, CI failures, flakiness, and code coverage.Remote & Local · HTTP, stdioLive check: sign-in requiredmcp.buildpulse.io
BuildtreeUpload Android and iOS builds to buildtree and get install links, QR codes and tester feedback.Local · stdionpm: @buildtree/mcp