Most sales intelligence platforms assume you want to click through dashboards. Search here, filter there, export, re-import, repeat. But a growing number of BD professionals, RevOps teams, and technically minded recruiters are asking a different question: why can't I just tell my AI assistant to do this?

Kolvera MCP lets compatible clients call documented sales intelligence tools. Use a clear task and inspect the proposed action instead of relying on a frozen catalogue size.

What Is MCP and Why Does It Matter for BD Teams?

MCP provides a structured way for an AI client to access documented tools and data. It does not eliminate mistakes or unsupported conclusions: review inputs, returned evidence and proposed actions before relying on the result.

Natural-language tool use can help with discovery, enrichment and campaign work when the account has access. Check the live reference for required inputs and supported actions.

A natural-language client can request documented Kolvera actions subject to account access, costs and connector support. Bullhorn and JobAdder cannot currently be enabled pending vendor access; one prompt does not guarantee enriched records or a completed CRM handover.

What You Can Do With Kolvera's MCP Tools

Choose a bounded task from the current tool catalogue. Start by reviewing the available records and proposed action, then confirm permissions, connector status and any credit cost before asking the client to make changes.

Here's what the MCP tools cover:

  • Contact enrichment: New valid-email contacts cost 2 credits. Phone costs depend on fresh, cached, already-owned and supported BYOK outcomes; check the credit guide.
  • Deep Research: Discover companies from a reviewed brief for 6 credits per run and 4 per expansion; contact enrichment is separate.
  • Company discovery: Browse shared company records free; adding new valid-email contacts is a separate 2-credit action per contact.
  • AI profile generation: Draft a profile from supplied material, review it, and confirm the 3-credit action cost.
  • Campaign management. Create, update, pause, and monitor AI email campaigns with A/B/C variant tracking.
  • CRM sync: Confirm connector availability and supported record actions. Atlas, HubSpot, Spott and Manatal are directly available; Bullhorn and JobAdder cannot currently be enabled pending vendor access.

A conversational interface can reduce context switching between supported tasks. Completion time still depends on the requested actions, available data and review; no fixed seconds-versus-minutes saving is established here.

Deep Research discovers companies from your brief; review the results before using them. A run costs 6 credits and an expansion costs 4 credits. Company discovery does not by itself return verified personal phone numbers or guarantee complete coverage. New-contact enrichment is a separate action; see the current credit guide.

Real Prompts, Real Workflows

Adapt these examples to the live tool catalogue and your account. Supply reviewed inputs, inspect the proposed actions and confirm any paid or write action before relying on an outcome.

Example: ask the client to discover candidate companies matching a supplied brief and show the sources and assumptions to review. Deep Research costs 6 credits per run and 4 per expansion; it does not guarantee a complete report of every buying trigger within a specified period.

Example: browse companies matching reviewed criteria, inspect the results, then select contacts for enrichment. Confirm the email and outcome-dependent phone costs before proceeding, and review campaign membership separately from discovery.

A safer prompt is: "Using this reviewed summary of successful clients that I supply, draft a target profile and identify assumptions for me to check." Confirm the action cost before running it. A CRM connection does not guarantee access to deal history.

MCP-based workflows represent the next step: not just AI writing your emails, but AI executing multi-step BD processes on your behalf.

New email enrichment costs 2 credits per valid contact found. Fresh direct-dial and company-line phone finds cost 2 credits; cached company lines cost 1 credit, while an eligible number already on the account or a supported BYOK lookup may cost no Kolvera credits. Availability and plan gates apply. Check the current credit guide before running enrichment.

Beyond MCP: The Full Developer Surface

MCP is one integration option. Use the REST API, CLI or webhooks where the documented interface fits a programmatic task; confirm the current scope in developer documentation.

For a custom integration, use documented events and supported actions, with appropriate receiver handling and account permissions. Review proposed outreach and activation rules; a webhook does not guarantee detection of a commercial trigger or authorise unattended sending.

The integration layer is where the real time savings compound.

Custom automations should use documented actions and events, with explicit permissions and error handling. Tool and endpoint counts are not a substitute for testing the required workflow.

Getting Started With Kolvera MCP

Follow the current client-specific setup guide. Sign-in and configuration vary by client; no universal setup time or API-key recipe is established here.

For CRM work, check connector availability first. Bullhorn and JobAdder cannot currently be enabled while vendor access is pending; MCP does not remove that restriction.

Compare current Kolvera plans using the same billing term, seat requirements and expected usage. Pro and Scale have different allowances and feature gates. Annual rates require annual billing; Monthly plan credits reset each billing period; purchased top-up credits remain available until used.

If you're curious about what natural language BD looks like in practice, book a demo or check pricing to see which plan fits your team. You can also browse more technical guides on the Kolvera blog.

FAQ

Does Kolvera's MCP integration work with Claude Desktop and Cursor?

Use a compatible client and its current setup instructions. Verify the connected Kolvera account and a bounded read action before authorising writes.

How much does it cost to use Kolvera through MCP?

MCP actions use the applicable Kolvera plan gates and credit rules. Check current action costs, including 3-credit AI profile generation and outcome-specific phone charges.

Can I push MCP results directly into my CRM?

A CRM prompt can use only the connector scope available to the account. Atlas, HubSpot, Spott and Manatal are directly available; check the directory for request-only and pending connectors.

What's the difference between MCP tools and the REST API?

MCP supports assistant tool calls; REST API actions support programmatic integrations. Select the documented interface for the task and verify the required action rather than assuming complete feature parity.

Does Kolvera have a built-in dialler for calling enriched contacts?

Customer calling uses Ringover or Dialpad on Pro or Scale, with provider terms and charges. Native voice and native SMS have separate restricted access; phone enrichment alone does not place a call.