Add Seqia MCP server to catalog

[fabian-emilius]

MCP Server Information

Server Name: Sequa.AI
Repository URL: https://github.com/sequa-ai/sequa-mcp
Brief Description: Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.

Sequa.AI (https://sequa.ai) is a Model Context Protocol (MCP) server that gives Copilot, Cursor, and other MCP‑capable assistants full-codebase and docs awareness without manual prompt stitching. Point it at your repos and knowledge bases once; after that, your AI tools can browse, search, diff, and reason over everything through standardized MCP tools.

Basic Requirements

• Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license)
• MCP Compliant: Implements MCP API specification
• Active Development: Recent commits and maintained
• Docker Artifact: Dockerfile
• Documentation: Basic README and setup instructions
• Security Contact: Method for reporting security issues

Submitter Checklist

• This server meets the basic requirements listed above
• I understand this will undergo automated and manual review.
• I have tested the MCP Server using task validate -- --name SERVER_NAME
• I have built the MCP Server using task build -- --tools SERVER_NAME

Why is the last box not checked?: When running task build -- --tools sequa it always exited with status 1 but I tested the mcp server locally with docker desktop and it worked after successful authentication

[cmrigney]

Thanks for your contribution! I'm not sure why, but it's failing for me. You can try it yourself by merging the latest main into your branch and running

task build -- --tools --pull-community sequa

[cmrigney]

Just saw your comment:

Why is the last box not checked?: When running task build -- --tools sequa it always exited with status 1 but I tested the mcp server locally with docker desktop and it worked after successful authentication

We'll need to get it working with task build before we can merge it. I'm not sure what the difference could be, but maybe some additional logging could help here?

[fabian-emilius]

Hey @cmrigney ,
the build command works without the --tools parameter but fails with it. From looking at the code, it seems that it tries to retrieve the tools from the server but the server requires authentication so it fails because the tools cant be listed without authentication.

I think I found a workaround now by including basic configuration that does not require authentication, so the command works now 💪 but this is probably an issue more people will run into.