Connectors
A connector links Aderra to another app or service so the assistant can use that service’s tools in your chats. For example, it can read a GitHub repository’s docs, search your Notion pages or look up a library’s documentation.
Connectors use the open MCP (Model Context Protocol) standard. Each connector is a remote MCP server: a web address run by a third party. You add the address, sign in if it asks you to, and its tools become available in chat.
Who can use connectors
Section titled “Who can use connectors”Connectors are available on paid plans (Plus, Pro and Max).
On the Free plan, the Connectors page explains what connectors do and shows “Connectors are available on paid plans. Upgrade to connect Aderra to your other apps.” with a See plans button. The server list and the add button are hidden. See Plans and credits.
If you move from a paid plan to Free, the servers you already added keep working in chat. You can only add or edit servers again on a paid plan.
Open the Connectors page
Section titled “Open the Connectors page”Click Connectors in the left rail, or go to /connectors. The page lists the servers you have added. A small coloured dot on each server’s icon shows its connection state.
Add a server
Section titled “Add a server”- On the Connectors page, click the + button (Add MCP).
- Fill in the Add MCP Server form:
- Name: must start with a letter or number. It can include spaces, hyphens and apostrophes.
- Description: optional.
- MCP Server URL: the server’s address, for example
https://mcp.example.com/mcp. - Transport: Streamable HTTPS is the only option.
- Authentication: see Signing in below. Leave it on None (Auto-detect) unless the server’s instructions say otherwise.
- Tick I trust this application. You can’t save the form without it.
- Click Create. Aderra connects to the server and lists its tools. A server that needs you to sign in is saved but stays disconnected until you sign in once.
What the address must look like
Section titled “What the address must look like”- It must start with
https://and use the standard port, 443. Addresses such ashttp://…orhttps://example.com:8443/…are refused. - The server must speak Streamable HTTP. Servers that offer only SSE or WebSocket can’t be added.
- It must be reachable on the public internet. Addresses on your own computer (
localhost) or on a private network are refused. Aderra can’t run local servers or command-line (stdio) MCP servers. - You can add up to 10 servers. Remove one to add another.
Signing in
Section titled “Signing in”Choose the option in Authentication that the server’s own documentation asks for:
| Option | When to use it |
|---|---|
| None (Auto-detect) | Public servers with no login, and servers that offer OAuth sign-in with automatic setup. If the server needs you to sign in, Aderra detects it. |
| API Key | Servers that give you a key or token. Leave Each user provides their own key unticked, paste the key into API Key, and pick the Header Format: Bearer (most common), Basic, or Custom with a header name such as X-Api-Key. |
| OAuth | Only if the service asks you to register your own OAuth app. Enter its Client ID and Client Secret, plus Authorization URL, Token URL and Scope if the service gives them. After you click Create, Aderra shows a Redirect URI. Copy it into the service’s app settings. It contains the server’s name, so it changes if you add the server again under another name. |
OAuth sign-in happens in your browser, for your account only. When a server needs it, click the Connect icon on its card and the service’s sign-in page opens in a new tab. Approve access there, and the tab tells you “Authentication Successful”. If nothing opens, allow pop-ups for Aderra and try again.
Examples
Section titled “Examples”These are public remote servers that met the rules above when this page was written. They are run by third parties. Check each provider’s own documentation for current addresses and terms.
| Service | URL | Authentication |
|---|---|---|
| GitMCP: docs and code of any public GitHub repository | https://gitmcp.io/<owner>/<repo> (for example https://gitmcp.io/colinhacks/zod) |
None |
| DeepWiki: questions about public GitHub repositories | https://mcp.deepwiki.com/mcp |
None |
| Notion: your Notion workspace | https://mcp.notion.com/mcp |
None (Auto-detect). Sign in to Notion when asked. |
| GitHub: your repositories, issues and pull requests | https://api.githubcopilot.com/mcp/, or https://api.githubcopilot.com/mcp/readonly for read-only tools |
API Key, Bearer, with a GitHub personal access token (a fine-grained token limits what it can reach). Auto-detect sign-in doesn’t work for GitHub. Your organisation’s settings may block access. See GitHub’s docs. |
Use a connector in a chat
Section titled “Use a connector in a chat”- In the composer, open the MCP Servers menu.
- Tick the servers you want for this conversation.
- Ask for what you need, for example “Using GitMCP, explain how zod’s
refineworks”.
The assistant decides when to call a tool, based on your message.
You approve every tool call
Section titled “You approve every tool call”Before any tool from a server you added runs, the chat pauses and shows:
This tool belongs to a server you connected. Allow it to run?
Choose Approve to let it run, or Reject (optionally with a reason, which the assistant sees). You can also choose Edit to change the tool’s input before it runs, or Respond to type a result yourself without calling the server. Then click Submit. The chat carries on from there.
Aderra’s own tools, such as image generation, don’t show this prompt. A few of them ask for other reasons, described in Tools in chat.
Images after a connector
Section titled “Images after a connector”Once a tool from a server you added has been called, Aderra asks before any image tool runs in the same reply:
A tool from a server you connected ran earlier in this reply, and its output may be steering this request. This image tool costs credits. Allow it to run?
You can Approve or Reject. In later messages Aderra doesn’t ask again, so check what you ask for after using a connector.
Use a connector in an agent
Section titled “Use a connector in an agent”- Open the agent builder and click Add tools.
- Under MCP servers, pick the server you added. Each server is one entry. Expand it to turn individual tools on or off.
- Save the agent.
The same approval prompt appears whenever the agent calls one of these tools.
Apps inside the chat
Section titled “Apps inside the chat”Some servers return a small interactive app, such as a form or a set of buttons, that appears inside the conversation. The app is the third party’s own code. It runs in your browser, can load content from the internet, and can show anything its server chooses.
Before the app sends a message or runs a tool as you, Aderra asks you to confirm in a browser dialog. Nothing is sent unless you click OK. The confirmation may not show everything the app sends: long inputs are cut short, and some requests show only their name.
- If the app wants to run a tool, the dialog names the tool and shows its input. If it’s one of Aderra’s paid tools, the dialog says “This tool costs credits.”
- If the app wants to send a message, the dialog shows it and warns that answering it may run tools that cost credits, such as image or video generation.
Limits
Section titled “Limits”- 10 servers per account.
- Time per tool call: a call is stopped if the server sends nothing for 60 seconds. A server that keeps reporting progress gets at most 2 minutes in total.
- Rate limits: you can add or edit servers 10 times an hour, and connect or sign in 30 times in 10 minutes. When you hit a limit, the message doesn’t say so: Create and Update show only “Error”, and Connect shows “Failed to initialize MCP server”. Stop retrying and wait up to an hour. Retrying again and again can lock your account for a while.
- Images from other websites load only when you click them. When a reply contains an image hosted elsewhere, you see a Load image from host button instead. This covers images only. Links in a reply can still point anywhere, so check where a link goes before you open it.
Security and privacy
Section titled “Security and privacy”- What the server receives. Every time a tool runs, the server gets whatever the assistant puts in the tool call. This can include parts of your conversation. It also gets your API key or sign-in token on every request, and it sees each time Aderra connects. If you signed in, it knows which of your accounts with that service is being used.
- Where the traffic comes from. Tool calls and connections to the server leave from Aderra’s servers, not from your device. Some things happen in your own browser and reach the internet from your device: OAuth sign-in pages, apps shown inside the chat, and images you choose to load.
- What Aderra keeps. An API key you paste is stored with the server’s settings on your account, so Aderra can send it on each request.
- What approval does and doesn’t do. Approval stops a tool call from running. It doesn’t stop a server from influencing the assistant. The server’s tool names and descriptions, and the results of calls you approved, reach the model without asking you. A badly behaved server can use them to try to steer the assistant. Read results with that in mind.
- Your responsibility. You choose which servers to add, what you approve and what you share with them. The third party’s own terms and privacy policy apply to whatever it receives.
- Connectors can’t be shared with other users. Each person adds and signs in to their own.
Edit, reconnect or remove
Section titled “Edit, reconnect or remove”On the Connectors page, each server card has small icon buttons (hover for the name):
- Edit (pencil): change the name, URL or sign-in settings, then click Update.
- Connect or Reconnect: retry the connection, for example after the service was down.
- Configure: update values the server asked you for, when it has any.
- Revoke (red trash icon, OAuth servers only): signs you out of that service. The server stays in your list, and you’ll have to sign in again to use it.
To delete a server, click Edit, then the trash button at the bottom left of the form, and confirm with Delete.
Troubleshooting
Section titled “Troubleshooting”| What you see | What to try |
|---|---|
| Error when you click Create or Update | Check that the URL starts with https://, has no port number (or :443), and is the server’s MCP endpoint, not its homepage. It’s often the one ending in /mcp. Check that the server supports Streamable HTTP. You may also have reached the 10-server limit, or a rate limit (see Limits). |
| “Connection attempt to the provided MCP server failed…” | The server didn’t answer, or refused the connection. Check the address in the provider’s docs and that the service is up, then try again. |
| “The MCP server domain is not in the allowed domains list…” | The address points to a private or local network, which Aderra blocks. Use the service’s public address. |
| The server doesn’t connect after you sign in | Click the Connect icon again and finish signing in in the new tab. Allow pop-ups if nothing opens. |
| “Authentication Failed” in the sign-in tab | Start again from Connect. If it keeps failing, check whether the service needs API Key or its own OAuth app instead. |
| The approval card says “This request expired or was already handled.” | The paused request is no longer waiting. Send your message again. |
| No + button, only See plans | Connectors need a paid plan. |
Still stuck? Contact us.