Schedulin MCP server

MCP detected 2026-07-05

Details

Endpoint: https://mcp.schedulin.app/mcp
Transport: streamable-http
Docs: https://developers.schedulin.app/guides/oauth

Authentication

OAuth 2.0 oauth2 detected 2026-07-05

OAuth · resolves from well-known metadata

OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

Schedulin API key api_key declared Get key ↗

x-api-key: <credential>

Generate a workspace API key from your Schedulin dashboard under Settings → API keys. Keys are prefixed sk_live_. Treat it as a secret — it grants full access to your workspace.

Schedulin OAuth (MCP) oauth2 declared

OAuth · resolves from well-known metadata

The MCP server is protected by OAuth 2.1 (authorization code + PKCE). MCP clients discover the authorization server automatically from the server URL via RFC 9728 / RFC 8414, and dynamic client registration is supported — no manual setup required.