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.


MCP Registry not found or connection failed

Cause: The client doesn’t support MCP Registry, or the registry identifier is incorrect. Solution:
  • Ensure you’re using a client that supports MCP Registry (e.g., latest Claude Desktop versions).
  • Verify the registry identifier: com.generect/generect-mcp
  • If your client doesn’t support registry, use the Local MCP (npx) method instead.

401 Unauthorized error

Cause: Your API key is invalid or missing. Solution:
  • Make sure you replaced your-api-key with your actual key.
  • For Local MCP, set the env var to either GENERECT_API_KEY="your-real-key" or GENERECT_API_KEY="Token your-real-key" — both are accepted.
  • For Remote MCP with a custom Authorization header, any of these forms work: YOUR_API_KEY, Bearer YOUR_API_KEY, Token YOUR_API_KEY, or Bearer Token YOUR_API_KEY.
  • Verify the key is active in beta.generect.com.

Timeout error

Cause: The API request took longer than the default timeout (1 minute). For example, a lead search may take longer with very broad filters. Solution:
  • If you are using local MCP: increase the timeout limit in your MCP configuration (default: 60000 ms).
"GENERECT_TIMEOUT_MS": "180000"
  • Try refining your query (e.g., add more filters for leads or companies).

MCP server does not appear in the client

Cause: Configuration file is invalid, or the MCP server didn’t start. Solution:
  • Double-check JSON syntax and content in your config (claude_desktop_config.json, Cursor config). NPM should be generect-ultimate-mcp
  • Try setting MCP_DEBUG=1 to see logs when starting the MCP.
  • Restart your client after editing the configuration.

LLM doesn’t call MCP tools

Cause: The LLM decides when to call external tools — it may not always trigger them. Solution:
  • Rephrase your request in a way that makes tool usage more likely (e.g., explicitly ask to “search leads”).
  • Check that the MCP server is shown as active in the client’s settings.