generate_email
Generate email by first/last name and domain via Generect Email Generator
Search B2B leads and companies by ICP filters, enrich a LinkedIn URL, and generate a work email.
LABSCO SUMMARY
Lead data is personal data, and a debug log is where it quietly leaks. Request and response payloads are reduced to non-identifying shape markers by default — you can see that a first name was sent without recording the name — and verbatim logging is an explicit opt-in for a short debugging session.
A minimal MCP server over the Generect Live API for lead generation. Five tools: search leads and companies by ICP filters, pull one lead from a LinkedIn profile URL, generate an email address from a name and a domain, and a health check.
The hosted server at https://mcp.generect.com/mcp speaks Streamable HTTP with OAuth 2.1, including dynamic client registration — connect, then paste your Generect API token on the authorization page. Clients that cannot complete OAuth may send the key in an Authorization header instead, including through mcp-remote. For local use: Node 18 or newer with GENERECT_API_BASE, GENERECT_API_KEY, GENERECT_TIMEOUT_MS, JWT_SIGNING_KEY and TOKEN_ENCRYPTION_KEY set. Keys come from beta.generect.com.
One command plus a key — npm i -g generect-ultimate-mcp, then supply credentials
USE CASES
Filter leads by title, industry and location, or start from the company side and work down.
One profile URL in, the full lead record out, optionally with recent posts and comments.
Generate the likely address rather than guessing at a pattern.
A quick request that fails fast, so a batch does not start against a dead endpoint.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
generate_emailGenerate email by first/last name and domain via Generect Email Generator
get_lead_by_urlGet Lead by LinkedIn URL
healthHealth check Generect API via a quick lead-by-link request
search_companiesSearch for companies by ICP filters
search_leadsSearch for leads by ICP filters
BEFORE YOU INSTALL
5 tools when we connected.
GENERECT_API_KEY in your environment
Of the 4 documented setups, 2 run the server on your machine and 2 connect to a hosted endpoint.
CONTEXT COST
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npm i -g generect-ultimate-mcphttps://mcp.generect.com/mcpAdd this hosted endpoint to your MCP client, then sign in.
{
"mcpServers": {
"generect-api": {
"command": "npx",
"args": [
"-y",
"generect-ultimate-mcp@latest"
],
"env": {
"GENERECT_API_BASE": "https://api.generect.com",
"GENERECT_API_KEY": "Token <YOUR_API_KEY>",
"GENERECT_TIMEOUT_MS": "300000",
"MCP_DEBUG": "0"
}
}
}
}This block runs the server from a checkout of the repository: git clone https://github.com/generect/generect_mcp.git, then cd generect_mcp and npm install; the paths in it are relative to that folder
Add it to Cursor's MCP settings with your Generect API key after Token (keys come from https://beta.generect.com):
{
"mcpServers": {
"generect-liveapi": {
"command": "node",
"args": [
"./node_modules/tsx/dist/cli.mjs",
"src/server.ts"
],
"env": {
"GENERECT_API_BASE": "https://api.generect.com",
"GENERECT_API_KEY": "Token <YOUR_API_KEY>",
"GENERECT_TIMEOUT_MS": "300000"
}
}
}
}{
"mcpServers": {
"generect": {
"url": "https://mcp.generect.com/mcp",
"type": "http"
}
}
}{
"mcpServers": {
"generect": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.generect.com/mcp",
"--header",
"Authorization: Bearer <YOUR_API_KEY>"
]
}
}
}