A Model Context Protocol server that lets AI assistants work with your Edular calendar, availability, and academics — on your behalf, with your permission.
Edular MCP is per‑school. Your URL includes your school's slug:
https://mcp.edular.app/mcp/<your-slug>
For example, the demo school is:
https://mcp.edular.app/mcp/demo
demo; replace it with your own.
There's no API key or token to paste. Edular MCP uses OAuth 2.1:
You can revoke access at any time. The assistant only ever acts as you, within what you approved.
Add a custom MCP server:
https://mcp.edular.app/mcp/democlaude mcp add --transport http edular https://mcp.edular.app/mcp/demo
Then run /mcp in Claude Code and authenticate when prompted.
Add a custom connector in your app's settings and paste the URL
https://mcp.edular.app/mcp/demo. The app walks you through the browser sign-in.
For a client that only speaks stdio, bridge to the remote server with mcp-remote:
npx -y mcp-remote https://mcp.edular.app/mcp/demo
It handles discovery, registration, and the browser sign-in for you.
Once connected, these tools are available:
Make sure you added it as a Streamable HTTP / remote server (or via
mcp-remote) — not a plain stdio command. The sign-in prompt appears on connect.
Remove and re-add the connector in your client. If you used mcp-remote, clear its
cached tokens: rm -rf ~/.mcp-auth.
Check the slug in your URL — /mcp/<slug> selects the school.