Remote MCP

MCP for Cursor.

Connect Cursor to SiberMate over the remote MCP endpoint.

Markdown version Interactive MCP guide

Server URLs

Default remote MCP: https://mcp.sibermate.com/mcp
Multi-tenant profile: https://mcp.sibermate.com/profile/{YOUR TENANT DOMAIN}/mcp
Example profile: https://mcp.sibermate.com/profile/sibermate.com/mcp

Setup notes

Add SiberMate to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Pass the key via the Authorization header (Cursor supports ${env:VAR}), or omit it to use OAuth.
Use the domain profile URL when one client needs multiple SiberMate tenants side by side.

Authentication

Recommended remote flow: OAuth discovery from the MCP server URL.
Bearer fallback: send Authorization: Bearer <SIBERMATE_API_KEY> only when the client supports custom headers.
Local stdio fallback: run npx -y @sibermatedev/mcp with SIBERMATE_API_KEY in the client environment.

Cursor mcp.json

{
  "mcpServers": {
    "sibermate": {
      "url": "https://mcp.sibermate.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SIBERMATE_API_KEY}"
      }
    }
  }
}

Safety checklist

Use a dedicated tenant API key for MCP setup.
Keep API keys out of prompts, screenshots, repositories, browser history, and shared docs.
For profile URLs, the domain in the URL must match the tenant returned by the API key.
Review generated action plans before sending assignments, reminders, removals, uploads, or deletions.