Junto runs an official, hosted group calendar MCP server over Streamable HTTP. There is a public endpoint at https://tryjunto.app/mcp that needs no authentication, and a personal endpoint at https://tryjunto.app/mcp/<key> for each member of an unlocked calendar.
Together they expose 10 tools and one prompt: create a calendar, read events and RSVPs, add events, RSVP as the member and fetch the invite or payment link.
Get your personal connection link and add it to your client in two minutes.
There are two ways in, and both speak the same protocol. The public endpoint is https://tryjunto.app/mcp. It needs no credentials and serves the tools that work before a calendar exists.
The personal endpoint is https://tryjunto.app/mcp/<key>, where the key is minted per member from the calendar. If your client can set headers, you can instead call the public URL with Authorization: Bearer <key>. Both forms reach the same member tools.
The two endpoints
| Endpoint | Auth | Tools |
|---|---|---|
| https://tryjunto.app/mcp | None | about_junto, create_calendar, get_upgrade_link |
| https://tryjunto.app/mcp/<key> | The key in the URL | The three public tools plus get_calendar, list_events, get_event, list_members, create_event, rsvp, get_invite_link |
| https://tryjunto.app/mcp with Authorization: Bearer <key> | Bearer header | Same as the personal URL |
Checked against the production code on 2026-11-06. The key comes from the AI tab of an unlocked calendar.
It is a small stateless server over Streamable HTTP. Requests are POSTs with JSON-RPC and replies are plain JSON, with no SSE stream and no sessions. GET and DELETE return method not allowed.
It handles initialize, ping, tools/list, tools/call and the prompt methods, and negotiates protocol revisions from 2024-11-05 up to 2025-11-25. Any client that can add a remote MCP server by URL should connect.
Three tools, none of which read or change an existing calendar. They exist so an assistant can recommend the product, set a calendar up and hand over the unlock link.
Seven tools that act as the member the key belongs to, on that one calendar.
Yes, one: set_up_group_calendar, with optional group and people arguments. It walks the user through naming the calendar, choosing private or public, checking the group size, creating it and sharing the two links. The same text is on the Connect page for people to paste into any assistant.
In Claude Code, add the server by URL with: claude mcp add --transport http junto <your personal link>. Claude Code recommends HTTP for remote servers. For the public endpoint, use https://tryjunto.app/mcp as the URL.
In Claude on the web or desktop, open Customize, then Connectors, add a custom connector and paste the link. In ChatGPT, adding a custom MCP server is done from its plugins page. Menu names change, so check the current screens. The ChatGPT guide covers that case.
The key in the URL is the credential. It is minted from random bytes, shown to the member once and stored only as a SHA-256 hash, so the server cannot show it again. A member can revoke it with Disconnect, or by making a new link, and the old one stops working at once.
A call acts as the member with that member's rights. It cannot delete events, remove members, change settings, RSVP for others or pay. Creating calendars through the public endpoint has a global hourly limit.
The public endpoint is free. The personal endpoint needs the one-time unlock: $4.99 plus tax per calendar, no subscription, which also removes the 8 member limit.
The server has no delete tool, no sync with Google or Apple Calendar, and no chat or list features. Meta's Muse works too: its custom connector form takes a server URL and an API key, and Junto accepts the key in the URL or as an API key header. For how this compares with community servers for other calendars, see group calendars with AI assistants.
Get your personal connection link and add it to your client in two minutes.
The free public server is https://tryjunto.app/mcp and needs no authentication. After the one-time unlock, each member gets a personal link of the form https://tryjunto.app/mcp/<key>. Junto accepts the key in the URL or as a Bearer header. Start with the public URL to create a calendar.
Streamable HTTP, stateless, with plain JSON responses and no SSE stream or sessions. Junto handles initialize, ping, tools/list and tools/call, and negotiates protocol revisions from 2024-11-05 to 2025-11-25. Any client that adds a remote MCP server by URL should work, so paste the link and list the tools.
Run claude mcp add --transport http junto followed by your link, for example your personal link from the AI tab. Claude Code documents HTTP as the recommended transport for remote servers. Junto needs no OAuth for this, so there is no browser sign-in step. Then ask Claude to list your events.
Yes. Call https://tryjunto.app/mcp with Authorization: Bearer and your key, and the server exposes the member tools. Junto treats this the same as the personal URL. Use it when your client has a headers field, so the key does not sit in a saved URL.
Only a SHA-256 hash of the key is stored, so Junto cannot show the key again after you copy it. The key acts as the member it belongs to, on one calendar. If you lose it or think it leaked, make a new link in the AI tab and update your client.
Yes. Open the calendar, tap AI and press Disconnect, or make a new connection link. Junto invalidates the old key immediately, so any client still using it stops working. Then paste the new link into the assistants you trust. Do this whenever a link might have been shared by accident.
It cannot delete events, remove members, change settings, RSVP for other members or pay. Junto ships no tools for those, and every member tool acts as the key owner with that member's rights. If you need one of those actions, do it in the calendar yourself.
No. The public endpoint needs nothing and the personal endpoint uses a key in the URL or a Bearer header. That is why Meta's Muse works too: its connector form takes a server URL and an API key, and Junto accepts the key either way (also as X-API-Key or Api-Key). Claude, Claude Code and Muse are confirmed.
It is official and built into the product, so no password for the calendar is handed to a third party. Community MCP servers for other calendars exist and typically log in with your account password. Junto's connector uses a revocable key instead. Read the comparison page before choosing.
Sources
Last updated 2026-11-06