MCP Tools
The Sequa Model Context Protocol (MCP) provides your AI assistants with a powerful suite of tools to interact with your Sequa workspace. By connecting an MCP-compatible agent, you grant it the same battle-tested capabilities that Sequa’s native AI uses to understand and reason about your software projects.
These tools allow the agent to perform actions like searching code, reading documentation, and analyzing your codebase architecture, all grounded in the single source of truth managed by Sequa. This empowers your agent to move beyond generic advice and provide context-specific, actionable insights directly within your workflow.
Workspace & Codebase Tools
These tools provide the agent with the ability to read, search, and analyze the context of your private projects, including documentation, services, and the code itself.
| Tool Name | Description |
|---|---|
search_workspace | Searches across all workspace documentation, including architectural diagrams, team decisions, product requirements, and other knowledge artifacts. |
get_detailed_service_overview | Retrieves comprehensive information about a specific service, including its tech stack, dependencies, onboarding guides, and file structure. |
scan_service | Deploys a specialized AI agent to perform a deep analysis of a service’s codebase, answering complex questions about architecture, design patterns, or implementation details. |
search_codebase_files | Performs a powerful search across your codebase using semantic, regular expression, or full-text search to find relevant files and functions. |
get_codebase_files | Retrieves the full content of specific files from a codebase when the exact file path is known. |
execute_codebase_command | Executes read-only bash commands (like ls, grep, or find) within a codebase to inspect the file system or analyze file contents. |
get_commits | Fetches the git commit history for a codebase, allowing the agent to understand recent changes, identify when a bug was introduced, or analyze development velocity. |
get_file_diffs | Retrieves a line-by-line “diff” of changes to a file between two points in time (e.g., between two commits or dates), showing exactly what was added or removed. |
External Information Tools
These tools give the agent access to information from the public internet, allowing it to supplement its understanding with external context, such as library documentation or recent articles.
| Tool Name | Description |
|---|---|
search_web | Searches the public internet to find current information, news, or data that may not be available within your workspace. |
read_website | Extracts and reads the full content of a public website or documentation page from a given URL. |
Example Use Cases
- Onboarding a New Developer: An AI assistant can use
search_workspaceto explain the high-level architecture and then useget_detailed_service_overviewandsearch_codebase_filesto show a new developer where to find key files in their first project. - Troubleshooting a Production Issue: An agent can be asked to investigate a bug. It could use
get_commitsto see recent changes,get_file_diffsto pinpoint a specific modification, andsearch_codebase_filesto understand how the affected code works. - Implementing a New Feature: A developer can ask their assistant for help building a feature. The agent can use
search_workspaceto retrieve the technical requirements,search_codebase_filesto find similar existing code, andread_websiteto pull in documentation for a new library it needs to use.
By providing this comprehensive toolset, the Sequa MCP turns your AI assistant from a general-purpose model into a specialized, context-aware software development partner.
Next, let’s explore some practical examples in the Examples page.