What is Sequa Mcp

Sequa is a Contextual Knowledge Engine designed to integrate various aspects of software development, including code, documentation, and issue tracking, across multiple repositories. It enhances AI development tools by providing real-time, contextual project knowledge, thereby facilitating better responses to complex queries and reducing inaccuracies in generated content.

Use cases

Sequa can be utilized in various development environments where AI tools are integrated. It is particularly effective for improving the accuracy of code suggestions, enhancing documentation retrieval, answering architecture-related questions, and minimizing AI hallucinations during code generation tasks. It can serve teams by providing context-aware assistance within IDEs.

How to use

To utilize Sequa MCP, you can quickly start by using NPX or Docker commands to set up the proxy with your Sequa workspace URL. You’ll need to configure the tool in your preferred IDE by specifying the command and arguments that point to the Sequa MCP, ensuring that you set it up correctly to interact through the STDIO interface despite underlying HTTP streaming.

Key features

Sequa MCP enables seamless communication between IDEs and the Sequa workspace through a lightweight proxy. It provides real-time, multi-repository context, enhances the performance of LLM-powered assistants by delivering accurate project information instantaneously, and operates over an HTTP stream, allowing for bidirectional data flow. The setup is lightweight and does not require additional infrastructure.

Where to use

Sequa MCP is designed for integration with various development tools and IDEs that support STDIO-based commands. It can be configured with popular environments like Cursor, Claude Desktop, VS Code, and others, facilitating its adoption in diverse development workflows and improving the interaction of AI assistants with project-specific knowledge.

Sequa MCP

The missing brain for your AI dev tools

🤔 What is Sequa?

Sequa is a Contextual Knowledge Engine that unifies code, documentation and tickets across multiple repositories and streams that live context to any LLM‑powered assistant. By giving tools like Cursor or Claude deep, always‑current project knowledge, Sequa helps them answer architecture‑level questions, generate more accurate code and slash hallucinations.

🖥️ What is Sequa MCP?

sequa‑mcp is a tiny proxy that lets any STDIO‑based AI client talk to your Sequa workspace using the Model Context Protocol (MCP). It forwards STDIO traffic to Sequa’s streamable HTTP MCP endpoint - so IDEs that only support the command transport can connect with zero extra infrastructure.

Why not just use a URL?

Most IDEs currently speak MCP over STDIO commands and assume the proxy is responsible for networking. Sequa exposes an advanced bidirectional HTTP stream, not SSE, so direct url: configs will not work yet. Until IDEs add first‑class support, always configure Sequa through the command/args option shown below.

🚀 Quick Start

Via NPX

npx -y @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/<endpoint>

Via Docker

docker run -i --rm --network host sequa/sequa-mcp:latest https://mcp.sequa.ai/<endpoint>

🔌 Connect Your Favourite Tools

Replace https://mcp.sequa.ai/<endpoint> with your actual Sequa MCP URL. Always use the command style until IDEs support HTTP‑stream URLs directly.

Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "sequa": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest",
        "https://mcp.sequa.ai/<endpoint>"
      ]
    }
  }
}

Claude Desktop

Settings ➜ Developer ➜ Edit Config

{
  "mcpServers": {
    "sequa": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest",
        "https://mcp.sequa.ai/<endpoint>"
      ]
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "sequa": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest",
        "https://mcp.sequa.ai/<endpoint>"
      ]
    }
  }
}

VS Code

.vscode/mcp.json

{
  "servers": {
    "sequa": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest",
        "https://mcp.sequa.ai/<endpoint>"
      ]
    }
  }
}

Cline (Claude Dev‑Tools)

~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

{
  "mcpServers": {
    "sequa": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest",
        "https://mcp.sequa.ai/<endpoint>"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Highlight AI

1. Click the plugins icon (@) ➜ Installed Plugins ➜ Custom Plugin ➜ Add using a command

2. Use:

   npx -y @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/<endpoint>
   

Augment Code

npx @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/<endpoint>

Or in augment_config.json:

{
  "mcpServers": {
    "sequa": {
      "command": "npx",
      "args": [
        "-y",
        "@sequa-ai/sequa-mcp@latest",
        "https://mcp.sequa.ai/<endpoint>"
      ]
    }
  }
}

⚙️ How It Works

IDE / Agent ⇄ Sequa MCP (local proxy) ⇄ Sequa Workspace (HTTP‑stream MCP)

1. Your IDE writes MCP requests on STDIO.
2. sequa‑mcp streams them over HTTPS to the Sequa workspace.
3. Sequa enriches the requests with real‑time, multi‑repo context and streams back partial results.
4. The proxy pipes the bytes straight to your IDE for instant feedback.