Integration

Enrow integration

Enrow finds professional email addresses and verifies them, including catch-all addresses. An agent can search one person's work email from a full name plus a company domain or name, or from a LinkedIn profile URL, wait for the result (the email, valid or invalid qualification, credits used, name and company details), read a search result by its id, and check the account's credit balance and registered webhooks. The bulk email finder, the email verifier and the phone finder routes are not exposed. Authentication is an API key, copied from the API page of the Enrow app, sent in the x-api-key header.

Connect Enrow How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Enrow.Built from the 3 Enrow tools below, on the connection you add once.

What you can do with Enrow

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Email, 2 operations

find_emailFind emailPOSTFinds a person's work email: pass fullname plus company_domain or company_name, or only linkedin_url. Read qualification: valid (found, 1 credit) or invalid. Waits for the job and returns the finished result; gives up after 5 minutes.
get_email_searchGet email searchGETReads the result of a single email search by its id (for example one launched with a webhook): qualification valid, invalid, or ongoing while still running, the email, credits used and name and company details. Free.

Account, 1 operation

get_accountGet accountGETReturns the Enrow account's current credit balance and its registered webhook URLs (webhooks may be absent when none is configured).

Use Enrow from Claude Code, Cursor or Codex

Connect Enrow in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Enrow operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Enrow

Create your workspace
Sign up free. Nothing to install.
Connect Enrow once
Add your Enrow connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.