# Add any MCP server

> Give June the tools of any service that offers an MCP server: add its address, sign in, and June can use its tools in your chats.

Source: https://www.dearjune.ai/docs/integrations/custom-mcp

Many services offer their tools as an MCP server: a web address that lists
what the service can do in a standard format. Add that address on the
**Integrations** page and June can use the service's tools in your chats,
even when June has no integration of its own for it.

1. Find the service's MCP server address in its documentation. It starts with `https://`.
2. On the **Integrations** page, choose **Add integration**, paste the address and choose **Detect**. If June cannot find the server, choose **Add manually** and enter a name, the address and a short description.
3. Choose **Add integration**. If the service needs you to sign in, June starts sign-in as part of adding the server and opens the service's sign-in page. Finish signing in and approve the connection. If it needs a token instead, paste the token and choose **Connect with token**.
4. June opens the server's page. On the **Integrations** page it has a row that shows how many tools it offers. Ask June to use it.

## What June can do

June gets every tool the server offers and uses it as the account you
signed in with: what the server's tools can read and change, June can too.
Changes follow your [approval settings](/docs/how-june-works/connections#a-step-that-needs-your-confirmation).
Review the requested action and account before approving; the server
provides the tool’s description.

## Use it in an organization

A server you add on the **Integrations** page reaches your organizations
like any personal connection
([personal or organization](/docs/integrations#personal-or-organization)).

An organization's admins can also offer a server to everyone in it: on
the organization's page, **Add MCP server** opens **Add integration** for
the organization. If the server uses sign-in, June starts the adding
admin's own sign-in immediately. Other members connect their own login
in the organization's Integrations section, with the
server's sign-in, a token, or one click when the server needs no login.
That connection works only in that organization. If you already have the
same server on your own **Integrations** page and it reaches your
organizations, the row shows it connected.

When an admin removes the server (**Remove server** in its row's menu), it
stops working in the organization for everyone at once. Your connection
stays on your **Integrations** page, marked **No longer offered by** the
organization, until you disconnect it.

## When something changes

- If adding the server stopped before its sign-in page opened, open its
  integration page and connect again. You do not need to add the server again.
- If the service adds or changes tools, choose **Refresh tools** in the
  row's menu.
- If the sign-in lapses, the row reads **Re-auth required**; choose
  **Re-auth**.
- To remove the server, open it from its row and choose
  **Remove integration**.

## What June does not do

- It connects only to servers on the public internet over HTTPS, on the
  standard port, with no username or password in the address: not to an
  address on your own computer or private network.
- June can ask you to approve a tool before it runs. It cannot answer a
  question the server asks while the tool is already running; it declines
  that question. If the tool needs more information, supply it in your
  request and try again, or complete that step in the service itself.
- It does not run MCP servers that you would start on your own computer
  (local, command-line servers).
- It cannot switch single tools of a server on or off; June gets all of
  them. Add only servers you trust with what their tools can do.