Skip to main content
MCP connectors let you bring live data from external services directly into your Ragen conversations. Instead of manually copying information across tools, you connect a service once and Ragen’s assistants can query it in real time — searching your emails, pulling CRM records, checking calendar events, or importing documents from Drive — all as part of a single chat response.

​
Available connectors

Ragen ships with these: This list is not fixed. Which connectors your installation offers is data a platform admin edits, not code — so any MCP server can be added, including one running on your own network, without a code change or a release of Ragen.

Add a connector

Paste a URL in the admin panel, test it, grant it to organisations.

Build a connector

No MCP server for the service you want? Scaffold one with a command.
So what you see in Settings → Connectors depends on your installation: the built-ins above, minus anything switched off, plus anything added, filtered by what your organisation has been granted.

​
How to connect a service

Connectors are set up per user, not per organisation. Each person who wants to use a connector must authorise it with their own account.
1

Open Connector Settings

In the Ragen main app, navigate to Settings → Connectors. You’ll see a list of all available connectors and their current status.
2

Click Connect

Select the connector you want and click Connect. What happens next depends on how that connector authenticates:
  • OAuth (Google, Slack, HubSpot, ClickUp) — an authorisation window opens.
  • API key — Ragen asks for your key for that service.
  • No credential — it connects immediately.
3

Authorise in the provider's window

For an OAuth connector, sign in and grant the requested permissions. The exact scopes depend on the connector.
4

Confirm the connection

After authorising, the browser redirects back to Ragen. The connector’s status changes to Connected. Your credentials are now stored securely.
Ragen stores your OAuth tokens securely in an isolated credential store, separate from the main application. Tokens are encrypted at rest and are never accessible to other users or organisations.
Connectors are per-user, not organisation-wide. Each team member must connect their own account for each service they want to use. An admin connecting Google Drive does not give anyone else access to that Drive.

​
Importing a Google Drive folder

If you connect Google Drive, you can import an entire folder’s contents into a project knowledge base — up to 200 files per import.
1

Open a project knowledge base

Navigate to the project where you want to import files and open the Knowledge Base tab.
2

Choose Import from Google Drive

Click Add files and select Import from Google Drive. The folder picker dialog opens.
3

Select a folder

Browse your Drive and select the folder you want to import. Ragen lists the files it finds in the folder — up to 200 — and shows you what will be imported.
4

Confirm the import

Click Import. Ragen uploads the files to storage and starts the ingestion pipeline in the background. Large folders may take a few minutes to finish indexing.
5

Verify indexed files

Once ingestion completes, the imported files appear in your knowledge base. Each file shows its source Drive ID so you can trace it back to the original.
Auto-sync with Google Drive is not yet available. If the source folder changes, re-import it to update the knowledge base. The import limit is 200 files per folder.

​
Using connectors in chat

Once a connector is active, Ragen’s assistants automatically include it as a tool source during conversations. You don’t need to do anything special — just ask a question that requires that data, and the assistant queries the connector in the background before answering.
If an assistant isn’t using a connector you’ve connected, check Settings → Connectors to confirm the connection is healthy. A connector with an expired or revoked token shows an error and needs to be reconnected.
Ragen prefixes each connector’s tools with its slug, so a weather connector’s find_place tool reaches the model as weather__find_place. You’ll see these names in an assistant’s reasoning when it uses one.

​
If a connector you expect isn’t there

A platform admin can see all of this at once in Connector Health in the admin panel.