Build

com.northerngoPublished by northerngo.comv1.0.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

NorthernGo Build lets an assistant start a NorthernGo cloud build from Cursor, Claude or Codex, with an EU database included.

What you can do
Start a NorthernGo cloud build from a connected AI assistant such as Cursor, Claude or Codex, using the provider's hosted build service. The manifest lists no individual tools, so the exact operations available are not documented here. The service is described as including an EU database.
When to use it
Useful when you already work with NorthernGo and want to trigger its cloud builds from inside an AI assistant instead of switching to the provider's own interface.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address. A bearer token is required in the Authorization header, using an ngmcp_ key obtained from My Projects, More, MCP in the NorthernGo account. No environment variables or local packages are declared.
Before you install
The Authorization header carries a secret API key; keep it private and do not share it. The server starts cloud builds, which may consume paid resources or change project state. The manifest lists no tools, so review what actions it can take before connecting.

Installation

In SourceWeft

  1. Open Build in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.northerngo%2Fbuild/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "build": {
      "type": "http",
      "url": "https://northerngo-backend.onrender.com/api/ng-mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 19, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.