Model Context Protocol (MCP) ¶

This section documents the MCP endpoints currently exposed by the AIOE team.

Access groups ¶

Request access in MyID Groups. If you have questions about MCP onboarding, permissions, or missing endpoints, ask in the Ask Space: webexteams://im?space=66d11270-538c-11f0-b53e-7dbfb1bd78bb.

Client configuration examples ¶

All endpoints follow the same URL pattern: https://aiops-mcp.webex.com/<module_name>/mcp/.

The AIOE MCP gateway publishes standard MCP OAuth discovery endpoints, so in compatible clients you usually only need to add the MCP URL. On first use, the client should guide you through sign-in. In the examples below, emsapi is used as a sample module. Replace it with the MCP you actually want to use.

VS Code ¶

Official VS Code MCP config uses .vscode/mcp.json with a "servers" block.

{
  "servers": {
    "aiops-emsapi": {
      "type": "http",
      "url": "https://aiops-mcp.webex.com/emsapi/mcp/"
    }
  }
}

Windsurf ¶

Official Windsurf MCP config uses ~/.codeium/mcp_config.json with a "mcpServers" block. For remote HTTP MCPs, Windsurf documents serverUrl or url; the example below uses serverUrl.

{
  "mcpServers": {
    "aiops-emsapi": {
      "serverUrl": "https://aiops-mcp.webex.com/emsapi/mcp/"
    }
  }
}

Codex ¶

Official Codex MCP config can be added either with the CLI or in ~/.codex/config.toml.

codex mcp add aiops-emsapi --url https://aiops-mcp.webex.com/emsapi/mcp/

[mcp_servers.aiops-emsapi]
url = "https://aiops-mcp.webex.com/emsapi/mcp/"

Current catalog ¶

The docs links below jump to the matching catalog page that contains tool-level details.

How to use this catalog ¶

1. Find the MCP by its exact module name from the table above.
2. Apply for the listed MyID group.
3. Add the MCP in your client with one of the sample configurations above.
4. Open the matching catalog page to review endpoint details and available tools.