Skip to main content

GitHub Copilot Agents (GitHub.com)

Connect SQAI Suite to GitHub Copilot Agents and Copilot Spaces directly on GitHub.com. This guide details how to configure a repository-level environment to store your credentials securely and how to activate the SQAI MCP server.

Updated yesterday

The SQAI Suite MCP (Model Context Protocol) server acts as a centralized intelligence layer for your development environment. By integrating it with GitHub.com, you enable the GitHub Copilot coding agent to autonomously interact with your software's lifecycle, test cases, and user stories directly on the platform.

Added Value: A Context-Aware Bridge

Connecting the SQAI MCP to GitHub.com extends the agent's reasoning capabilities beyond just your code:

  • Unified Intelligence: It connects code repositories, user stories, and documentation so the GitHub coding agent understands the relationship between different artifacts.

  • Automated Traceability: Enable the agent to perform tasks like automated test generation, impact analysis, or documentation creation during its autonomous coding sessions.

  • Continuous Updates: As the agent makes changes or processes new issues, the MCP ensures it remains aligned with the most current system model.

1. Generate Your API Key

You need an authentication key to securely connect the GitHub coding agent to the SQAI Platform.

  1. Log in to the SQAI Platform.

  2. Go to the MCP Configuration page: app.sqai-suite.com/mcp.

  3. Generate and copy your unique API Key.

2. Setup Instructions

For GitHub.com, the configuration is managed within the repository settings. This allows the agent to use your SQAI tools when working on issues or within Copilot Spaces.

2.1 Configure the Environment and Secret

  1. Navigate to your repository on GitHub.com.

  2. Go to Settings > Environments.

  3. Click New environment and name it copilot. (If this environment already exists, simply click to configure it).

  4. Under Environment secrets, click Add environment secret.

  5. Name: COPILOT_MCP_SQAI_TOKEN

  6. Value: Paste the API key you generated in Step 1.

2.2 Configure the MCP Server

  1. In your repository settings, go to Copilot > Coding agent.

  2. Locate the MCP configuration section.

  3. Paste the following JSON snippet and click Save.

JSON

{
"mcpServers": {
"SQAI-Suite": {
"type": "http",
"url": "https://api.sqai-suite.com/mcp",
"headers": {
"Authorization": "Bearer $COPILOT_MCP_SQAI_TOKEN"
},
"tools": ["*"]
}
}
}

3. How to Use

  1. Initiate a Task: You can now use the MCP server for any actions Copilot takes in your repository from Copilot Spaces or by assigning an issue to the Coding Agent.

  2. Autonomous Interaction: When the agent starts a session, it will automatically recognize the SQAI capabilities and use them as needed to fulfill the task (e.g., pulling user story context to write code).

  3. Learn More: For deep dives into extending agents, check out the official GitHub documentation: Extending Copilot coding agent with MCP.


Troubleshooting

Issue

Potential Cause

Solution

Agent ignores SQAI tools

Tools not allowlisted.

Ensure the "tools": ["*"] entry is present in your JSON to allow the agent to see all SQAI capabilities.

Authentication Error

Secret name mismatch.

Verify the secret in your environment is exactly COPILOT_MCP_SQAI_TOKEN. The $ prefix is only used in the JSON config.

Server not active

Environment name.

Ensure the GitHub environment is named exactly copilot. This is a reserved name the agent looks for.

Connection failed

Network restrictions.

Verify the repository has permission to access external URLs. Large organizations may have firewall policies restricting MCP traffic.

Did this answer your question?