Minimal MCP server exposing Generect Live API tools.
Minimal MCP server exposing Generect Live API tools. Exposed over MCP by the generect mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Minimal MCP server exposing Generect Live API tools for B2B lead generation and company search.
Everything the assistant can do here goes through one of these:
search_leads — Search for leads by ICP filters (supports timeout_ms)search_companies — Search for companies by ICP filters (supports timeout_ms)generate_email — Generate email by first/last name and domain (supports timeout_ms)get_lead_by_url — Get LinkedIn lead by profile URL (supports timeout_ms)health — Quick health check against the API (optional url, supports timeout_ms)Logging — The server emits one structured JSON log line per event to stderr (stdout is reserved for the MCP stdio protocol). Metadata logging is **on byTools — The Tools tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: GENERECT_API_BASE, GENERECT_API_KEY, GENERECT_TIMEOUT_MS, MCP_DEBUG, YOUR_API_KEY, JWT_SIGNING_KEY, TOKEN_ENCRYPTION_KEY, OAUTH_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Generect MCP's toolset — search_leads, search_companies, generate_email and 4 more — is a fair guide to whether it matches your workflow. It is maintained by generect; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Generect MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search_leads | Search for leads by ICP filters (supports timeout_ms) |
| search_companies | Search for companies by ICP filters (supports timeout_ms) |
| generate_email | Generate email by first/last name and domain (supports timeout_ms) |
| get_lead_by_url | Get LinkedIn lead by profile URL (supports timeout_ms) |
| health | Quick health check against the API (optional url, supports timeout_ms) |
| Logging | The server emits one structured JSON log line per event to **stderr** (stdout is reserved for the MCP stdio protocol). Metadata logging is **on by default**; set MCP_LOG=0 to disable it entirely. |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"generect": {
"url": "https://mcp.generect.com/mcp",
"type": "http"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GENERECT_API_BASE | Configuration value read at startup. | Optional |
| GENERECT_API_KEY | Credential the server authenticates with. | Yes |
| GENERECT_TIMEOUT_MS | Configuration value read at startup. | Optional |
| MCP_DEBUG | Configuration value read at startup. | Optional |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| JWT_SIGNING_KEY | Credential the server authenticates with. | Yes |
| TOKEN_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
| OAUTH_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.