---
title: "Connect FirstSales to Claude and other AI..."
description: "FirstSales now speaks MCP. Connect your workspace to Claude, approve exactly which workspace it can reach, and work with campaigns, leads and analytics throu..."
canonical: "https://firstsales.io/changelog/connect-firstsales-to-claude/"
---

1. [Home](/)
2. [Changelog](/changelog/)
3. Connect FirstSales to Claude and other AI assistants

[All updates](/changelog/)

NewAugust 12, 20265 min read

# Connect FirstSales to Claude and other AI assistants

FirstSales now speaks MCP. Connect your workspace to Claude, approve exactly which workspace it can reach, and work with campaigns, leads and analytics through conversation.

New

Connect FirstSales to Claude and other AI assistants

Developer docs page for the FirstSales MCP server, showing the endpoint and how a client authorises

FirstSales now works as an MCP server, which means you can connect it to Claude and other assistants that support the protocol. Once connected, you can ask about campaigns, pull analytics, work with lead lists, and run operations through conversation instead of through the interface.

## What changed

Everything in FirstSales used to require the interface. That is fine for the work the interface is designed around, and awkward for everything else: a question that spans four screens, a comparison across six campaigns, a summary you want in a different shape than the dashboard provides.

MCP is a standard way for an assistant to talk to a product. Connecting FirstSales through it means an assistant can read your campaigns, look at your analytics, work with your lead lists, and carry out operations, using your permissions and only in the workspace you approved.

The useful part is not that it replaces the interface. It is that questions spanning several screens become one question. "Which of my campaigns had the worst reply rate last month and what did those emails have in common" is a reasonable thing to ask an assistant with access to the data. Answering it by hand means opening six analytics screens and reading a lot of emails.

## How to use it

Start from your assistant. In Claude, add FirstSales as a connector and follow the prompt to sign in.

You will land on a consent screen inside FirstSales. It shows which workspace the assistant is asking for and what it will be able to do. Read it rather than clicking through. If you belong to several workspaces, this is where you choose, and the choice matters: the assistant gets that workspace and no others.

Approve, and you are returned to the assistant with the connection live. From there you ask questions in plain language. There is no query syntax and no need to know how the data is structured.

To revoke access, go to your workspace settings and remove the connection. This takes effect immediately and does not require any action in the assistant.

## Why it matters

The interface is organised around tasks: build a campaign, import a list, check a dashboard. That organisation is correct for doing work and unhelpful for asking questions, because a question rarely respects the boundaries of a screen.

Analysis is where this shows most. Comparing performance across campaigns, finding patterns in which prospects reply, working out whether a change you made three weeks ago had any effect: all of these are answerable from data the product already holds, and all of them are tedious to assemble by clicking.

There is also the matter of where your work already happens. If you are already drafting messaging, thinking through positioning, or planning a campaign inside an assistant, having your actual campaign data in that same conversation removes a great deal of copying between windows.

## What the assistant can and cannot reach

It reaches one workspace, the one you approved. It cannot see other workspaces you belong to, and it cannot reach another organisation's data.

It operates with your permissions. If you are a member rather than an owner, the assistant is a member too, and anything you cannot do it cannot do on your behalf.

It cannot change your billing, remove your account, or alter your security settings. Those are deliberately outside what the connection exposes, regardless of your role.

## Approving safely

Treat the consent screen the way you would treat granting access to any other account. Check the workspace name. Check that you started the connection yourself rather than arriving at it from a link someone sent you.

Grant from the workspace you actually intend to work in. Connecting a production workspace when you meant to connect a test one is the most likely mistake here, and the consent screen names the workspace precisely so that mistake is catchable before it happens.

Review connections periodically in workspace settings. A connection you set up for a project three months ago and have not used since is worth removing.

## What works well and what does not

It is good at questions over data you already have: comparisons, summaries, finding the outlier, explaining what a number is made of. It is good at multi step work where each step depends on reading the last.

It is less suited to bulk operations you would do faster by selecting rows in the interface, and to anything visual. A chart is a chart, and asking for one in text is a downgrade.

## Where it goes wrong

The most common problem is the assistant answering from an old reading rather than checking again. If you asked about a campaign an hour ago and something has changed since, say so and ask it to look again.

The second is scope. An assistant with access to one workspace will answer confidently about that workspace even when you meant another one. If a number looks wrong, check which workspace the connection points at before assuming the number is wrong.

The third is arithmetic across large sets. Asking for a total across thousands of records is a request the assistant will attempt, and the analytics screens are more reliable for that. Use the connection for questions about shape and pattern, and the dashboard for exact totals you are going to report to someone else.

## Working with several people

Each person connects their own assistant with their own account. There is no shared connection, and one person's setup does not give access to anyone else.

That means permissions stay meaningful. If someone on your team cannot see billing in the app, their assistant cannot either, and nothing about the connection changes that.

When someone leaves, removing their account removes their assistant's access at the same time. There is no separate step and no orphaned connection left behind.

## Availability

Available on all plans. Any assistant that supports MCP can connect. Access is granted per workspace and can be revoked at any time from workspace settings.

[ PreviousDeliverability monitoring is back to full coverage](/changelog/deliverability-monitoring-full-coverage/)[Next Run FirstSales from the command line](/changelog/headless-api-and-cli/)