Northflank integration
Northflank platform API. Create and delete projects, list the services, jobs and addons inside them, read a service in full, scale, restart and rebuild it, list its builds, run a job and follow its runs, read the connection credentials of a managed database addon, list secret groups, and pull container logs, regions, billing usage and the permissions of the token in use. Every response wraps its payload in a data object, with a pagination object beside it on the paged calls.
Say what should happen.
The workflow builds itself.
Common Northflank use cases
- tearing down a preview environment
- creating a project for a new application
- removing a service replaced by a new one
- scaling up replicas before a traffic peak
- triggering a migration job after a deploy
- finding the job id before triggering a run
- choosing a region before creating a project
- auditing which secret groups a project defines
- rebuilding a service after a dependency change
- waiting for a build to finish before deploying
What you can do with Northflank
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Service, 5 operations
delete_serviceDelete serviceDELETEDeletes a service from a project.get_serviceGet serviceGETReturns a service with its build settings, billing plan and current status.list_servicesList servicesGETLists the services of a project with their type and current status.restart_serviceRestart servicePOSTRestarts the containers of a service without rebuilding it.scale_serviceScale servicePOSTChanges the instance count, plan or storage of a service, through an operation Northflank marks deprecated.
Project, 4 operations
create_projectCreate projectPOSTCreates a project in a region or on a bring your own cloud cluster.delete_projectDelete projectDELETEDeletes a project, optionally with everything inside it.get_projectGet projectGETReturns a project together with the services, jobs and addons it contains.list_projectsList projectsGETLists projects with their identifiers and descriptions.
Build, 2 operations
list_service_buildsList service buildsGETLists the builds of a service, newest first.start_service_buildStart service buildPOSTBuilds a service from a commit, a branch or a pull request.
Job run, 2 operations
list_job_runsList job runsGETLists the run history of a job with the outcome of each run.run_jobRun jobPOSTStarts a job run, optionally overriding its environment for this run only.
Addon, 1 operation
list_addonsList addonsGETLists the managed databases and other addons of a project.
Addon credential, 1 operation
get_addon_credentialsGet addon credentialsGETReturns the secrets and connection strings needed to reach an addon.
Auth, 1 operation
get_auth_infoGet auth infoGETReturns which entity the token belongs to, its role and its effective permissions.
Billing usage, 1 operation
get_billing_usageGet billing usageGETReturns hourly resource usage entries, most recent first.
Job, 1 operation
list_jobsList jobsGETLists the manual and cron jobs of a project.
Log, 1 operation
get_service_logsGet service logsGETReturns container log lines of a service over a time window.
Region, 1 operation
list_regionsList regionsGETLists the regions a project can be created in.
Secret, 1 operation
list_project_secretsList project secretsGETLists the secret groups of a project with their scope and priority.
Northflank API rate limits
- 1,000 requests per hour
Default account limit is 1000 requests per hour, counted from the first request and reset one hour later. The remaining budget is reported on every response in x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset.
These are the limits Northflank documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Northflank documentation for current values.
Use Northflank from Claude Code, Cursor or Codex
Connect Northflank in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Northflank operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Northflank
- Create your workspace
Sign up free. Nothing to install.
- Connect Northflank once
Add your Northflank connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Northflank integration FAQ
What can you do with the Northflank integration?
LiveContext exposes 21 operations on Northflank, covering service, project, build and job run. Common uses include tearing down a preview environment, creating a project for a new application and removing a service replaced by a new one.
What are the Northflank API rate limits?
Northflank documents 1,000 requests per hour. Default account limit is 1000 requests per hour, counted from the first request and reset one hour later. The remaining budget is reported on every response in x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset. Limits are set by Northflank and can depend on your plan.
