Browse documentation

Connectors (MCP)

Connect agents to external apps and data through MCP connectors: activate one, connect it in a vault, and choose which of its tools your agents may use.

A connector plugs an outside app into SPARK so your agents can use it. Connectors follow the Model Context Protocol (MCP), an open standard for exposing tools and data to AI agents. Each active connector contributes a set of tools that you can then give to an agent.

A connector that reaches an outside service also needs an account to act as. That connection is stored in a vault, and SPARK asks for it right after you activate the connector, in the same dialog. This page covers activating and connecting from the Connectors page; Connect an account goes through each way of signing in.

Open the Connectors page

Open Agent Studio, then Connectors. The page, External apps whose tools your agents can use., splits connectors into two foldable sections, each with its count:

  • Active: connectors currently offering tools to your agents. Spark comes first: it is the built-in connector for the platform's own tools, carries a Built-in badge, and is always active.
  • Available: connectors you can activate.

Each row shows the connector's logo and name, what it does, how many tools it has, and its ⋯. Marks after the name say more: a warning triangle on an active connector that none of your vaults connects yet (Not connected to any of your vaults), Built-in on Spark, and a flask on a connector that is still Experimental.

ConnectorsExternal apps whose tools your agents can use.Active (2)SparkBuilt-inBuilt-in platform tools for data objects, files, tasks,…Microsoft 365Connect to Microsoft 365 to search, read, create,…28Available (28)AirtableSpreadsheet-database hybrid - read and write…19Clarity AIESG and sustainability data - company impact, risk,…4FactSetFactSet financial data and analytics - fundamentals…16BigQueryQuery Google BigQuery datasets and tables…5
The Connectors page: Active connectors offer tools now; Available ones can be switched on.

Activate a connector

Click a row under Available. Its dialog says what the connector does and offers one button: Activate (Activate Microsoft 365 to offer its tools to your agents.). A row's ⋯ has Activate too, and View tools & instructions, which opens the connector's page so you can look first.

Microsoft 365Connect to Microsoft 365 to search, read, create, change and deleteSharePoint and OneDrive files, Outlook mail and calendar events, andTeams chat messages.Activate Microsoft 365 to offer its tools to your agents.Activate
An available connector's dialog: Activate first.

Connect it in a vault

A connector that signs in to an outside service goes straight on to Connect in the same dialog: choose the Vault that keeps the connection (Agents that use this vault can use Microsoft 365's tools.), then sign in or paste the key, as the connector asks. SPARK says Microsoft 365 connected and which vault holds it. Right after activating, Skip for now leaves the connection for later.

The vault decides who the connection works for: in your personal vault it works only when you ask, in a shared vault for everyone, in agents and in workflows. See Vaults.

Connect Microsoft 365OAuth 2.0Microsoft 365 uses OAuth. You'll be sent to Microsoft 365 to grantaccess. Choose which vault to store it in.InstructionsVaultClaire's vaultAgents that use this vault can use Microsoft 365's tools.How do you want to connect?One-click (use the Microsoft 365 app we manage)Bring your own Microsoft 365 OAuth appRequested scopes: offline_access, User.Read, Files.ReadWrite.All,Sites.Read.All, Mail.ReadWrite, Mail.Send, Calendars.ReadWrite,Chat.ReadWrite, People.ReadConnect with Microsoft 365Skip for now
Right after Activate: pick the vault that keeps the connection, then sign in.

To connect later, open the row's ⋯ and choose Connect (it shows while none of your vaults connects the connector), or use Connect on the connector's page. A connector that holds a connection already offers Reconnect and Disconnect there instead.

Open a connector

Click an active connector's row, or choose Open connector (View tools & instructions for one that is off) from its ⋯. Its page has:

  • A Set up card, for a connector that needs a connection: whether it is connected yet (Add a credential to a vault your agent uses., or the vaults it is connected in), how it signs in, numbered steps for getting the key or registering the app at the provider and then connecting it in SPARK, and Bring your own app folded under them where that applies. Its footer has Connect (or Reconnect and Disconnect) and a link to the provider's documentation.
  • Its tools, grouped by what they do, such as Read and Write, each with a switch to allow or disallow it across the workspace. See Tools.
GitHubRead and act on GitHub repositories, issues, pull requests and Actions via the GitHub API.Set up GitHubAPI keyAdd a credential to a vault your agent uses.1.In GitHub, open Settings → Developer settings → Personal access tokens → Fine-grained tokens.2.Click Generate new token, give it access to the repositories the agent should reach, and select therepository and account permissions needed by the tools you plan to use.3.Copy the token. It starts with github_pat_.4.Select Connect, then choose the vault that keeps the credential. Enter the credential fields and select Save.5.In the agent editor, select that Vault and add the connector’s tools under Tools.ConnectGitHub documentationRead (18)Mcp Github Actions ListList GitHub Actions workflows and runs.Mcp Github Get CommitGet a single commit with its diff.Mcp Github Get File ContentsRead the contents of a file or directory.
A connector's page: follow its setup steps, connect it, and allow or disallow individual tools.

To switch a connector off, choose Deactivate from its ⋯. The built-in Spark connector's Deactivate is disabled, because Built-in connectors are always available to agents.

What is in the catalogue

SPARK lists 30 connectors. The page itself is the list to trust: the catalogue grows between releases.

  • Built in: Spark.
  • Productivity and collaboration: Microsoft 365, Gmail, Google Calendar, Google Drive, Slack, Notion, Airtable, monday.com, HubSpot and Intercom.
  • Engineering: GitHub, Linear and Supabase.
  • Market and reference data: OpenFIGI, FactSet, LSEG, Moody's, Morningstar, MSCI, S&P Global, ICE Data Services and Clarity AI.
  • Google Cloud: BigQuery, Cloud Storage, Cloud Logging, Cloud Run, Cloud SQL and Firestore.
  • Web search: Tavily.

Microsoft 365

One connector covers SharePoint, OneDrive, Outlook and Teams. Its 28 tools let an agent search, read, create, change and delete SharePoint and OneDrive files, search and send Outlook mail and manage calendar events, and search and send Teams chat messages. It signs in with OAuth 2.0.

It needs two approvals:

  • Your organisation's, once. A Microsoft 365 admin needs to approve Spark once for your organization: Microsoft leaves these permissions to a tenant admin. After that, each person chooses One-click and signs in with their work account.
  • Yours, for each action, if you want it. Every Microsoft 365 tool that sends, creates, changes or deletes something is marked as such, so an agent with the Approve actions in connected apps guardrail stops and asks you before it runs one. See Guardrails.

OpenFIGI

OpenFIGI maps ISINs, CUSIPs, SEDOLs and tickers to FIGIs, and searches instruments. Its key is free from openfigi.com, and it connects only in a shared vault: the key is the workspace's, for its agents and workflows alike. A personal vault does not offer it.

Agents get its tools to map identifiers, search instruments and list the values its filters accept. Workflows get two steps: Map to FIGI, for up to 10,000 identifiers a run, and Search OpenFIGI.

GitHub and Linear

GitHub reads and acts on repositories, issues, pull requests and Actions. Linear reads and manages issues, projects, comments and docs. Both authenticate with a key you create at the provider: a GitHub personal access token (it starts with github_pat_) or a Linear personal API key (it starts with lin_api_). The connector's page walks through creating each one.

Many connectors carry a flask marking them Experimental: visible but not fully wired yet, for example because the provider's OAuth app or an enterprise entitlement is still pending. They include Microsoft 365, Gmail, GitHub, Linear, Slack, Google Drive and Google Calendar, the Google Cloud connectors, OpenFIGI and most market-data connectors. Hover the flask for the reason, and test such a connector on your own workspace before you rely on it.

The Google Cloud connectors authenticate with a service account key rather than a person's sign-in, which suits an agent reading a warehouse on a schedule. See Connect an account.

Connectors fail on their own

Each connector's tools load independently. A connector that fails to respond, or whose connection is missing or expired, drops only its own tools from a run: the agent keeps working with every other connector that is still connected.

An agent only gains a connector's tools when you add them to it on its page. Activating the connector makes the tools available; selecting them gives them to a specific agent, and its Vault must hold the connection.

Where to go next