Remote MCP server

Use KontexIQ project intelligence from GitHub Copilot

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

Copy config View OAuth metadata

Hosted endpoint

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

GitHub Copilot setup

Connect the hosted KontexIQ 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 KontexIQ MCP.

1. Add the MCP server

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

{
  "servers": {
    "kontexiq": {
      "type": "http",
      "url": "https://kontexiq-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 KontexIQ projects. The MCP server validates the token with Microsoft Entra and calls KontexIQ using the signed-in user's identity.

3. Ask Copilot to use KontexIQ

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

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

Available tools

What Copilot can ask KontexIQ to do

List projects

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

Project summary

kontexiq_get_project_summary retrieves project context and delivery signals.

Ask KontexIQ

kontexiq_ask_project answers source-backed questions against authorized project facts, including SharePoint document knowledge when connected.

Tests and RBT

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

Access model

Authenticated, project-scoped agent access

KontexIQ 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

KontexIQ 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 KontexIQ 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 KontexIQ data. Customer-private deployments need a customer-owned MCP server in their Azure subscription before enabling MCP.

Need enterprise setup?

Review KontexIQ 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