Use June from any MCP client

Connect Gmail, GitHub or Notion once in June, and Claude Code, Codex or Cursor can use them, with no keys or sign-ins of their own.

It reaches the integrations in your personal space, never an organization's. It is for your integrations only. The client does not talk to June: it gets no chat with June, no threads, no memory and no schedules, and nothing it does shows up in your chats.

The address is the same for every MCP client:

https://www.dearjune.ai/api/mcp

Set up your client has the command or file for each one, and how to sign in with your June account.

What the client gets

Two tools, not one per integration:

• skills tells the client how to write a program for execute, lists the integrations you have connected, and names the MCP servers you added but have not signed in to.
• execute runs a short program on June's side. The program finds the tools it needs among your integrations, calls them and returns the result to the client.

You do not write the program yourself: you ask the client for the work, and it writes one. To write your own, see Write June MCP programs.

Which connections it reaches

June MCP reaches what you connected in your personal space, on the Integrations page. It never reaches an organization.

Not every integration offers the same tools here as in a chat with June:

Integration	What a client can do
Mailbox, and Outlook mail from Microsoft 365	search and read your mail, save drafts
Microsoft 365	read your calendar, Teams chats and OneDrive and SharePoint files
Google Drive	search and read your files
Google Search Console	read search performance, index status and sitemaps
GitHub	read your account, a repository's details and one file at a time
Notion	read the pages and databases you share; add pages and rows, set values, add to the end of a page
X	read posts, threads, mentions, bookmarks, likes, followers and following, and your posts' analytics
Any MCP server you added	every tool the server offers, except one that asks for confirmation

Obsidian, ownCloud and Tailscale work only in June's sandbox, so a client does not reach them. GitHub's issues, pull requests and pushes go through June's sandbox too: a client reads GitHub but does not work in it.

When a connection is missing

When a request needs an integration you have not connected, or one whose sign-in expired, the client can give you a June link. Open it, sign in to June and to the service, and ask again.

The link connects or renews only an integration's default connection. A connection you gave another name, such as work, is renewed with Re-auth on its row on the Integrations page. A mailbox added with a password, or a server added with a token, is fixed on that page too.

What June does not do

• It does not hand out your credentials. The program calls your integrations through June and never sees a token.
• It does not open websites, read files on your computer or run commands: a program reaches only your integrations.
• It does not ask for your approval. A step that needs it, such as creating a Microsoft 365 calendar event, sending a Teams message or sending an email, does not run; ask June for it in a chat on the web or in the app, where you approve it on a card (how).
• It does not let a client add, connect or remove integrations. Connect them on the Integrations page.
• It does not run a program past its limits on size, run time and result.

More on June MCP

• Set up your client: Claude Code, Codex, Cursor, OpenCode or another client.
• Write June MCP programs: how a program finds and calls tools, three examples, and its limits.