Ankra

ai.ankraPublished by ankra.aiv1.0.1Updated Nov 6, 2026

Deploy and operate Kubernetes: clusters, stacks, apps, logs, metrics and security, with OAuth.

The publisher's own server: Ankra Docs

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Hosted Ankra MCP server that lets an assistant deploy and operate Kubernetes clusters, stacks, apps, logs, metrics and security via OAuth.

What you can do
  • Deploy and operate Kubernetes clusters, stacks and apps through Ankra
  • Inspect logs, metrics and security information for running workloads
  • Work through Ankra's agent skills and slash commands for building, shipping and operating Kubernetes
  • Connect from Cursor or Claude Code through the hosted Ankra MCP server with browser sign-in
When to use it
Useful when you want an assistant to help build, ship and operate Kubernetes through Ankra rather than by hand, especially inside Cursor or Claude Code where the Ankra plugin adds skills and commands.
Requirements
A remote endpoint at platform.ankra.app; OAuth sign-in (browser sign-in) is required. No packages, environment variables or headers are declared. The plugin route targets Cursor or Claude Code.
Before you install
The server can change live Kubernetes infrastructure: deploying stacks and apps affects real clusters, so review actions before they run. Access is granted through OAuth to your Ankra account, so the assistant acts with your permissions. The README's sync workflow uses the repository's GITHUB_TOKEN, which is a maintainer concern rather than a user credential.

Installation

In SourceWeft

  1. Open Ankra in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.ankra%2Fplatform/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ankra": {
      "type": "http",
      "url": "https://platform.ankra.app/api/v1/mcp"
    }
  }
}

README

Ankra plugin for Cursor and Claude Code

The Ankra plugin for Cursor and Claude Code. It connects the agent to the hosted Ankra MCP server and adds Ankra's agent skills and slash commands for building, shipping and operating Kubernetes through Ankra.

For Claude Code, run this in a terminal:

sh
claude plugin install ankra --marketplace ankraio/cursor-plugin

Using the plugin: see plugins/ankra/README.md.

Layout

text
.cursor-plugin/marketplace.json   Cursor marketplace manifest.claude-plugin/marketplace.json   Claude Code marketplace manifestplugins/ankra/  .cursor-plugin/plugin.json      Cursor plugin manifest  .claude-plugin/plugin.json      Claude Code plugin manifest  mcp.json                        the hosted Ankra MCP server for Cursor (browser sign-in)  .mcp.json                       the same server for Claude Code  rules/ankra.mdc                 when and how to work through Ankra (Cursor only)  skills/                         generated from ankra-cli, do not edit here  commands/                       generated from ankra-cli, do not edit here  assets/logo.svg  SOURCE                          the ankra-cli release the skills and commands came fromscripts/  sync-from-cli.sh                regenerate skills and commands  sync-latest-release.sh          download, verify and sync a release (used by the scheduled workflow)  validate-template.mjs           Cursor's plugin validator, from cursor/plugin-template

Updating the skills and commands

The skills and commands are maintained in ankraio/ankra-cli (internal/skills) and also ship through ankra skills install. Change them there, cut a CLI release, then regenerate this plugin from that release:

bash
brew upgrade ankra            # the installed CLI must match the releasescripts/sync-from-cli.sh      # defaults to the installed CLI's versionnode scripts/validate-template.mjs

Bump version in plugins/ankra/.cursor-plugin/plugin.json and plugins/ankra/.claude-plugin/plugin.json when the plugin content changes. The two stay equal; CI checks it. Claude Code users stay on a version until it changes, so a content change without a bump never reaches them.

This also runs on its own: the Sync from ankra-cli release workflow (.github/workflows/sync-from-cli.yml) checks ankra-cli's latest stable release every morning. When it is newer than plugins/ankra/SOURCE, scripts/sync-latest-release.sh downloads that release's binary, verifies its checksum, regenerates the skills and commands, bumps the minor version and validates, and the workflow opens (or updates) a pull request from sync/ankra-cli-release. It uses only the repository's GITHUB_TOKEN. Run it by hand from the Actions tab, optionally with a tag or as a dry_run. The same script works locally without an installed ankra:

bash
scripts/sync-latest-release.sh            # latest stable releasescripts/sync-latest-release.sh v0.30.0    # a specific release

Testing locally

Claude Code:

bash
claude plugin validate --strict plugins/ankraclaude plugin validate .claude --plugin-dir plugins/ankra

Cursor:

bash
mkdir -p ~/.cursor/plugins/localcp -R plugins/ankra ~/.cursor/plugins/local/ankra-marketplace

Reload Cursor (Developer: Reload Window) and check that the rule, skills, commands and the ankra MCP server appear. If ankra skills install already wrote a local ankra plugin, move it aside while testing so the two do not overlap.

License

Apache-2.0

Source: README.md at commit 7bab206

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestNov 6, 2026
  2. v1.0.0Oct 10, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Ankra integrations

Ankra Docs

ai.ankraOfficial publisher

Ankra Docs's hosted MCP server, published by ankra.ai; no sign-in required; Streamable HTTP; 3 tools.

Streamable HTTPWeb executable
Knowledge & Memory3 toolsNov 6, 2026