Skip to directory

Generect MCP

Generect

Streamable HTTP (hosted); stdio or HTTP locally21 documented tools5

About Generect MCP

Generect MCP gives AI clients access to B2B lead and company search; audience sizing and search are free, while retained contact details and full profiles are paid.

What you can use it for

  • Search leads by ICP filters
  • Search companies
  • Generate personalized email using name and domain
  • Retrieve lead by LinkedIn profile URL
  • Check API health
Connection and setup
Hosting
Remote hosted; local Node.js alternative documented
Transport
Streamable HTTP (hosted); stdio or HTTP locally
Endpoint
https://mcp.generect.com/mcp
Authentication
Hosted OAuth 2.1 with PKCE and dynamic client registration; direct API-key Authorization header is also documented. Local mode requires GENERECT_API_KEY and GENERECT_API_BASE.

Requirements

  • Generect account/API key from https://beta.generect.com
  • OAuth-capable MCP client, or local Node.js 18+ environment
  • API access subject to account entitlements

Setup steps

  1. Add https://mcp.generect.com/mcp as a remote HTTP MCP server in an OAuth-capable client.
  2. Complete Generect OAuth in the browser; the repository says the authorization flow accepts the account API token.
  3. If OAuth is unsupported, use a client-supported Authorization header with an API key stored locally; mcp-remote is one documented option.
  4. For self-hosting, use Node.js 18+ and set GENERECT_API_BASE and GENERECT_API_KEY. Production deployment also requires strong signing/encryption secrets.
  5. Verify using the health tool or a harmless search allowed by the account.
Tools 21

Current official README documents 21 tools. Pricing is account-dependent: counts/health/balance and some thin database searches can be free; several profile, preview, email, phone and bulk operations are billable. A per-call spend ceiling (default $5) requires explicit confirm_spend_usd when exceeded.

  • count_leads

    Count people matching ICP filters and report the next-step cost.

    01
  • count_companies

    Count companies matching ICP filters and report the next-step cost.

    02
  • search_leads

    Search people matching ICP filters; thin database rows can be free within quota, while full/realtime results may be billed.

    03
  • preview_leads

    Preview matching leads or count only; preview rows are billable unless count_only is true.

    04
  • search_companies

    Search companies matching ICP filters; thin database rows can be free within quota, while full/realtime results may be billed.

    05
  • enrich_lead

    Retrieve a full lead profile; billed per record found.

    06
  • get_lead_by_url

    Retrieve a lead profile by profile URL; billed per record found.

    07
  • enrich_company

    Retrieve a full company profile; billed per record found.

    08
  • get_balance

    Return account balance, operation prices, and optional spend breakdown.

    09
  • generate_email

    Find and return valid email addresses for selected leads; billed per valid address found.

    10
  • get_bulk_job

    Poll the status and results of a bulk job; bulk work is billed at submission.

    11
  • list_webhooks

    List webhook endpoints for bulk-job completion events.

    12
  • create_webhook

    Create a webhook endpoint for bulk-job completion events.

    13
  • update_webhook

    Update a webhook endpoint for bulk-job completion events.

    14
  • delete_webhook

    Delete a webhook endpoint.

    15
  • test_webhook

    Send a test event to a webhook endpoint.

    16
  • health

    Check service liveness and credentials through a free health endpoint.

    17
  • resolve_profile

    Resolve a professional profile; billed per resolved profile.

    18
  • validate_email

    Validate an email address; billed per submitted address.

    19
  • find_phone

    Find a phone number for a lead; billed per number found.

    20
  • start_bulk_job

    Submit a bulk job; per-record cost is reserved on submission.

    21
Limitations and notes
  • Access depends on account/API entitlements.
  • Keep API keys and OAuth tokens in local secret storage, never chat.
  • Repository documents payload redaction by default and production signing/encryption requirements.
  • Local setup/deployment is for developers; hosted OAuth is the normal user path.
Original sources
  • official repository setup tools

    Current maintainer README lists 21 tools, classifies free vs billable operations, explains thin/full/realtime search modes, per-account pricing, resources and spend ceiling.

  • official product page

    Official product page documents MCP onboarding, account API-key access, and B2B lead-data use cases.

  • official documentation repository

    Official organization documents this repository as the API documentation source.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.

Similar tools