Connect Copilot, Cursor & IDEs to Monita

Any MCP-capable client can use the Monita MCP server. Recipes for the common ones:

Microsoft Copilot Studio agents can call Monita as an MCP action:

In your agent, choose Add an action → Model Context Protocol.
Set the transport to Streamable HTTP and the server URL to https://api.monita.ai/mcp.
For authentication, supply an API key from Settings → API keys as a bearer token (Authorization: Bearer ak_…).
Publish the agent — Monita’s tools appear in its action catalog.

GitHub Copilot’s agent mode reads MCP servers from your VS Code configuration. Add to mcp.json (via MCP: Add Server or manually):

{
  "servers": {
    "monita": {
      "type": "http",
      "url": "https://api.monita.ai/mcp"
    }
  }
}

VS Code handles the OAuth sign-in when the server is first used. Prefer an API key for shared or headless setups:

{
  "servers": {
    "monita": {
      "type": "http",
      "url": "https://api.monita.ai/mcp",
      "headers": { "Authorization": "Bearer ak_your_key" }
    }
  }
}

Add to ~/.cursor/mcp.json (or a project’s .cursor/mcp.json):

{
  "mcpServers": {
    "monita": {
      "url": "https://api.monita.ai/mcp"
    }
  }
}

Cursor runs the OAuth flow on first use; or add a headers block with Authorization: Bearer ak_… to use an API key.

Point the client at https://api.monita.ai/mcp with Streamable HTTP transport. If it supports MCP OAuth, connection is fully automatic (discovery + dynamic registration). Otherwise use an API key as a bearer token, with X-Org-Id: org_… if your account spans several organizations.