The SQAI Suite MCP (Model Context Protocol) server acts as a centralized intelligence layer for your development environment. It connects your code, user stories, and test management tools into a single, real-time understanding of the system under development.
Added Value: A Context-Aware Bridge
By connecting the SQAI MCP to Cursor, you create a direct link between the editor's "Agent" capabilities and your broader project data:
Unified Intelligence: It connects code repositories, user stories, and documentation so Cursor’s AI understands the relationship between different artifacts.
Automated Traceability: Easily perform tasks like automated test generation, impact analysis, or documentation creation without leaving your editor.
Continuous Updates: As you change your code or update a user story, the MCP enables you to keep the system model updated, ensuring your AI assistant is never working with stale information.
1. Generate Your API Key
You need an authentication key to securely connect Cursor to the SQAI Platform.
Log in to the SQAI Platform.
Go to the MCP Configuration page: app.sqai-suite.com/mcp.
Generate and copy your unique API Key.
2. Setup Instructions
Cursor allows you to configure MCP servers by editing a mcp.json file. You can apply this configuration globally for all projects or locally for a specific repository.
Important Configuration Note: It is advised to only add the config in one place (locally per project OR globally), otherwise the MCP server may appear twice.
The advantage of project-level installation is that you can check the configuration into your repository so all team members share the same setup. While Cursor does not currently support the "promptString" input method for keys, it is still recommended to use a local .cursor/mcp.json for team consistency.
2.1 Choose Your Method
Local (Per Project): Create or update the file
.cursor/mcp.jsonin your project root.Global (All Projects): Open the file at
%USERPROFILE%/.cursor/mcp.json.Quick Tip: In Cursor, press
CTRL+SHIFT+P, search for "MCP", and select "Open MCP Settings" to manage servers via the UI.
2.2 Configuration Snippet
Paste the following into your mcp.json file. Replace your-SQAI-access-token with the API key you generated in Step 1.
JSON
{
"mcpServers": {
"SQAI-Suite": {
"url": "https://api.sqai-suite.com/mcp",
"headers": {
"Authorization": "Bearer your-SQAI-access-token"
}
}
}
}
3. How to Use
Open Cursor Chat: Open the chat interface or use the Composer (CMD/CTRL + I).
Enable Agent Mode: Ensure you are using a model that supports agents (like Claude 3.5 Sonnet or GPT-4o) and that "Agent" mode is toggled on.
Verify Connection: Cursor will automatically recognize SQAI's MCP capabilities. You can click the tools icon in the chat window to see the full list of SQAI tools available.
Interact: Ask Cursor to utilize your SQAI data.
Example:
Using the SQAI tools, analyze this function against the existing user stories and tell me if any test cases are missing.
4. Troubleshooting
Issue | Potential Cause | Solution |
Server not appearing | Settings not refreshed. | Go to Cursor Settings > Features > MCP and click the refresh/restart button next to the SQAI-Suite entry. |
Auth/Header Errors | Incorrect token format. | Ensure the header value is exactly |
Connection failed | Network/Proxy restrictions. | Verify access to |
Logs and Debugging | Startup errors. | Check the Cursor logs (Help > Toggle Developer Tools > Console) for any fetch errors or JSON parsing issues related to MCP. |
Unresponsive tools | Duplicate configs. | Ensure you don't have conflicting configurations in both the global and local project |