MySched developer resources

Machine-readable entry points for agents, documentation tools, and developers evaluating MySched.

Markdown and discovery

The landing page and help center expose Markdown representations for clients that send Accept: text/markdown. The agent index explains when MySched is a good fit and links to the complete help corpus.

Use the sitemap to enumerate public URLs. Use the help docs for product behavior and published support guidance. These resources are public and do not grant access to private student schedules.

MCP access

MySched publishes an MCP endpoint at mcp.getmysched.com. The endpoint uses authenticated access when it is available. Complete the server's current OAuth challenge before attempting protected tools. Check the response before use because the MCP service runs outside this website.

The public OpenAPI contract covers the documented documentation search, assistant, and calendar routes. It does not grant access to private student data or private app routes. The public routes do not require OAuth. For integration questions, contact MySched and describe the agent or developer workflow.

Contact MySched

MySched API contract

The public REST contract is version 1. Send X-MySched-API-Version: 1 to pin the version. Omit the header to use version 1. MySched publishes a deprecation timeline here before it removes a version.

Public API responses describe their quota with RateLimit-Policy. Responses with current quota data also include RateLimit. A 429 response includes Retry-After.

The public routes do not require an account or API key. A calendar feed token is a separate read-only capability. The OAuth metadata links above return 503 until a live authorization server is configured and tested.

Start without credentials by fetching OpenAPI, then call /api/search?query=next%20class or run the checked-in mysched-cli package. Public routes are read-only and do not require an account or API key.

MySched API and integration status

The website provides a public REST contract, Markdown content, and links to the external MySched MCP endpoint. The public REST routes do not require OAuth.

MySched does not publish a general authenticated student-data API, webhook catalog, or separate authentication SDK. The documented public routes are available in theOpenAPI specification. Do not infer private app routes to be a public API. Contact MySched if you need an integration that is not listed here.

The official dependency-free mysched-cli package is prepared in thepackages/mysched-cli source directory. npm publication requires the project's npm credentials.