MCP setup
The repository includes a stdio MCP server for compatible local assistant clients. The hosted /api/mcp URL is an informational manifest, not a remote MCP transport.
Use the repository server
Clone the Pindrop repository and configure your assistant to launch Node with the absolute path to packages/pindrop-mcp/bin/index.mjs. Set GOOGLE_PLACES_API_KEY in your local assistant environment for discovery. Keep provider keys out of shared configuration files.
{
"mcpServers": {
"pindrop": {
"command": "node",
"args": ["/absolute/path/to/pindrop/packages/pindrop-mcp/bin/index.mjs"]
}
}
}Use the reviewed repository copy for this release. Changes here do not update an npm-published package.
Implemented tools
pindrop_discover: sends a query to the Google Places route using your Google Places key. Available fields depend on the provider response.pindrop_audit: fetches website HTML, reports HTTP response time, and checks for CMS markers. It does not measure browser rendering, LCP, mobile performance, or revenue loss.pindrop_pitch: creates a generic outreach template for manual review. It does not run an AI model or verify prospect findings.