- Home
- Resources
- Integrations
- Sprouts Data Intelligence
Claude Sprouts Data Intelligence connectorWhat Claude can do in your Sprouts Data Intelligence account.
The Claude Sprouts Data Intelligence connector exposes 7 tools. 1 reads the prospect database, 4 change something in your Sprouts workspace, 2 aren't settled by any source. Below: what Claude finds, what it saves, and what spends credits.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your prospecting
No more ticking filters one by one in a sales data tool. You describe the audience you're after in a full sentence, and Claude queries the Sprouts.ai B2B database for you: contacts, companies, job titles, industries, locations, company sizes. The results land in the conversation.
Build a prospect list from one sentence. sprouts_data_intelligence takes a fully written request, something like “VPs of Marketing at US SaaS companies using HubSpot”, and returns matching profiles. If you've set up an ideal customer profile, the search can be narrowed to it.
Push the right profiles into Sprouts. Once the list is trimmed, move_to_sprouts sends the selected contacts or accounts to your Sprouts platform, using the IDs from the search results. That step spends credits.
Pin down your target once. icp_analysis sets up your ideal customer profile, then scores prospects against it. Without targeting criteria filled in, Sprouts warns that every fit score stays at zero.
What the sheet doesn't say: two tools, query_refinement and search_history, are described by the publisher, yet nobody states whether they save anything. Signing in requires a work email address. And nothing runs by itself: no search reruns on a schedule. That kind of chaining is an automation tool's job, a different trade; the Integrations hub covers that side.
The vocabulary in one minute
Five words you'll meet while connecting Sprouts.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can withdraw it anytime.
- Approval
- The confirmation Claude waits for before going through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service at all.
Connect Sprouts Data Intelligence to Claude in three steps
- 01
Find Sprouts in Claude
In Claude's settings, open Customize, then Connectors, and locate Sprouts Data Intelligence in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first so that each member can connect afterwards.
- 02
Start the connection
Click Connect on its row, then sign in to Sprouts in the window the service opens itself. If the link breaks at some point, use Disconnect and connect it again from that same row.
- 03
Read the authorization screen
Before accepting, read the authorization screen: it belongs to Sprouts, not Claude, and it decides what the access covers. Anything granted there can also be withdrawn later from your Sprouts account.
The 7 tools, grouped by what they do
Sprouts Data Intelligence gives Claude 7 tools: 1 that read your account, 4 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it changes, and what the sources don't let us classify. Names stay exactly as Claude shows them.
- 1 read
- 4 write
- 2 not documented
What Claude reads (1)
1 toolOne tool that searches the prospect database without touching anything.
sprouts_data_intelligence
Searches contacts and companies in the Sprouts B2B database from a complete sentence written the way you would say it. If an ideal customer profile is set up, the search can be filtered to it.
Sourcesprouts-mcp-server.kartikay-dhar.workers.dev · October 1, 2026 ↗
What Claude changes (4)
4 toolsFour tools that act on your Sprouts workspace. No source details their confirmation, so the general rule below applies.
move_to_sprouts
Approval: see the ruleSends contacts or accounts found during a search to your Sprouts platform. The IDs must come from the search results.
Sourcesprouts-mcp-server.kartikay-dhar.workers.dev · October 1, 2026 ↗
query_templates
Approval: see the ruleBrowses, applies, creates or deletes reusable prospect-search templates, so you restart from a proven query instead of rewriting it each time.
Sourcesprouts-mcp-server.kartikay-dhar.workers.dev · October 1, 2026 ↗
icp_analysis
Approval: see the ruleSets up your ideal customer profile (industries, company sizes, job titles, seniority, locations), then scores prospects against it. Sprouts also files profile updates, reports, a history and profile removal under it.
Sourcesprouts-mcp-server.kartikay-dhar.workers.dev · October 1, 2026 ↗
sprouts_user_preferences
Approval: see the ruleConfigures and saves your preferences for field selection and response optimisation, so later searches take them into account automatically.
Sourcesprouts-mcp-server.kartikay-dhar.workers.dev · October 1, 2026 ↗
Unsettled (2)
2 toolsThe publisher describes both tools, but its own annotations don't mark them read-only. No source says whether they only look things up or also save something.
query_refinement
Sprouts presents this tool as an analysis of a prospect-search query, with suggestions to sharpen it by location, industry, size or job title. Its annotations nevertheless don't mark it read-only, and no source settles its effect on your workspace, so the general approval rule applies.
search_history
Per the publisher, this tool shows your past searches and the patterns across them, so you can run one again. Its annotations don't class it as read-only though, and no source says whether it only looks things up, so treat it under the general approval rule.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the conversation, right when it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time. They can also cap what a connector may do across the organisation, keeping search open and closing transfers, for example. Nobody bypasses that from their own account. Finally, Claude works with your Sprouts access and nothing more than that: whatever your own account can't open stays closed to it too.
Which plans it's available on
Of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer isn't published anywhere: it's a real gap in the catalogue.
The general rule, though, is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before each member can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector isn't an automation: Claude calls these tools while it answers you, and nothing kicks off when a new prospect appears in the database. Only the publisher documents this connector.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge isn't a security audit, and Anthropic says so on every sheet: it doesn't choose the tools a publisher exposes or vouch for how they behave. Connect only what comes from a publisher you trust, here Sprouts.ai. Other connectors are listed on the Claude integrations page.
Need help connecting Sprouts Data Intelligence to Claude?
A person reads every message.