Code Understanding
codingthefuturewithaiLABSCO SUMMARY
Your assistant writes code that fits, because it has read your codebase.
The failure it targets is the one every team recognises: documentation drifts from the code, so both the new engineer and the coding assistant work from something that was true a year ago. Regenerating the docs from the source is what makes the answers worth acting on.
What it is
The MCP entry point for Sequa, a contextual knowledge engine that generates documentation from your codebase and keeps it updated as the code changes. This repository is the connector: you add Sequa as an MCP server in Cursor, Claude, Windsurf, VS Code, Cline or any other MCP-capable client, and your assistant answers from your own architecture, docs and tickets rather than from what it can infer.
What you get
- Documentation generated from the codebase — architecture overviews, API docs, runbooks and onboarding guides — that regenerates rather than going stale
- Knowledge unified across repositories, so an answer does not depend on which repo the assistant happened to be looking at
- Plain-language questions answered with source links, for people and for agents on the same engine
- Two ways to connect: a direct URL for clients that speak HTTP, or the
@sequa-ai/sequa-mcpproxy launched with npx for clients that expect a command
Requirements
A Sequa account and — this is the step people skip — a Project created inside the Sequa app. Without the project the proxy launches but every call comes back as an authentication or project error. Once the project exists, its MCP Setup URLs page gives you the URL for the transport your client supports; if you use that project-specific endpoint, put it in place of the https://mcp.sequa.ai/v1/setup-code-assistant address in the configurations under Installation. Clients that take a URL get it directly; clients that want a command run npx -y @sequa-ai/sequa-mcp@latest with the URL as an argument.
Setup effort
One command plus credentials — npx -y @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/v1/setup-code-assistant, then supply credentials
USE CASES
01
Getting code that matches your conventions
The assistant answers from your architecture and internal standards, so what it writes fits rather than needing to be corrected afterwards.
02
Onboarding someone into an unfamiliar service
Ask in plain language and get current answers with source links, instead of reading a runbook that stopped matching reality.
03
Answering a question that spans repositories
Knowledge is unified across repos, so the answer does not depend on which one is open.
04
Stopping the manual context-stitching
One MCP entry replaces pasting architecture notes into every session for Copilot or Cursor.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/v1/setup-code-assistantHosted endpoint
ENDPOINT URL
https://mcp.sequa.ai/v1/setup-code-assistantAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"sequa": {
"url": "https://mcp.sequa.ai/v1/setup-code-assistant"
}
}
}Before connecting, sign in at app.sequa.ai and create a Project — without one the server refuses connections. The project's MCP Setup URLs page gives the URL for your client's transport; if you use that project-specific endpoint, it is the address in the configuration instead of https://mcp.sequa.ai/v1/setup-code-assistant.
Claude Desktop, Windsurf, Augment Code
JSON
{
"mcpServers": {
"sequa": {
"command": "npx",
"args": [
"-y",
"@sequa-ai/sequa-mcp@latest",
"https://mcp.sequa.ai/v1/setup-code-assistant"
]
}
}
}Before connecting, sign in at app.sequa.ai and create a Project — without one the server refuses connections. The project's MCP Setup URLs page gives the URL for your client's transport; if you use that project-specific endpoint, it is the address in the configuration instead of https://mcp.sequa.ai/v1/setup-code-assistant.
VS Code
VS CODE · JSON
{
"servers": {
"sequa": {
"command": "npx",
"args": [
"-y",
"@sequa-ai/sequa-mcp@latest",
"https://mcp.sequa.ai/v1/setup-code-assistant"
]
}
}
}Before connecting, sign in at app.sequa.ai and create a Project — without one the server refuses connections. The project's MCP Setup URLs page gives the URL for your client's transport; if you use that project-specific endpoint, it is the address in the configuration instead of https://mcp.sequa.ai/v1/setup-code-assistant.
Cline
CLINE · JSON
{
"mcpServers": {
"sequa": {
"command": "npx",
"args": [
"-y",
"@sequa-ai/sequa-mcp@latest",
"https://mcp.sequa.ai/v1/setup-code-assistant"
],
"disabled": false,
"autoApprove": []
}
}
}Before connecting, sign in at app.sequa.ai and create a Project — without one the server refuses connections. The project's MCP Setup URLs page gives the URL for your client's transport; if you use that project-specific endpoint, it is the address in the configuration instead of https://mcp.sequa.ai/v1/setup-code-assistant.
Highlight AI
HIGHLIGHT AI · TERMINAL
npx -y @sequa-ai/sequa-mcp@latest https://mcp.sequa.ai/v1/setup-code-assistantBefore connecting, sign in at app.sequa.ai and create a Project — without one the server refuses connections. The project's MCP Setup URLs page gives the URL for your client's transport; if you use that project-specific endpoint, it is the address in the configuration instead of https://mcp.sequa.ai/v1/setup-code-assistant.
