> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythex.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Connectors
> Connect Google Sheets, Gmail, Slack, Notion and hundreds more, then ask the agent to use them — no API keys in your code.
# Connectors
Connectors let Mythex act on the tools you already use. Connect an account once, then just
ask in chat: *"add each new signup as a row in my Leads sheet"*, *"post a message to
\#launches when someone publishes"*.
Your account is linked to Mythex, not to your code. **The agent never sees the
credential**, and nothing lands in your repository.
## Connect an app
### Where to find it
**Connectors** sits in the left sidebar, under **Projects**. It opens over whatever you
were doing — the dashboard, or a project — so you never lose your place.
Inside a project you can also reach it from the chat composer: press **+** next to the
message box and choose **Connectors**.
### Connecting
1. Open **Connectors** by either route above
2. Find the app — search covers the whole catalogue, not just what is on screen
3. Click **Connect**. The provider's sign-in page opens **in a new tab**, so your project
and any half-written message stay where they are
4. Approve access there
5. Come back to the Mythex tab. The app shows a green dot and reads **Connected**
That's it. There is no key to copy and nothing to paste into Mythex.
Approve **every** permission the provider asks for. Google in particular splits access
per product — approving Gmail but not Drive leaves the connection half-working, and the
agent will report `ACCESS_TOKEN_SCOPE_INSUFFICIENT` when it tries to use it.
## Use one in chat
Once an app is connected, ask for what you want in plain language:
```text theme={null}
Read the "Q4 pipeline" sheet and build me a dashboard from it
```
```text theme={null}
When someone submits the contact form, email me at me@example.com
```
The agent finds the right action, checks the arguments it needs, and runs it.
If the app is not connected yet, the turn stops on a card with a **Connect** button
rather than a link buried in a paragraph:
Press it, approve in the tab that opens, and come back — the card notices and turns to
**Connected**, with a **Disconnect** on hover. Then ask again and the agent carries on.
It will not guess at your data or invent a spreadsheet in the meantime.
## What the agent can do
| Tool | What it does |
| -------------------- | ------------------------------------------------------------- |
| `AppListConnections` | Lists the apps you have connected |
| `AppSearchTools` | Finds the right action for a task, and the arguments it takes |
| `AppConnect` | Gives you a link to connect an app it needs |
| `AppRun` | Runs one action against your connected account |
In **Ask** and **Plan** mode the agent can only look — it can list your connections and
research what they could do, but it cannot run anything or start a connection. Planning
never sends an email.
## Disconnect
Open **Connectors**, switch to **Connected** in the left rail, and hover the app you want
to remove.
**Disconnect** revokes Mythex's access with the provider immediately. Anything the agent
already built stays; it just stops being able to reach that account.
## Custom MCP servers
Not everything is in the catalogue. **Connectors → Custom MCP** takes any MCP server's
URL — your own, your company's, or one a vendor gave you.
Press **Add server** (or the **+ Add MCP server** button in the modal's header).
Fill in a name and the URL, choose how it authenticates, and press **Add & authorize**.
Mythex handshakes with the server there and then:
* **If it asks you to sign in** (most remote servers do) a tab opens on the server's own
consent screen, the way Claude and Cursor do it. Approve, and you land back in Mythex
with the server connected. Nothing to register, and no token to copy.
* **If it wants a static token**, paste one in the Bearer token field.
* **If it needs nothing**, it connects straight away.
Either way the tools are read at that moment, so a wrong URL or a refused token fails in
the form rather than three messages into a build. After that the agent can call those
tools by name, the same way it calls a connected app:
```text theme={null}
Use my internal MCP server to look up order 4821
```
Click a server to edit it — the panel becomes **Connectors / Edit MCP server**, and the
breadcrumb takes you back. A rename saves outright; changing the URL or the
authentication re-checks the server before anything is kept, and moving to OAuth sends
you back through consent — a grant belongs to the address it was issued for. A stored
bearer token is never shown; leave the field blank to keep it.
Each server can be switched off without removing it, and **Refresh** re-reads the tool
list after you deploy a change to it. Up to ten servers per account.
A sign-in is kept alive on your behalf — Mythex renews it in the background. If the
server revokes access, the card says so and offers **Sign in** again.
Mythex has an MCP server of its own (`https://mcp.mythex.ai/mcp`) — see
[MCP](/features/mcp). You can add it here like any other, which gives the chat agent your
projects, deployments and domains as tools.
## Where credentials live
* Held by Mythex's connection service, encrypted at rest — a custom MCP server's bearer
token the same way
* Never written into your project, your `.env`, or generated code
* Never sent to the sandbox your app builds in — the sandbox asks the server to make the
call and gets the result back
* Removed when you disconnect, or when you delete your account
## Limits
* Connections belong to **you**, and are shared across all your projects
* Connecting requires the provider to support it — a few apps in the catalogue are
listed but not yet connectable, and show as unavailable
* Rate limits apply to how often the agent can call a connected app, to protect the
quota on your own provider account
## Troubleshooting
**"That connection is not linked to this project."**
The connection was removed, or belongs to another account. Reopen **Connectors** and
check the **Connected** tab.
**The agent says an app needs reconnecting.**
The provider revoked or expired the grant — common after a password change, or when an
admin changes workspace permissions. Disconnect and connect again.
**`ACCESS_TOKEN_SCOPE_INSUFFICIENT`**
The account was linked without enough access. Disconnect, connect again, and approve
every scope the provider asks for.
**Connectors says it isn't enabled.**
Self-hosted Mythex needs `COMPOSIO_API_KEY` set on the server. On mythex.ai it is always
on.