Skip to main content
Everything the Ankra CLI, API and MCP tools change is also visible in the portal at platform.ankra.app. Every portal page has a stable address, so you can bookmark it, paste it into a ticket, or have an AI client hand it to you. This page explains how those addresses are built and lists the main ones.

How addresses are built

  • The organisation comes from your session. Most pages live under /organisation/... and show the organisation you have selected in the top-left switcher. Only the organisation admin pages (members, service tokens and organisation settings) put the organisation id in the path.
  • ?org= opens a link in the right organisation. Links from Ankra (notifications, AI answers, MCP results) add ?org=<organisation-id>. If that is not your current organisation, the portal offers to switch to it instead of showing “Resource not found”.
  • Clusters are addressed by id, not by name. Every cluster page starts with /organisation/clusters/cluster/imported/<cluster-id>/. The imported segment is used for every cluster, including ones Ankra built. 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 workloads are addressed by namespace and name.
You rarely need to build these URLs yourself. ankra CLI commands that create a cluster print a View it in the UI link, and MCP clients can call get_portal_url.

Organisation pages

Cluster pages

Every path below starts with /organisation/clusters/cluster/imported/<cluster-id>. An operation whose cluster you do not know opens at /organisation/operations/<operation-id>.

Applications and pipelines

AI

The Ankra MCP server tells every connected client to give you a portal link when it reports on a resource, finishes a change, or asks you to review or approve something in the UI.
  • 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.
If you write your own agent instructions, ask the agent to use these returned URLs rather than composing portal paths from memory.
  • Cluster creation and ankra cluster apply print View it in the UI: with the cluster’s overview URL.
  • ankra cluster debug prints a link to the debug pod’s terminal.
  • Slack, Microsoft Teams, email and webhook notifications link to the alert firing, ticket, pipeline run or cluster page they are about, and carry the organisation the page belongs to.

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.

Dashboard

The organisation landing page.