Skip to content

raia Command · Section

Connectors

30+ integrations, import scope, sync history, and Agent Access (MCP).

Connectors pull content from external systems into a project folder so it can be converted, trained, and processed like any uploaded document. 30+ pre-built integrations cover storage, knowledge bases, CRMs, ticketing, engineering tools, meetings, the web, and MCP bridges. Each connection is per-user, so your credentials stay yours.

In this section

  • Authenticate a connector by API key, token, or OAuth and pick a target folder.
  • Choose import scope, combined vs. individual output, and auto-push to agents.
  • Read Sync History, cancel a long import, and resume where it left off.
  • Use the Agent Access (MCP) tab to expose a connector's live tools to an agent.
An MCP connector page in Command, showing the Airtable workspace header, its MCP endpoint, and the steps to generate a token
MCP connectors get their own page: the header describes the integration, the MCP endpoint is ready to copy, and the steps below walk you through generating the token your agent will use.
The lower half of an MCP connector page in Command, with How to connect steps, Details accordions, and a note that Command stores nothing for this connector
The rest of the page shows how to connect the agent, collapsible details for scopes and tools, and a note that Command stores nothing for this connector — the token lives only in the agent's MCP Skill settings.
A connector setup page in Command, showing the Setup & Import tab, setup instructions, and the connection form with authentication and credential fields
Import connectors open a setup page: the Setup & Import tab lists the provider's setup instructions, and the form below collects the authentication method and credentials before Connect starts the import.
01

What's inside

  1. 01

    Connecting and importing

    Open a connector card, complete the connect flow (API key, token, or OAuth), then choose what to import and which project folder it should land in. Imported files behave exactly like uploads — convert, train, and process them normally. Manual re-sync refreshes content on demand, and disconnecting runs through the backend so it always succeeds.

  2. 02

    Output shape and auto-push

    Where a connector supports it (TeamSupport, Confluence, and others), choose Combined output — one merged Markdown file, sharded around ~10MB — or Individual files, and toggle auto-push-to-agents so new imports queue for training automatically.

  3. 03

    Sync history and cancellation

    Every connector records sync history in a shared format: when each import ran, how many items it touched, and any errors. Long-running imports can be cancelled mid-flight, and most connectors resume from where they stopped.

  4. 04

    MCP Server connector

    Point Command at any remote Model Context Protocol server over Streamable HTTP and ingest its output as Markdown — either by picking resources from resources/list, or by calling tools and saving the responses.

  5. 05

    Agent Access (MCP)

    Salesforce, Zendesk, Zoho, HubSpot, Jira, Bitbucket, Gmail, tldv, and Zapier expose an Agent Access tab that reuses the existing connection's credentials. Tools are filtered by the scopes the token actually holds, and an optional 'Allow agent to create/update records' toggle gates write tools.

  6. 06

    Wiring a connector to an external agent

    Option A (recommended): on the connector's page in Command, click Connect to <agent> — a key is minted, the MCP server is registered on the agent, and the binding is tracked for one-click revoke. Option B: create a key from the connector's Agent Access tab and paste the JSON config into the agent's MCP servers list. Revoking the key from the connector page or Settings → Action Keys cuts access immediately.

  7. 07

    File Drop

    File Drop gives an outside sender a private upload address for one chosen Knowledge folder, without requiring a Command account. Create it from Connectors, copy the one-time token, and rotate or revoke it whenever needed. Accepted files follow the normal validation, conversion, privacy scan, retention, and optional agent-training flow. The delivery log records accepted and rejected attempts with a clear reason.

02

At a glance

CategoryExamplesTypical use
StorageGoogle Drive, OneDrive, SharePoint, DropboxDocument libraries
Knowledge basesGitBook, Confluence, HelpJuice, RoboHelp, ServiceNowPublished documentation
CRMSalesforce, HubSpotCustomer context and cases
SupportZendesk, Zoho Desk, Freshdesk, TeamSupport, AutotaskKB articles and ticket history
EngineeringGitHub, Bitbucket, Azure DevOps, JiraRepos, wikis, and issues
MeetingsMicrosoft Teams transcripts, tldvMeeting knowledge
Web & endpointsFirecrawl, Basic Web Scrape, HTTP Endpoint, SOAP EndpointSites and custom APIs
Agent bridges (MCP)MCP Server, Zapier, Gmail, raia CXLive tools instead of imports
03

Related