Developer Portal

    Build on OpenDesk

    Full OpenAPI 3.1 spec, OAuth-protected MCP streamable-HTTP endpoint, and an llms-full.txt manifest so any agent or AI tool can discover and integrate with OpenDesk.

    MCP discovery

    /.well-known/mcp.json

    Open

    OAuth protected resource

    /.well-known/oauth-protected-resource

    Open

    OpenAPI 3.1 spec

    /openapi.yaml

    Open

    llms.txt

    /llms.txt

    Open

    llms-full.txt

    /llms-full.txt

    Open

    AI plugin manifest

    /.well-known/ai-plugin.json

    Open

    MCP Quickstart

    JSON-RPC 2.0 over Streamable HTTP. Connect with OAuth first; the Accept header pair is required by the MCP spec.

    curl -X POST https://opendesk.tech/api/mcp \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENDESK_TOKEN" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

    OAuth 2.0 Scopes

    OpenDesk uses OAuth consent for identity, then backend policies scope CRM and scheduler access per signed-in user.

    openid

    Identify the signed-in OpenDesk account.

    email

    Share the account email during consent.

    profile

    Share basic profile information during consent.

    RLS

    OpenDesk backend policies decide which CRM rows tools can access.

    Request SDK / partnership