Connectors

Connectors link your third-party accounts to MCPGate. Once connected, every MCP App you create can selectively expose those services — with full guardrail control over which tools are allowed and how they behave.

How connecting works#

Each connector uses a standard OAuth 2.0 flow. MCPGate handles the token exchange and stores the credentials in your encrypted vault — your AI clients never see them directly. When a tool call arrives, MCPGate injects the token, calls the third-party API, and returns the result.

  1. Go to Connectors in the dashboard.
  2. Click Connect next to the service you want to add.
  3. Approve the OAuth consent screen. You are redirected back automatically.
  4. The connector status changes to Connected. Its tools are now available in every MCP App.
Connectors list showing connected and available services
The Connectors page. Green badge = connected, grey = not yet connected.

Start here

Start with Gmail — it's the most common first connector and demonstrates the full OAuth + guardrail flow in under two minutes.

Token management#

MCPGate stores OAuth tokens encrypted with AES-256-GCM. Tokens are refreshed automatically before they expire. You can revoke a connector at any time from the dashboard, which immediately deletes the stored credentials and disables all related tools across every App.

Available connectors#

MCPGate ships with 14 connectors covering 106 tools across five categories. Click a connector name for its full tool reference and guardrail recipes.

ConnectorCategoryTools
GmailGoogle7
Google CalendarGoogle6
Google ContactsGoogle7
Google DriveGoogle8
SlackMessaging8
DiscordMessaging7
GitHubDevelopment10
LinearDevelopment8
JiraDevelopment8
NotionProductivity7
TrelloProductivity7
AsanaProductivity8
DropboxStorage7
HubSpotCRM8
Total106

Permissions and scopes#

MCPGate requests only the OAuth scopes needed to execute the tools in that connector. Scopes are listed on each connector's reference page. If you connect an account with restricted permissions, any tool that requires a missing scope will return an error rather than silently degrading.

Next steps#

  • Read the per-connector reference pages for tool details and guardrail recipes.
  • See MCP Apps to learn how to expose connector tools to your AI clients.
  • See Guardrails to add allow/deny rules on top of individual tools.