MCP Connections

Extend Quotient by connecting external tools and data sources

MCP (Model Context Protocol) is an open standard that extends the capabilities of Quotient's agent by giving it access to other systems. When you connect an MCP server to Quotient, you're giving it a set of tools it can call during conversations — for example, the ability to look up GitHub pull requests, pull SEO data from Ahrefs, or read documents from Notion.

You can think of it like a universal adapter: once a tool supports MCP, any AI application (including Quotient) can plug into it. Thousands of applications now offer MCP servers, and connecting one to Quotient takes just a few clicks.

A note on how this differs from Quotient's built-in integrations. MCP connections give Quotient tools it can use during conversations — it's like handing a coworker a login to another app. Built-in integrations like your CRM or Slack are more deeply embedded into the platform. Your CRM integration doesn't just give Quotient a tool to call; it continuously syncs your customer data so it can power audience segments, personalization, and reporting. The Slack integration lets you talk to Quotient without leaving your workspace. MCP connections, by contrast, extend what Quotient's agent can do in a conversation, and nothing more.

What You Can Do with MCP

Here are some of the most common ways Quotient customers use MCP connections today.

Bridge the gap between product and marketing. Connect Linear or GitHub so Quotient can read issues, pull requests, and commit history. This is incredibly useful for product marketing — instead of waiting for engineering to write up release notes or explain what shipped, you can ask Quotient to look at the last sprint's PRs and draft a changelog, blog post, or launch email. It saves a huge amount of back-and-forth between teams.

Inform campaigns with SEO data. Connect Ahrefs or Semrush and ask Quotient to pull keyword research, competitor analysis, or backlink data while you're planning a campaign. Instead of switching between tabs and copy-pasting data, you can have a conversation: "What keywords are we ranking for in the enterprise analytics space?" and Quotient will look it up and factor the results into its recommendations.

Give Quotient access to your company knowledge. Many teams keep important context in Notion — product briefs, competitive intel, messaging frameworks, onboarding docs. Connecting Notion lets Quotient read those documents directly, which means it can draw on that context when writing content or making strategic recommendations. You can even ask Quotient to read specific Notion pages and save the key points as memories for future conversations.

Connecting an MCP Server

Navigate to Settings > MCP Servers to see the list of available connections. The marketplace shows all supported providers — just click one to begin the connection process. Most providers use OAuth, so you'll be redirected to authorize Quotient's access and then sent back to the settings page once the connection is established.

Once connected, you don't need to do anything special to use it. Quotient automatically discovers the tools that each connected server provides and will use them when relevant. If you ask Quotient something that one of your connected tools can help with, it will reach for it naturally.

You can disconnect a server at any time from the same settings page using the menu on each connected provider. If a connection stops working (for example, if you revoked access on the provider's side), you can use the Reconnect option in the same menu to re-authorize without removing and re-adding the server.

Custom MCP Servers

The marketplace covers the most popular tools, but MCP is an open standard — thousands of applications and services now offer MCP servers. If you want to connect something that isn't in the marketplace, you can add it as a custom server.

To add a custom server, click Custom Server at the bottom of the marketplace list. You'll need to provide the server's URL and choose an authentication method.

OAuth is the most common authentication method for MCP servers. When you choose OAuth, Quotient will redirect you to the service's login page to authorize access — the same flow you'd use when connecting a marketplace provider. Most major SaaS tools that offer MCP servers support OAuth.

API Key authentication is the alternative. Some MCP servers require you to generate an API key or token in their settings and provide it to Quotient directly. If you're connecting a server that uses API keys, you'll typically find instructions for generating one in that service's documentation, usually under a section called "API Keys," "Tokens," or "Developer Settings."

If you're not sure which authentication method to use, check the documentation for the MCP server you're trying to connect — it will tell you what's supported. OAuth is generally the simpler option when available, since you don't need to manage any keys yourself.