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. 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, ishttps://platform.ankra.app/next/clusters/<cluster-id>. An address of the retired portal, such as/organisation/dashboard, sends you to the page that replaced it: Where did it go? lists each one. - 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.ankracommands 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 jsonand thelist_clustersMCP 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..
Organisation pages
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.
A cluster’s own Security page lists what needs fixing there, with a button for each fix. The same findings open in the Security Center, scoped to that cluster, at
/next/security?scope=cluster&cluster=<cluster-id>.
The stacks and add-ons Ankra manages on a cluster 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:member, and kind=manifest for a 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:<addon-name> is the name ankra cluster addons list shows.
Operations
An operation (an execution) on a cluster opens at:ankra cluster operations list -o json: <operation-id> is the operation’s id and <cluster-id> is its cluster_id.
When you have only the operation’s id, open:
Applications and pipelines
An application’s sections are views of one page, named with?view=. A view’s own tabs are named with §ion=.
Older application links keep working:
?view=ship opens Environments (or Previews with §ion=previews), ?view=protect opens Security, ?view=cache opens the Cache tab of Pipelines, ?view=source opens the Repository tab of Settings, and ?view=settings§ion=secrets opens Variables, the view that was named Secrets. A bare ?view=settings, which opened Secrets, now opens Settings on Address.
Pipeline runs
A run of an application’s pipeline opens in the application’s Pipelines view: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. It opens under the repository instead:
/next/pipelines/<repository-id> is the repository’s own page. <repository-id> is the id ankra pipeline repositories list shows. A run an application built, opened at this address, redirects to the application’s Pipelines view. From the terminal, follow a run with ankra pipeline get <run> --wait and ankra pipeline logs.
AI
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_clustersandget_cluster_detailsreturn each cluster’sportal_url(its overview page).get_portal_urlreturns the link for any page on this list. It takes apage(for examplecluster_overview,addon,pod,application,pipeline_run,ticketorcve) and the ids that page needs, and it reads and changes nothing, so anmcp:readtoken can call it.
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 infoprints a Portal: line, andankra cluster list -o jsoncarries each cluster’sportal_url.ankra cluster stacks list,ankra cluster manifests listandankra cluster addons listcarry aportal_urlfor each stack, manifest and add-on in-o json, and print a Portal: line when you name one.ankra cluster debugends by printing where to open a shell on the debug pod in Ankra.
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=.
Related
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.