vibeprospecting-mcp README

The project's README from github.com/explorium-ai/vibeprospecting-mcp. As one markdown file: README.md.

Vibe Prospecting

Vibe Prospecting Logo

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

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.


Installation

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

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.

Manus

Connect Vibe Prospecting from Manus’s built-in connectors UI (no local server or API key):

  1. Open the connectors menu (or choose + Add connectors).
  2. Search for vibe.
  3. Under Apps, select Vibe Prospecting (“Build B2B lead lists and enrich companies and contacts”).
  4. Confirm the connector details (MCP by Explorium), then click Try it out / connect and complete the browser sign-in.

Once connected, use Vibe Prospecting from a Manus chat with prompts like those in Examples.

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


Troubleshooting


Support & documentation

For technical support, contact [email protected].

Directory listings

Listed in the Claude Market MCP directory.

License

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

vibeprospecting-mcp (explorium-ai/vibeprospecting-mcp)

oauth2
Searching Database…

What is this?Vibe Prospecting is a remote MCP server that connects your AI assistant to live B2B data, letting you build lead lists, research companies, enrich contacts, and personalize outreach without leaving the chat.
Is this something I install and run locally?No, it is a remote MCP server hosted in the cloud — you don't run any code on your machine, you just point your AI client at a single URL and authenticate once via your browser.
How do I connect it to my AI assistant?Pick your client: Claude Code uses a one-line add command, Claude Desktop/Cowork lets you add it as a custom connector in the UI, and Codex CLI, Gemini CLI, Manus, and Hermes each have their own connect step, but all of them point to the same remote endpoint and authenticate via browser OAuth on first use.
Do I need an API key to use it?No API key is required — authentication happens through a one-time OAuth sign-in in your browser; you just need a supported MCP client such as Claude Code, Codex CLI, Gemini CLI, Manus, or Hermes.
Does exporting data cost anything?Searching and previewing a 5-10 row sample is free and lightweight, but exporting the full dataset to CSV consumes credits, so costs only kick in once you explicitly ask for the complete export.
Is it really MIT-licensed like GitHub shows?Despite the GitHub license label, the README states the project is actually governed by Explorium's own Terms of Service rather than a standard open-source license.
Which AI clients can I use this with?It supports Claude Code, Claude Desktop/Cowork, Codex CLI, Gemini CLI, Manus, and Hermes, all connecting to the same remote MCP endpoint.
What can I actually ask it to do?You can search companies by name, domain, industry, size, location, or tech stack, enrich contacts with roles and buying signals, and pull firmographics, technographics, funding, and competitor data.
Why does it show a sample first instead of the full dataset?Previewing 5-10 rows before export keeps exploration fast and credit-free until you explicitly ask for the full CSV export.
What happens if I'm still using the old local uvx command?The old local 'uvx vibeprospecting-mcp' (stdio) command is deprecated and causes connection errors — switch to the remote '--transport http' connection method instead.
Size
0.1 MB
Stars
197
Age
8mo
Commits · 90 Days