Skip to main content
Connectors integrate external APIs and services as tools in your agents and gateways. Three types: REST, MCP Registry, and Custom MCP.

​
What is a Connector?

A Connector is a bridge to an external service that:
  • Exposes service functionality as tools
  • Handles authentication securely
  • Maps request/response formats
  • Manages credentials and secrets
Think of it as a reusable integration to any external service.

​
Three Connector Types

REST

HTTP API endpointsBest for: Public/private APIs, webhooks

MCP Registry

Services from mcp.runBest for: Pre-built MCP tools

Custom MCP

Your own MCP serverBest for: Custom implementations

​
Connectors vs Other Options

OptionSetupUse Case
REST ConnectorManual configCustom APIs
MCP RegistryGuided setupPre-built tools
Custom MCPYour serverFull control
PluginWASM uploadComplex logic
Built-inAttachCore capabilities

​
Creating a Connector

​
Basic Flow

  1. Choose Type - REST, MCP Registry, or Custom
  2. Configure - Provide endpoints, parameters
  3. Authenticate - Set up credentials
  4. Test - Verify connection works
  5. Attach - Add to agent or gateway

​
For REST Connector

  1. Connectors > Create Connector
  2. Choose REST API
  3. Enter base URL
  4. Define operations (tools)
  5. Configure authentication
  6. Test and save

​
For MCP Registry

  1. Connectors > Create Connector
  2. Choose MCP Registry
  3. Search and select service (e.g., “Airtable”)
  4. Configure environment variables
  5. Authorize via OAuth if needed
  6. Save

​
For Custom MCP

  1. Connectors > Create Connector
  2. Choose Custom MCP
  3. Provide server URL/transport
  4. Configure environment
  5. Authenticate
  6. Save

​
Attaching Connectors

​
To an Agent

  1. Agents > Select Agent > Settings > Capabilities
  2. Click Attach Capability
  3. Select Connectors
  4. Choose your connector
  5. Save

​
To an MCP Gateway

  1. Gateways > Select Gateway > Capabilities
  2. Click Attach Capability
  3. Select Connectors
  4. Choose your connector
  5. Save

​
Authentication Methods

Connectors support multiple auth patterns:
  • No Auth - Public endpoints
  • Bearer Token - API key in Authorization header
  • OAuth 2.0 - Dynamic client registration
  • API Key - Custom header or parameter
  • Basic Auth - Username:password
  • Custom Headers - Any headers needed
All credentials encrypted at rest (AES-256-GCM).

​
Cost

For current pricing details, see Pricing. Costs vary by connector type and usage patterns. Monitor in Account > Usage dashboard.

​
Connector Limits

LimitValue
Connectors per account500
Operations per REST connector100
Rate limitPer-connector configurable
Auth methods5 per connector

​
Per-Type Documentation

Detailed guides for each connector type:

​
Common Connectors

  • Stripe (Payments)
  • GitHub (Code repos)
  • Slack (Messaging)
  • Twitter (Social)
  • OpenWeather (Weather data)
  • Airtable (Spreadsheets)
  • Notion (Notes/databases)
  • Linear (Issues/projects)
  • Salesforce (CRM)

​
Quick Recipes

​
Stripe Payment Gateway

1. Create REST Connector
2. Base URL: https://api.stripe.com/v1
3. Auth: Bearer {sk_live_...}
4. Define: POST /charges
5. Attach to agent

​
GitHub Repository Access

1. Create REST Connector
2. Base URL: https://api.github.com
3. Auth: Bearer {github_token}
4. Define: GET /repos/{owner}/{repo}
5. Attach to agent

​
Airtable Spreadsheet

1. Create MCP Registry Connector
2. Select "Airtable"
3. Enter API key
4. Grant permissions
5. Attach to agent

​
Security

​
Credential Protection

  • All credentials encrypted at rest (AES-256-GCM)
  • Never logged or exposed in UI (last 6 chars only)
  • Rotated regularly
  • Can be revoked instantly

​
Access Control

  • Restrict connector per agent/gateway
  • Audit all connector access
  • Monitor for unusual activity
  • Disable untrusted connectors

​
Troubleshooting

​
”Connection Failed”

  • Verify endpoint URL is correct
  • Check authentication credentials
  • Ensure service is online
  • Try different endpoint (if multiple available)

​
“Authentication Error”

  • Check API key/token format
  • Verify key hasn’t expired
  • Confirm key has required permissions
  • Re-authorize OAuth if needed

​
”Operation Not Found”

  • Verify operation name matches definition
  • Check MCP service supports operation
  • Confirm correct connector attached

​
Next Steps