Help

MCP Server — AI Integration

GetCurrent exposes a Model Context Protocol (MCP) server at /api/mcp. AI assistants such as GitHub Copilot, Claude, and any MCP-compatible client can query live M365 data directly from GetCurrent — no copy-paste needed.

For Claude Desktop and similar stdio-only clients, use a personal bearer token generated in Settings → Tenant → MCP access tokens.

Available tools

• 🧭 get_connection_status Check if MCP is using your own tenant or reference data, and get a direct remediation action when tenant mapping/auth is not healthy.
• 📨 get_message_center Query Message Center notifications — filter by service, time range, or search term. Authenticated users receive their own tenant's data; unauthenticated users receive reference data.
• 🗺️ get_roadmap Query the M365 Roadmap — filter by service, upcoming days, or search term.
• ✨ search_whats_new Search What's New items across Defender, Intune, Entra, and Windows 365.

What you can ask after connecting

Once GetCurrent MCP is connected, your assistant can retrieve Message Center tenant data plus Roadmap and What's New reference data:

• 📨 Message Center Examples: “Show the last 10 items for Exchange”, “Are there any items that require action?”, “Show only major changes”, “What's open for Teams in the next 30 days?”
• 🗺️ M365 Roadmap Examples: “What's coming for Intune in the next 60 days?”, “Show Defender roadmap items rolling out soon”, “Search for Copilot features on the roadmap”.
• ✨ What's New Examples: “What's new in Defender?”, “Show recent updates for Entra”, “What's new in Windows 365 or Intune?”

You can also combine filters like service, time period, search term, and urgency in one request.

Connect your AI assistant

Add the following to your MCP client configuration (e.g. .github/mcp.json for GitHub Copilot, or claude_desktop_config.json for Claude Desktop). Set GETCURRENT_MCP_AUTH to the token you copied from GetCurrent:

{
  "mcpServers": {
    "getcurrent": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://updates.getcurrent.cloud/api/mcp",
        "--header",
        "Authorization: Bearer ${GETCURRENT_MCP_AUTH}"
      ],
      "env": {
        "GETCURRENT_MCP_AUTH": "gct_your_token_here"
      }
    }
  }
}

Windows tip: use plain ASCII --header (two hyphens). If your MCP client logs 'C:\Program' is not recognized, set command to npx.cmd.

Claude Desktop steps

1. Sign in to GetCurrent and open Settings → Tenant → MCP access tokens.
2. Generate a token, copy it once, and save it securely.
3. Paste the mcpServers.getcurrent block shown above into Claude Desktop.
4. Save the file and restart Claude Desktop.
5. Open a new chat and call get_connection_status first to confirm tenant context, then use get_message_center, search_whats_new, or get_roadmap.

Troubleshooting (auth/token)

• 🔐 401 Unauthorized Set GETCURRENT_MCP_AUTH to your raw token (for example gct_..., without Bearer) and confirm the token has not expired or been revoked.
• 📌 Header format Use Authorization: Bearer ${GETCURRENT_MCP_AUTH} exactly (including Bearer).
• 🔄 Wrong tenant data Generate a new token after reconnecting your tenant in Settings → Tenant so the bearer token matches the current onboarded tenant.
• 🧪 Config not detected Validate JSON syntax, keep the env var on one line, use plain ASCII --header, and restart Claude Desktop after saving the config file.

Auth: The MCP server accepts a personal bearer token generated in GetCurrent for tenant-scoped access. Administrators can restore anonymous reference-data access by setting MCP_REQUIRE_AUTH=false.