Log inSubmit server
Sequa MCP logo

Sequa MCP

by sequa-ai

Keeps codebase and documentation context available to AI coding clients through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Sequa MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sequa-ai-sequa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @sequa-ai/sequa-mcp@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The sequa-ai/sequa-mcp MCP server connects MCP-capable coding assistants to Sequa's project knowledge. It uses a Sequa-provided setup URL, launched directly with NPX or configured as a remote MCP endpoint, to provide context from codebases, documentation, tickets, and internal standards. Create a Sequa account and project first, then copy the project's MCP Setup URL into your client. Reach for it when an assistant needs current repository and documentation context rather than manually assembled background.

Use cases

  • Query codebase architecture from an AI coding assistant
  • Generate or maintain API and onboarding documentation
  • Find answers across repositories, tickets, and internal standards
  • Provide source-linked project context during code generation

Key features

  • Codebase and repository context
  • Continuously updated documentation
  • Cross-repository knowledge access
  • Tickets and internal standards context
  • Plain-language questions with source links
  • NPX-based MCP proxy launch

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 1Low 0

Scanned 10d ago via OSV.dev · @sequa-ai/sequa-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars22Stargazers on the source repository.
npm downloads162Package downloads in the last 30 days.
Last commit10mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Sequa MCP works

What sequa-ai/sequa-mcp MCP server does

The sequa-ai/sequa-mcp MCP server exposes Sequa project knowledge to AI development clients through the Model Context Protocol. Sequa is described as a contextual knowledge engine that builds and maintains documentation from a codebase, including architecture overviews, API documentation, runbooks, and onboarding guides.

The available context can span repositories and documentation, along with tickets and internal standards. Developers can ask questions in plain language and receive answers with source links. The intended use is to give coding assistants current project information while they generate or modify code, reducing the need to assemble repository and documentation context manually.

How it works

The package acts as a proxy to a Sequa MCP endpoint. Its NPX command takes a setup URL as an argument:

Terminal
npx -y @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/v1/setup-code-assistant

A project-specific URL can replace the example endpoint. Clients that support remote MCP URLs can use the endpoint directly; clients configured with a command can launch the NPX package and pass the URL as an argument.

Before connecting, create or sign in to a Sequa account and set up a project in the Sequa application. The project's MCP Setup URLs provide the transport-specific URL or configuration. Without a project, the proxy may launch but connections will return authentication or project errors.

Setup and configuration

The sequa-ai/sequa-mcp MCP server can be configured in Cursor, Claude Desktop, Windsurf, VS Code, Cline, Highlight AI, and Augment Code. Configuration varies by client. Cursor uses a server entry with a url, while the other examples generally invoke npx with the package name and setup URL.

For Claude Desktop, the configuration is added under Settings → Developer → Edit Config. Cursor reads ~/.cursor/mcp.json; Windsurf reads ~/.codeium/windsurf/mcp_config.json; VS Code uses .vscode/mcp.json; and Cline uses cline_mcp_settings.json. Highlight AI accepts the NPX command through its custom-plugin interface, and Augment Code supports either the command or an augment_config.json entry.

The setup URL is the key configuration value. Use the URL generated for the intended Sequa project rather than assuming the example endpoint applies to every project. No environment variables are specified in the provided setup instructions.

Tools and capabilities

The documented capabilities are knowledge-oriented rather than a named list of individual MCP tools. They include access to:

  • Codebase and repository context
  • Generated documentation such as architecture, API, runbook, and onboarding material
  • Documentation collected across repositories
  • Tickets and internal engineering standards
  • Plain-language questions with source links in the answers

Sequa is intended to keep documentation aligned with changes in the underlying code. The README presents this as continuous updating from code, so assistants can use a maintained knowledge base instead of relying only on static documents.

Limitations and notes

The repository material does not provide a detailed tool schema, request examples, permission model, rate limits, pricing information, or supported operating systems. It also does not list environment variables or a separate local indexing process.

A Sequa account and project are prerequisites. The server is not expected to provide a usable connection from the setup command alone: the README specifically notes that omitting project creation results in authentication or project errors. Client compatibility depends on MCP support and the transport available from the project's MCP Setup URLs.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sequa MCP

Create or sign in to a Sequa account, create a project, copy its MCP Setup URL, and run the package with NPX using that URL as the argument.

Yes. The README provides Claude Desktop configuration using `npx -y @sequa-ai/sequa-mcp@latest` and a Sequa setup URL.

Yes. Cursor can configure the Sequa endpoint in `~/.cursor/mcp.json` under an MCP server entry.

You need a Sequa account, a project inside the Sequa app, and the MCP Setup URL for that project.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSequa MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sequa-ai-sequa-mcp?style=directory)](https://allmcps.com/mcp/sequa-ai-sequa-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/sequa-ai-sequa-mcp"><img src="https://allmcps.com/api/badge/sequa-ai-sequa-mcp?style=directory" alt="Sequa MCP on AllMCPs" /></a>