Vibe Prospecting MCP connector for AI agents

Vibe Prospecting MCP tools for AI agents

CALL ANY TOOL

6 tools covering search, enrich, get.

vibeprospectingmcp_autocomplete

Autocomplete

Autocomplete values for business filters based on a query. Supports fields: naics_category, linkedin_category, company_tech_stack_tech, job_title, business_intent_topics, city_region. Never use for fields not in this list. Prefer linkedin_category over naics_category unless the LinkedIn result is too broad. Do not call autocomplete for country or region codes — use ISO codes directly.

Parameters

Name

Type

Required

Description

field

string

Required

The field to autocomplete. Only use fields listed here. Never use autocomplete for a field not in this list.

query

string

Required

The query to autocomplete

tool_reasoning

string

Required

The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Maximum 2000 characters.

session_id

string

Optional

Session ID for tracking tool calls within the same user request context. Reuse when continuing the same request; omit to create a new session.

vibeprospectingmcp_enrich_business

Enrich business

vibeprospectingmcp_enrich_prospects

Enrich prospects

vibeprospectingmcp_estimate_cost

Estimate cost

vibeprospectingmcp_export_to_csv

Export to csv

vibeprospectingmcp_fetch_businesses_events

Fetch businesses events

vibeprospectingmcp_fetch_entities

Fetch entities

Find companies and/or prospects using any combination of filters (returns ~10 sample rows for exploration, no charge). Use entity_type 'prospects' when the request involves people in any way; use 'businesses' only when the request is purely about companies. Filters requiring autocomplete first: linkedin_category, naics_category, job_title, business_intent_topics, company_tech_stack_tech, city_region (USA cities). Make ONE comprehensive fetch call — multiple calls combining filters that could be merged are forbidden.

Parameters

Name

Type

Required

Description

entity_type

string

Required

REQUIRED: The type of entity you want as final output. Use "businesses" for company data, "prospects" for people/contact data. This helps disambiguate when filters alone don't clearly indicate intent.

filters

object

Required

Combination of filters to narrow down results. All filter fields are optional. Filters requiring autocomplete first: linkedin_category, naics_category, job_title, business_intent_topics, company_tech_stack_tech, city_region (USA).

tool_reasoning

string

Required

The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters.

businesses_reference_table

string

Optional

OPTIONAL: Only use to REFINE prospects from a previous fetch-businesses result. For fresh searches, use company filters directly with entity_type: "prospects" instead. MUST be provided with a session_id.

estimate_cost

boolean

Optional

No description.

exclude_key

string

Optional

Exclude key to avoid returning previously seen entities. Use 'prospects' or 'business' for the tenant-global exclude list, or pass a specific dataset_id from get-dataset or export-to-csv.

max_per_company

number

Optional

Maximum number of prospects to return per company. Only applicable for prospect queries. CRITICAL: DO NOT use unless explicitly requested by the user.

number_of_results

number

Optional

Number of results to return. Defaults to 50 if not specified. Use the exact number requested by the user.

session_id

string

Optional

Session ID for tracking tool calls within the same user request context. Reuse when refining or continuing the same user request; omit to create a new session for a distinct new request.

vibeprospectingmcp_fetch_entities_statistics

Fetch entities statistics

vibeprospectingmcp_fetch_prospects_events

Fetch prospects events

vibeprospectingmcp_get_dataset

Get dataset

vibeprospectingmcp_match_business

Match business

vibeprospectingmcp_match_prospects

Match prospects

vibeprospectingmcp_show_pricing_plans

Show pricing plans

vibeprospectingmcp_show_sample

Show sample

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="vibeprospectingmcp")

mcp = MultiServerMCPClient({
    "vibeprospectingmcp": {
        "url": "https://mcp.scalekit.com/vibeprospectingmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "vibeprospectingmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/vibeprospectingmcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "vibeprospectingmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/vibeprospectingmcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="vibeprospectingmcp")
# Connect to MCP at https://mcp.scalekit.com/vibeprospectingmcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Present the final sample rows to the user from a fetch, enrich, or events exploration table?

Copy the prompt

Copied

Show Vibe Prospecting credit package pricing in an interactive widget?

Advanced

Copy the prompt

Copied

Match specific individuals to get their Explorium prospect IDs?

Copy the prompt

Copied

Get the Explorium business IDs from business name and/or domain in bulk?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Vibe Prospecting MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Vibe Prospecting MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Vibe Prospecting MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Vibe Prospecting MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Vibe Prospecting as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Vibe Prospecting API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Vibe Prospecting?
Yes. Pass a tool name filter to listScopedTools so the marketing agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Vibe Prospecting.

What happens when a user revokes Vibe Prospecting access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Whose Explorium credits does lead enrichment consume?
The authorizing user's. Enrichment, list building, and CSV exports run against that user's Vibe Prospecting account and quota, so spend attribution stays clean per rep.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit