northflank
Server Details
Inspect and control your Northflank projects, services, jobs, and builds from your AI assistant.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
17 toolsnorthflank_get_addonGet addonRead-onlyInspect
Get details and status of a single addon. GET /v1/projects/{projectId}/addons/{addonId}.
| Name | Required | Description | Default |
|---|---|---|---|
| addonId | Yes | Addon id (from northflank_list_addons). | |
| projectId | Yes | Project id. |
northflank_get_jobGet jobRead-onlyInspect
Get details of a single job, including build/deploy config and cron schedule. GET /v1/projects/{projectId}/jobs/{jobId}.
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | Job id (from northflank_list_jobs). | |
| projectId | Yes | Project id. |
northflank_get_projectGet projectRead-onlyInspect
Get details of a single project, including region, cluster and associated services/jobs/addons. GET /v1/projects/{projectId}.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | Project id (from northflank_list_projects). |
northflank_get_serviceGet serviceRead-onlyInspect
Get details and current status of a single service. GET /v1/projects/{projectId}/services/{serviceId}.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | Project id. | |
| serviceId | Yes | Service id (from northflank_list_services). |
northflank_get_service_metricsGet service metricsRead-onlyInspect
Get CPU / memory metrics for a service's containers. GET /v1/projects/{projectId}/services/{serviceId}/metrics. Use queryType=single (default) for a current snapshot or queryType=range with duration/startTime/endTime.
| Name | Required | Description | Default |
|---|---|---|---|
| time | No | Point-in-time for queryType=single. | |
| endTime | No | Range end. | |
| duration | No | Range duration in seconds (alternative to startTime/endTime). | |
| projectId | Yes | Project id. | |
| queryType | No | single = point-in-time (default), range = time series. | |
| serviceId | Yes | Service id. | |
| startTime | No | Range start (unix ms/seconds per API). | |
| metricTypes | No | Which metrics to return; defaults to all if omitted. |
northflank_list_addonsList addonsRead-onlyInspect
List addons (managed databases / services) in a project with their status. GET /v1/projects/{projectId}/addons.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| per_page | No | Results per page (max 100). | |
| projectId | Yes | Project id. |
northflank_list_domainsList domainsRead-onlyInspect
List custom domains for the account (or a team), with verification status. GET /v1/domains (team: GET /v1/teams/{teamId}/domains).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| teamId | No | Optional team id to scope to a team's domains. | |
| per_page | No | Results per page (max 100). |
northflank_list_jobsList jobsRead-onlyInspect
List jobs (manual / cron) in a project. GET /v1/projects/{projectId}/jobs.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| per_page | No | Results per page (max 100). | |
| projectId | Yes | Project id. |
northflank_list_projectsList projectsRead-onlyInspect
List projects for the authenticated token (or a specific team). Good first call to discover project ids. GET /v1/projects (team: GET /v1/teams/{teamId}/projects).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| teamId | No | Optional team id to scope to a team's projects. | |
| per_page | No | Results per page (max 100). |
northflank_list_secret_groupsList secret groupsRead-onlyInspect
List a project's secret groups — METADATA ONLY (id, name, type, priority, restrictions). Does NOT return secret values. GET /v1/projects/{projectId}/secrets.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| per_page | No | Results per page (max 100). | |
| projectId | Yes | Project id. |
northflank_list_service_buildsList service buildsRead-onlyInspect
List a build service's build runs / history (branch, sha, status, timestamps). GET /v1/projects/{projectId}/services/{serviceId}/build.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| per_page | No | Results per page (max 100). | |
| projectId | Yes | Project id. | |
| serviceId | Yes | Service id of a build/combined service. |
northflank_list_servicesList servicesRead-onlyInspect
List services in a project (build / deployment / combined) with their build+deployment status. GET /v1/projects/{projectId}/services.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to access. | |
| cursor | No | Cursor from a previous page's pagination.cursor to fetch the next page. | |
| per_page | No | Results per page (max 100). | |
| projectId | Yes | Project id. |
northflank_pause_servicePause service (mutates infra)DestructiveInspect
MUTATING: pause a service, scaling it to zero running instances. POST /v1/projects/{projectId}/services/{serviceId}/pause.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | Project id. | |
| serviceId | Yes | Service id. |
northflank_restart_serviceRestart service (mutates infra)DestructiveInspect
MUTATING: restart all running containers of a service. POST /v1/projects/{projectId}/services/{serviceId}/restart.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | Project id. | |
| serviceId | Yes | Service id. |
northflank_resume_serviceResume service (mutates infra)DestructiveInspect
MUTATING: resume a paused service. Optionally set the instance count and CI/CD/autoscaling state to restore. POST /v1/projects/{projectId}/services/{serviceId}/resume.
| Name | Required | Description | Default |
|---|---|---|---|
| instances | No | Instances to scale to on resume. | |
| projectId | Yes | Project id. | |
| serviceId | Yes | Service id. | |
| disabledCD | No | Whether CD should be disabled after resume. | |
| disabledCI | No | Whether CI should be disabled after resume. | |
| enableAutoscaling | No | Restore autoscaling (defaults to the state captured when paused). |
northflank_scale_serviceScale service (mutates infra)DestructiveInspect
MUTATING: set the number of running instances (replicas) for a service. POST /v1/projects/{projectId}/services/{serviceId}/scale.
| Name | Required | Description | Default |
|---|---|---|---|
| instances | Yes | Desired number of instances / replicas. | |
| projectId | Yes | Project id. | |
| serviceId | Yes | Service id. |
northflank_trigger_service_buildTrigger service build (mutates infra)DestructiveInspect
MUTATING: start a new build for a build/combined service. With an empty body it builds the latest commit on the linked branch; optionally target a branch, a specific commit sha, or a pull request. POST /v1/projects/{projectId}/services/{serviceId}/build.
| Name | Required | Description | Default |
|---|---|---|---|
| sha | No | Specific commit SHA to build from the branch. | |
| branch | No | Branch to build (defaults to the service's linked branch). | |
| projectId | Yes | Project id. | |
| serviceId | Yes | Build/combined service id. | |
| pullRequestId | No | Build the latest commit of this pull request's branch. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!