Portal URLs

Everything the Ankra CLI, API and MCP tools change is also visible in the Ankra web app at platform.ankra.app/next. Every page has a stable address, so you can bookmark it, paste it into a ticket, or have a script or an AI client hand it to a teammate. This page explains how those addresses are built and lists the main ones. Links on this page use https://platform.ankra.app. If you sign in to Ankra at a different address, use that one instead. Opening a link needs a signed-in session in the organisation that owns the resource. Classic Ankra, the previous web interface, used addresses under /organisation/.... Ankra is replacing it, so use the addresses on this page in scripts, runbooks and agent instructions.

How addresses are built

Every page is under /next. A cluster’s overview, for example, is https://platform.ankra.app/next/clusters/<cluster-id>.
The organisation comes from your session. A page shows the organisation you have selected in the organisation picker at the top of the side menu. No address puts the organisation id in its path.
?org= opens a link in the right organisation. Links Ankra hands you add ?org=<organisation-id>. If that is not the organisation you are working in, the page says which organisation the record belongs to and offers to switch to it, then opens the same address there. If you are not a member of that organisation, the page says so.
?project= names the project beside it. The same links add ?project=<project-id>, so a link to a cluster in another project opens in that project rather than in the one you last worked in. If that is not your current project, the page offers to switch to it. ankra commands that print a link add it too.
Clusters are addressed by id, not by name. Every cluster page starts with /next/clusters/<cluster-id>, however the cluster was created. ankra cluster info -o json, ankra cluster list -o json and the list_clusters MCP tool all return the id.
Stacks and add-ons are addressed by name within their cluster. Kubernetes resources are addressed by namespace and name, or by name alone for one that belongs to no namespace, such as a node. URL-encode a name that contains anything other than letters, digits, -, _ and ..

You rarely need to build these URLs yourself. ankra commands print the link to what they create or list, and MCP clients can call get_portal_url.

Organisation pages

Page	Path
Home and Ask Ankra	`/next`
Notifications	`/next/notifications`
Clusters	`/next/clusters`
Create a cluster	`/next/clusters/new` (one provider: `?provider=<provider>`)
Import a cluster	`/next/clusters/import`
Applications	`/next/applications`
Stack profiles	`/next/stack-profiles`
Add-on catalogue (Helm charts)	`/next/services/helm`
Credentials	`/next/credentials`
Your API tokens (CLI and MCP)	`/next/account/api`
Cloud cost	`/next/cost`
Security Center	`/next/security`
Security findings	`/next/security?tab=explore`
One CVE	`/next/security/advisories/<cve-id>`
Members	`/next/organisation/people`
Service tokens	`/next/organisation/automation#service-tokens`
Organisation settings	`/next/organisation`
Domains and DNS	`/next/organisation/domains`
Backup vaults	`/next/organisation/storage#backup-vaults`
Plan and billing	`/next/organisation/billing`

The Security Center names its views with ?tab=. An application’s page and a pod’s page name theirs with ?view=.

Cluster pages

Every path below starts with /next/clusters/<cluster-id>. That address on its own is the cluster’s overview.

Page	Path after `<cluster-id>`
Stacks	`/stacks`
One stack (editor)	`/stacks/<stack-name>`
Add-ons	`/addons`
One add-on	`/addons/<addon-name>`
Operations	`/operations`
One operation	`/operations/<operation-id>`
Node groups and machines	`/node-groups`
Kubernetes nodes	`/kubernetes/nodes`
One Kubernetes node	`/kubernetes/nodes/<node-name>`
Namespaces	`/kubernetes/namespaces`
Pods	`/kubernetes/pods`
One pod	`/kubernetes/pods/<namespace>/<pod-name>`
A shell in one pod	`/kubernetes/pods/<namespace>/<pod-name>?view=exec`
One Deployment	`/kubernetes/workloads/deployments/<namespace>/<name>`
One StatefulSet	`/kubernetes/workloads/stateful-sets/<namespace>/<name>`
One DaemonSet	`/kubernetes/workloads/daemon-sets/<namespace>/<name>`
One Job / CronJob	`/kubernetes/workloads/jobs/<namespace>/<name>`, `/kubernetes/workloads/cron-jobs/<namespace>/<name>`
Events	`/kubernetes/events`
Logs	`/kubernetes/logs`
Metrics	`/metrics`
Backups	`/backups`
Settings	`/settings`
GitOps, credentials and variables settings	`/settings/gitops`, `/settings/credentials`, `/settings/variables`
Access	`/access`

A cluster’s security findings open in the Security Center, scoped to that cluster: /next/security?scope=cluster&cluster=<cluster-id>. Ankra has no page yet for the list of resources Ankra manages on a cluster. Its stacks and add-ons are on the cluster’s Stacks and Add-ons pages.

Stacks, and the add-ons and manifests in them

A stack opens in the stack editor:

https://platform.ankra.app/next/clusters/<cluster-id>/stacks/<stack-name>

The same address opens a stack that exists only as a draft. To open the editor on one add-on or manifest of the stack, add member, and kind=manifest for a manifest:

.../stacks/<stack-name>?member=<addon-name>
.../stacks/<stack-name>?member=<manifest-name>&kind=manifest

<stack-name>, <manifest-name> and <addon-name> are the names ankra cluster stacks list and the MCP list_stacks and get_stack_details tools return. A link cannot select an application inside a stack: the editor opens on the stack’s first member instead.

An add-on’s own page

Each add-on on a cluster also has a page outside the stack editor:

https://platform.ankra.app/next/clusters/<cluster-id>/addons/<addon-name>

<addon-name> is the name ankra cluster addons list shows.

Operations

An operation (an execution) on a cluster opens at:

https://platform.ankra.app/next/clusters/<cluster-id>/operations/<operation-id>

Take both values from ankra cluster operations list -o json: <operation-id> is the operation’s id and <cluster-id> is its cluster_id. Ankra has no page yet for an operation that has no cluster_id.

Applications and pipelines

An application’s sections are views of one page, named with ?view=. A view’s own tabs are named with &section=.

Page	Path
One application	`/next/applications/<application-id>`
Its pipeline runs	`/next/applications/<application-id>?view=pipelines`
One pipeline run	`/next/applications/<application-id>?view=pipelines&run=<pipeline-run-id>`
Where it is deployed	`/next/applications/<application-id>?view=where-it-runs`
Deploy, promote and roll back	`/next/applications/<application-id>?view=ship`
Pull request previews	`/next/applications/<application-id>?view=ship&section=previews`
Security findings	`/next/applications/<application-id>?view=protect`
Environment secrets	`/next/applications/<application-id>?view=settings` (Settings opens on its first tab, Secrets)
One Settings tab	`/next/applications/<application-id>?view=settings&section=<section>`, where `<section>` is `secrets`, `address`, `deploys`, `ai`, `registry` or `runtime`
One stack profile	`/next/stack-profiles/<profile-id>`

Pipeline runs

A run of an application’s pipeline opens in the application’s Pipelines view:

https://platform.ankra.app/next/applications/<application-id>?view=pipelines&run=<pipeline-run-id>

Take both values from ankra pipeline get <run> -o json: <application-id> is application_id and <pipeline-run-id> is id. Do not use the run’s run_id field, which identifies a different record. The Open this run in Ankra link in a pull request’s pipeline status comment points at the same page. A run of a repository connected without an application has application_id set to null. Ankra has no page for it yet: follow it with ankra pipeline get <run> --wait and ankra pipeline logs.

AI

Page	Path
Ask Ankra	`/next` (one conversation: `/next?conversation=<conversation-id>`)
AI tickets	`/next/ai/tickets`
One ticket	`/next/ai/tickets/<ticket-id>`
Agent runs	`/next/ai/agent-runs`
One agent run	`/next/ai/agent-runs/<run-id>`
Needs you: approvals, fixes and alerts waiting on a person	`/next/needs-you`
Alerts	`/next/ai/alerts`
One alert rule	`/next/ai/alerts/<alert-id>`
One alert firing	`/next/ai/alert-triggers/<trigger-id>`

Links from AI and MCP clients

The Ankra MCP server tells every connected client to give you a link when it reports on a resource, finishes a change, or asks you to review or approve something in Ankra.

list_clusters and get_cluster_details return each cluster’s portal_url (its overview page).
get_portal_url returns the link for any page on this list. It takes a page (for example cluster_overview, addon, pod, application, pipeline_run, ticket or cve) and the ids that page needs, and it reads and changes nothing, so an mcp:read token can call it.

{
  "name": "get_portal_url",
  "arguments": { "page": "addon", "cluster_id": "5d1f3a52-7e0b-4f3c-9b8f-0f6d3c2a1b4e", "addon_name": "cert-manager" }
}

{
  "page": "addon",
  "url": "https://platform.ankra.app/next/clusters/5d1f3a52-7e0b-4f3c-9b8f-0f6d3c2a1b4e/addons/cert-manager?org=<organisation-id>",
  "description": "One add-on: status, values, the resources it created and its history."
}

If you write your own agent instructions, ask the agent to use these returned URLs rather than composing paths from memory.

Links from the CLI

Commands that create or import a cluster, and ankra cluster apply, print View it in the UI: with the cluster’s overview address.
ankra cluster info prints a Portal: line, and ankra cluster list -o json carries each cluster’s portal_url.
ankra cluster stacks list, ankra cluster manifests list and ankra cluster addons list carry a portal_url for each stack, manifest and add-on in -o json, and print a Portal: line when you name one.
ankra cluster debug ends by printing where to open a shell on the debug pod in Ankra.

The REST API returns IDs and names, not links. Build the address from them with the tables on this page.

Links in notifications

A notification sent to Slack, Microsoft Teams, email or the mobile app links to its own page, /next/notifications/<notification-id>. That page says what happened and links on to the page where you deal with it.
An alert message links to the alert firing it is about.
Both carry the organisation the page belongs to as ?org=.

MCP Server

Connect Cursor, Claude and other MCP clients to Ankra.

MCP Tools

Every tool the MCP server exposes.

Command Palette

Jump to any page with ⌘K.

Projects

What ?project= selects.

Get Started

Use Cases

Concepts

Create and Run Clusters

Ship Your App

Ankra Pipelines

Stacks and Add-ons

Observe and Troubleshoot

Ankra AI

Connect Tools

Source Control

Security and Access

Cost and Backups

Organisation and Account

Reference

How addresses are built

Organisation pages

Cluster pages

Stacks, and the add-ons and manifests in them

An add-on’s own page

Operations

Applications and pipelines

Pipeline runs

AI

Links from AI and MCP clients

Links from the CLI

Links in notifications

MCP Server

MCP Tools

Command Palette

Projects

How addresses are built

Organisation pages

Cluster pages

Stacks, and the add-ons and manifests in them

An add-on’s own page

Operations

Applications and pipelines

Pipeline runs

AI

Links from AI and MCP clients

Links from the CLI

Links in notifications

Related

MCP Server

MCP Tools

Command Palette

Projects