Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.generect.com/llms.txt

Use this file to discover all available pages before exploring further.

Remote MCP servers extend AI capabilities beyond your local environment, providing access to internet-hosted tools and data sources. By connecting to Generect’s remote MCP server, you can access lead search, company search, and email generation directly in your AI conversations without any local installation.
Remote MCP works with Claude (web and Desktop) and other MCP-compatible clients. For local installation via npx, see Local MCP (npx).

​
Server Information

PropertyValue
Registry IDcom.generect/generect-mcp
Remote URLhttps://mcp.generect.com/mcp
TransportStreamable HTTP
AuthOAuth 2.1 or API Key

​
Claude Desktop — Custom Connectors

Claude documentation states: Custom connectors are available for users with paid plans (Pro, Max, Team, or Enterprise).This may change in the future, but for now this restriction applies.
1

Navigate to Connector Settings

Open Claude Desktop. Click on your profile icon and select Settings from the dropdown menu. Then click on Connectors in the sidebar.
2

Add a Custom Connector

Scroll to the bottom and click Add custom connector.Enter the Generect MCP server URL:
https://mcp.generect.com/mcp
Leave Advanced settings empty.enter-urlClick Add to proceed.
3

Complete Authentication

Then click on “Connect”. You will be redirected to login page.click-connectGet your API key from beta.generect.com and enter it on the login page.click-connect
4

Connector is ready

Now you can use Generect MCP server. Make sure that you have enabled it in Connectors tab.response-example

​
Other Clients (Cursor, OpenAI, etc.)

Integration with other MCP-compatible clients follows the same pattern:
  1. Find the MCP/Connector settings in your client
  2. Add a remote MCP server with URL: https://mcp.generect.com/mcp
  3. Configure authentication with your API key (see formats below)
Each client has its own configuration method — look for “MCP”, “Connectors”, or “Tools” in settings. Some clients may require editing a config file, others provide a UI.

​
Supported Authorization header formats

If your client passes the API key directly via an Authorization header (no OAuth flow), the server accepts any of: 
Authorization: YOUR_API_KEY
Authorization: Bearer YOUR_API_KEY
Authorization: Token YOUR_API_KEY
Authorization: Bearer Token YOUR_API_KEY   (legacy, still supported)
Pick whichever format your client makes easiest. Example for mcp-remote: 
{
  "mcpServers": {
    "generect": {
      "command": "mcp-remote",
      "args": [
        "https://mcp.generect.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

​
Remote MCP vs Local MCP

FeatureRemote MCPLocal MCP (npx)
InstallationNone requiredRequires Node.js & npx
ConfigurationURL or registry IDCommand + args in config
AccessAny MCP-compatible clientRequires local setup
Offline accessNot availableAvailable (with cached data)
UpdatesAutomaticManual (@latest)
Choose Remote MCP for simplicity and accessibility. Choose Local MCP if you need offline capabilities or have network restrictions.

​
Available Tools

The MCP integration provides access to the following Generect API functions:
  • search_leads: Search for leads by ICP filters
  • search_companies: Search for companies by ICP filters
  • generate_email: Generate an email using first/last name and domain
  • get_lead_by_url: Get LinkedIn lead by profile URL
  • health: Quick health check against the API

​
MCP Registry

Generect MCP is registered in the official MCP Registry: 
com.generect/generect-mcp