Northflank MCP server

What the model can do

Northflank cloud platform: projects, services with their build and deployment status, builds, deployments with image and commit, jobs and their runs, and databases (addons); when you ask, can run or abort a job, pause or resume a cron schedule, restart, pause or resume a service, start or abort a build, restart, pause, resume or back up a database, and delete a service or job.

Reads

• northflank_list_projectsNorthflank projects: id, name, description and lifecycle status.
• northflank_list_servicesServices in a Northflank project: type (combined, build, deployment), the latest build status and deployment status with when each changed…
• northflank_list_jobsJobs in a Northflank project: manual or cron, whether a cron schedule is suspended, environment, CI/CD switched off, tags.
• northflank_job_runsRun history of a Northflank job: each run's status (SUCCESS, RUNNING, FAILED), start and end time, and retries allowed, with a count by status.
• northflank_service_buildsBuilds of a Northflank service: status, whether it succeeded, branch or pull request, commit, message, when it started and finished.
• northflank_service_deploymentsDeployments of a Northflank service, newest first: when, whether it is serving traffic, canary or stable, instances, image and tag…
• northflank_list_addonsDatabases and other addons in a Northflank project: type (postgresql, mongodb, redis…), status (running, paused, backup, failed…), environment, tags.

Acts, when you ask

These change something in Northflank. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• northflank_run_jobStarts a new run of a Northflank job now, with its saved settings (no overrides).
• northflank_abort_job_runAborts a running Northflank job run; the work it was doing stops part-way and cannot be resumed (run the job again instead).
• northflank_set_job_scheduleSuspends (suspended true) or resumes (false) the automatic schedule of a Northflank cron job; while suspended it runs only when started by hand.
• northflank_restart_serviceRestarts every running instance of a Northflank service, a brief interruption to whatever it serves.
• northflank_pause_servicePauses a Northflank service: its instances stop and it serves no traffic until resumed.
• northflank_resume_serviceResumes a paused Northflank service, starting billable instances again (optionally a given number, and with or without the autoscaling it had).
• northflank_start_buildStarts a new build of a Northflank service.
• northflank_abort_buildAborts a Northflank service build in progress; nothing from it is deployed.
• northflank_restart_addonRestarts a Northflank database addon; connections to it drop while it comes back.
• northflank_pause_addonPauses a Northflank database addon: it stops and nothing can connect until it is resumed (its data is kept).
• northflank_resume_addonResumes a paused Northflank database addon, which is billed again while it runs.
• northflank_backup_addonStarts a backup of a running Northflank database addon now: a snapshot by default, or a native dump where the database supports one.
• northflank_delete_servicePermanently deletes a Northflank service, its builds and deployments; whatever it served goes offline.
• northflank_delete_jobPermanently deletes a Northflank job and its run history; a cron job stops running.

Connect it

First connect Northflank on Dashboard → Connections, then add Memtro to your client once. The Northflank tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Northflank connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Is the API service deployed and running?
• › Which builds failed today?
• › When did the nightly import job last succeed?
• › Which databases in the production project are paused?
• › Restart the worker service.

Questions

Is this an official Northflank MCP server?

No. It is Memtro's MCP server with Memtro's Northflank connector behind it: the connector reads Northflank through its API with the credentials you connect on Dashboard → Connections, and Northflank publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Northflank?

Only when you ask, and only what it has been granted: run a job now; abort a running job run; pause or resume a cron job's schedule; restart a service; pause a service (takes it offline); resume a paused service; start a build of a service from a branch, pull request or commit; abort a service build; restart a database addon; pause a database addon; resume a paused database addon; back up a database addon now; delete a service; delete a job. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server