Vibe Prospecting

Power your chat with live B2B data — build lead lists, research companies, enrich contacts, and personalize outreach, all from inside your AI assistant.

Vibe Prospecting is a remote MCP server. There's nothing to run locally and no API key to manage — you connect over a single URL and sign in through your browser on first use.

MCP endpoint: https://vibeprospecting.explorium.ai/mcp

What you can do

• 🔎 Find companies by name, domain, industry, size, location, tech stack, and more

• 👤 Discover & enrich contacts — roles, profiles, and buying signals at any company

• 🏢 Research firms — firmographics, technographics, funding, competitors, and challenges

• 📈 Analyze & export — preview a sample instantly, then export the full dataset to CSV when you're ready

You always see a sample preview first (5–10 rows). The full dataset is only processed when you explicitly ask to export — so exploring is fast and credit-friendly.

Related MCP server: scrapercity-cli

Installation

Pick your tool below. All clients connect to the same remote endpoint and authenticate through your browser (OAuth) on first use.

Claude Code ⭐ recommended

One line — paste it into your terminal:

claude mcp add --transport http vibe-prospecting https://vibeprospecting.explorium.ai/mcp

Then start (or restart) Claude Code and run a prompt that uses it (see Examples). The first call opens your browser to sign in. Verify the connection anytime with:

claude mcp list
# vibe-prospecting: https://vibeprospecting.explorium.ai/mcp - ✓ Connected

Cowork & Claude Desktop

Add it as a custom connector through the UI (no terminal needed):

1. Open Customize → Connectors in Chat/Cowork/Code in Claude Desktop

2. Click the + next to Connectors and choose Browse connectors

3. Under Anthropic & Partners look for Name: Vibe Prospecting — URL: https://vibeprospecting.explorium.ai/mcp

4. Click + and then click Install, then follow the sign-in prompts to grant access

Once added, Vibe Prospecting's tools are available to Claude automatically.

Codex CLI

One command — Codex detects OAuth automatically and opens your browser to sign in:

codex mcp add vibe-prospecting --url https://vibeprospecting.explorium.ai/mcp

Confirm it's connected with codex mcp list (look for Auth: OAuth), or start a Codex session and run /mcp to see its tools. If you ever need to re-authenticate, run codex mcp login vibe-prospecting.

No native OAuth in your Codex version? Use the universal mcp-remote bridge instead. Add this block to ~/.codex/config.toml — it opens the browser for sign-in on first use:

[mcp_servers.vibe-prospecting]
command = "npx"
args = ["-y", "mcp-remote", "https://vibeprospecting.explorium.ai/mcp"]

Gemini CLI

Install the extension directly from this repository:

gemini extensions install https://github.com/explorium-ai/vibeprospecting-mcp

The extension is loaded and managed automatically by Gemini CLI, and OAuth sign-in is handled on first use. See the Gemini CLI extensions docs for details.

Hermes

Hermes uses the same remote endpoint, but its CLI needs the server written to config plus an explicit OAuth login. Run these in your terminal:

1. Register the server — write both keys directly under mcp_servers:, which is the namespace hermes mcp login (and the runtime) read from:

   hermes config set mcp_servers.vibe_prospecting.url "https://vibeprospecting.explorium.ai/mcp"
   hermes config set mcp_servers.vibe_prospecting.auth oauth

   Don't use hermes mcp add: in a non-interactive shell it can fail mid-way and save a disabled, half-written entry under mcp_servers: — auth set but url dropped — which then fails at login. Setting both keys yourself avoids it, and if you already hit it, the same two commands repair it. (A url showing up elsewhere in config doesn't count — hermes mcp login only reads mcp_servers:.)

2. Sign in — opens your browser to authenticate:

   hermes mcp login vibe_prospecting

   On a remote, SSH, or Docker host, the browser can't reach the local callback after you approve — that's expected. Copy the full URL from the address bar and paste it back at the Hermes prompt.

3. Verify & use — hermes mcp list should show vibe_prospecting as authenticated. Start a new chat so the mcp_vibe_prospecting_* tools load, then try a prompt from Examples. To get a CSV, ask Hermes to "export and download" (exports return a link, not the file itself).

Connection drops on the first call? The default MCP discovery timeout is too short for the OAuth handshake — raise it: hermes config set mcp_discovery_timeout 10.

Examples

Once connected, just ask in plain language:

Who should I contact for a partnership with monday.com? Get anyone who can
promote a partnership with them, with all the contact details you can find.

What are the business challenges of Amazon?

Get the engineering leadership team at Palo Alto Networks.

Find B2B SaaS companies in New York with 50–200 employees, then enrich
the decision-makers and export the list to CSV.

Authentication & credits

• Sign-in: OAuth through your browser on first use — no API keys to copy or store.

• Free to explore: searching and previewing samples is lightweight. Exporting the full dataset uses credits.

• Pricing & credits: https://www.vibeprospecting.ai/pricing

Troubleshooting

• Failed to connect / error -32000 in Claude Code — this happens with the old local uvx vibeprospecting-mcp (stdio) command. That path is deprecated; use the --transport http command above instead.

• Connector won't connect in Cowork/Desktop — the server is reached from Anthropic's cloud, so the URL must be publicly reachable. Double-check the URL is exactly https://vibeprospecting.explorium.ai/mcp.

• Re-authenticate — in Claude Code run claude mcp remove vibe-prospecting then re-add it; in Codex run codex mcp login vibe-prospecting again; in Hermes run hermes mcp login vibe_prospecting again.

Support & documentation

• API Documentation

• Support & Help Center

• Vibe Prospecting Homepage

For technical support, contact support@vibeprospecting.ai.

License

This project is licensed under the Explorium Term of Service. See Term of Service for details.