Skip to main content

Microsoft Copilot Agents

Connect SQAI Suite to Microsoft Copilot Agents via Copilot Studio. This guide covers creating a custom connector in Power Apps using the Model Context Protocol (MCP), integrating it into your agent, and publishing it to Microsoft Teams and Office 365.

Updated yesterday

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 Microsoft Copilot, you create a direct link between the agent's reasoning capabilities and your broader project data:

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

  • Automated Traceability: Easily perform tasks like automated test generation or impact analysis directly within Microsoft 365 apps.

  • Continuous Updates: As you change your code or update a user story, the MCP enables you to keep the system model updated for the agent.

1. Create a New Agent in Copilot Studio

  1. Navigate to Copilot Studio.

  2. Select Agents from the sidebar and click + New agent.

  3. Choose Skip to configure to manually set your agent basics (Name, Description, and Instructions) and click Create.

2. Setup the SQAI MCP Connector

Microsoft Copilot Studio leverages Custom Connectors to interface with external APIs like the MCP server.

2.1 Create the Connector in Power Apps

  1. Open your agent in Copilot Studio, go to the Tools tab, and select + Add a tool.

  2. Select New tool > Custom connector. This will redirect you to the Power Apps maker portal.

  3. In Power Apps, click + New custom connector and choose Import an OpenAPI file.

  4. Upload the sqai-mcp-server-schema.yaml file and click Continue.

Schema Snippet (.yaml):

YAML

swagger: '2.0'
info:
title: SQAI Suite
description: SQAI Suite MCP server for various integrations
version: 1.0.0
host: api.sqai-suite.com
basePath: /
schemes:
- https
securityDefinitions:
BearerAuth:
type: apiKey
name: Authorization
in: header
description: 'Enter your API key'
security:
- BearerAuth: []
paths:
/mcp:
post:
summary: SQAI Suite integrations MCP server
x-ms-agentic-protocol: mcp-streamable-1.0
operationId: InvokeMCP
responses:
'200':
description: Success
  1. Confirm the host is api.sqai-suite.com and click Create connector.

3. Add the MCP Tool to Your Agent

  1. Return to your agent tab in Copilot Studio and click Refresh on the "Add tool" dialog.

  2. Select the Model Context Protocol filter and search for "SQAI".

  3. Authentication: Generate your API key at app.sqai-suite.com/mcp.

  4. Create a new connection when prompted by entering your API key. Once connected, add it to the agent.

4. Publish and Share

To make your agent available to your team, you must publish it to the correct channels.

  1. Publish: Click the Publish button at the top of the agent overview.

  2. Authentication Settings: Navigate to Settings > Security > Authentication and ensure your agent is configured for Authenticate with Microsoft (Entra ID) to maintain security within your organization.

  3. Add Channels: Go to Channels and select Teams and Microsoft 365 Copilot.

  4. Availability: Click Add channel, then select Availability options to share the agent link or submit it for admin approval.

5. Troubleshooting

Issue

Potential Cause

Solution

Server not appearing

Incorrect filter.

Ensure you select the Model Context Protocol filter when searching for your connector in the tool selection.

Agent needs authorization

First-run requirement.

The first time you test, click the Open connection manager link in the chat to verify your credentials.

Connection failed

Network restrictions.

Verify the URL https://api.sqai-suite.com/mcp is accessible. Check for data loss prevention (DLP) policies in your tenant.

Tool details missing

Agent initialization.

If tools don't list, click Retry in the test pane after ensuring the connection status is "Connected" in the manager.


This video provides a step-by-step visual demonstration of linking an MCP server to Copilot Studio, including how to handle initial connection prompts.

Did this answer your question?