Remote MCP server

Use HeyAI project intelligence from GitHub Copilot

HeyAI MCP gives authenticated agent clients a project-scoped way to list HeyAI projects, ask project questions, inspect work items, generate test scenarios, and request RBT plans.

Copy config View OAuth metadata

Hosted endpoint

https://heyai-mcp.azurewebsites.net/mcp
Microsoft Entra OAuth
Project-scoped tools
Write tools disabled by default

GitHub Copilot setup

Connect the hosted HeyAI MCP server

Add this server to your MCP configuration in VS Code, Visual Studio, JetBrains, or another MCP-compatible Copilot surface. On first use, the client should open Microsoft sign-in and request access to HeyAI MCP.

1. Add the MCP server

Use the hosted MCP endpoint and the dedicated HeyAI MCP Entra client ID.

{
  "servers": {
    "heyai": {
      "type": "http",
      "url": "https://heyai-mcp.azurewebsites.net/mcp",
      "oauth": {
        "clientId": "b9eda3af-10b0-4826-aa46-1207a21b397e"
      }
    }
  }
}

2. Sign in with Microsoft

Use the same work account that has access to HeyAI projects. The MCP server validates the token with Microsoft Entra and calls HeyAI using the signed-in user's identity.

3. Ask Copilot to use HeyAI

Use natural language prompts that refer to your HeyAI projects and delivery workflow.

Use HeyAI to list my projects.
Use HeyAI to summarize release risk for sickleavereporting.
Use HeyAI to generate test scenarios for work item 12345.

Available tools

What Copilot can ask HeyAI to do

List projects

heyai_list_projects returns only projects available to the signed-in user.

Project summary

heyai_get_project_summary retrieves project context and delivery signals.

Ask HeyAI

heyai_ask_project answers source-backed questions against an authorized project.

Tests and RBT

Generate test scenarios and risk-based testing plans from HeyAI project context.

Access model

Authenticated, project-scoped agent access

HeyAI MCP is not a shared admin tunnel. Every tool call is authenticated, checked against the user's allowed projects, and audited without logging project content.

Dedicated Entra app

HeyAI MCP uses a dedicated app registration with scope MCP.Access and publishes OAuth protected resource metadata for MCP clients.

User-scoped authorization

The server resolves the signed-in user's HeyAI project list before executing project tools.

Write tools off

Project write-back tools remain disabled until a separate release approves and audits them.

Private deployment boundary

Hosted MCP is for hosted HeyAI data. Customer-private deployments need a customer-owned MCP server in their Azure subscription before enabling MCP.

Need enterprise setup?

Review HeyAI MCP with your security and Azure teams

We can walk through OAuth, project scoping, audit behavior, and the path for customer-owned MCP in private Azure deployments.

Request MCP review