Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs Codna — repository intelligence

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Codna — repository intelligence is an MCP server published by thyn-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceSequa.AICodna — repository intelligence
Docker MCP Catalog Listed
Version: sha256:f4e0e271c5c5
Forks (GitHub): 5
Pulls (Docker Hub): 10 257
Stars (Docker Hub): 1
Stars (GitHub): 22
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.93
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Sequa.AI vs Codna — repository intelligence
FactSequa.AICodna — repository intelligence
Marketplaces that list it11
Stars (GitHub) (differs)22 (better)0 (worse)
Pulls (Docker Hub) (differs)10 257No figure on Docker Hub
Forks (GitHub) (differs)5 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/sequa)On your machine (codna)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 5
Licence (differs)MITNot stated
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/thyn-ai/codna-cli
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Sequa.AI

In its own words, on Docker MCP Catalog:

Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.

Codna — repository intelligence

In its own words, on Official MCP Registry:

Repo intelligence: triage, fix PRs, SARIF reachability, recall. Free codna login to execute.

How to run each

Sequa.AI As a local MCP server: Docker image

Claude Code
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio sequa -- docker run -i --rm -e API_KEY mcp/sequa

Requires: API_KEY (secret)

Codna — repository intelligence As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "CODNA_API_KEY=<YOUR_CODNA_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio codna -- uvx codna

Requires: ANTHROPIC_API_KEY (secret), CODNA_API_KEY (secret), GEMINI_API_KEY (secret), GITHUB_TOKEN (secret), OPENAI_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Codna — repository intelligence publish no list of tools, so we do not compare tools.

Settings each asks for

Only Sequa.AI asks for

  • API_KEY (secret)
  • MCP_SERVER_URL

Only Codna — repository intelligence asks for

  • ANTHROPIC_API_KEY (secret)
  • CODNA_API_KEY (secret)
  • GEMINI_API_KEY (secret)
  • GITHUB_TOKEN (secret)
  • OPENAI_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Sequa.AI · What it can do: Codna — repository intelligence · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built