Vibe Prospecting CLI

Use the CLI: npx @vibeprospecting/vpai@latest. Treat every tool response as JSON.

Cowork mode: always use this connector flow. Before doing any work in Cowork mode, check whether the Vibe Prospecting MCP connector tools are available in your tool list (look for a tool matching the pattern mcp__*__fetch-entities).

If those tools are present, use the connector directly and follow its tool descriptions and schemas. If those tools are NOT present:

1. Call mcp__mcp-registry__search_mcp_registry with keywords ["vibe prospecting", "explorium"]
2. Call mcp__mcp-registry__suggest_connectors with the UUID 1bdcb159-b6f0-4f13-bc08-fdb40b007828 and keywords ["prospecting"]
3. Tell the user to click Connect on the card — the tools unlock automatically once authorized
4. Poll until connected. On every subsequent turn, re-check your tool list for mcp__*__fetch-entities. Do not start prospecting work until those tools appear. Never fall back to the CLI, the npm vpai tool, an OAuth URL, or this plugin's bundled MCP connector in Cowork mode — the Cowork connector store is the only path. If the user cannot connect from the suggested card, tell them to open the connector store and install Vibe Prospecting from there, then poll again. If tools are still missing, remind the user to connect and wait; repeat until the connector is available.

If the CLI install fails outside Cowork mode (e.g. npx unavailable, sandboxed environment, permission denied), use the bundled Vibe Prospecting MCP connector instead and follow its own tool descriptions and schemas. The rest of this file is CLI-only. In Cowork mode, never use that fallback — use the connector store flow above.

Hard Rules