Leadfeeder

Leadfeeder MCP integration

Resolves visitor IPs to company profiles, pulls a lead's full visit history, and lists the custom feeds a team segments traffic by.

6actions available

What your agent can do with Leadfeeder

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Get account

    Lyro retrieves the details of a specific account in Leadfeeder. Support agents can check account settings and configurations without leaving the chat.

  • Get company info by IP

    Lyro looks up company information based on an IP address in Leadfeeder. Support agents identify organizations behind website visits without manual research.

See all 6 actions

How businesses use Leadfeeder + Lyro

Each card is one request a support team gets, and the Leadfeeder actions Lyro runs to close it.

  • Name the company behind an anonymous visitor

    Lyro enriches an IP address into a company profile and ties it to the Leadfeeder account tracking that site, so a sales question about an unidentified visitor gets an answer instead of a shrug.

    Get Company Info by IPGet AccountGet Accounts
  • Read a lead's visit history before the call

    Lyro pulls every recorded visit for a lead, filtered to the date range that matters, so a rep walks in knowing which pages the account kept returning to.

    Get All VisitsGet AccountGet Company Info by IP
  • Check which segments a team already filters by

    Lyro lists the custom feeds saved on an account - the filter configurations that segment company visits - so a new campaign reuses an existing segment rather than duplicating it.

    Get Custom FeedsGet AccountsGet Account
  • Hand over the tracking script for a new site

    When someone asks how to start tracking a domain, Lyro returns the JavaScript tracking code for the right account so it can be pasted straight into the page.

    Get Tracking ScriptGet AccountsGet Account

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Leadfeeder actions it has and picks the ones a request needs.

  1. 01

    Connect Leadfeeder

    Authorize the Leadfeeder account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Leadfeeder actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Leadfeeder · Lyro

Everything else about Leadfeeder

Setup, permissions, and the limits of what Lyro can do inside Leadfeeder.

  • No. All six actions here read - accounts, visits, company lookup by IP, custom feeds, and the tracking script. Lyro can surface and summarise what Leadfeeder knows, but assigning, tagging, and CRM sync stay in Leadfeeder's own integrations.

Every action available in Leadfeeder

All 6 actions your agent can call on Leadfeeder, straight from the live MCP connection.

  • Get account

    Retrieve the details of a specific account by ID.

  • Get accounts

    Retrieve a list of accounts the user has access to.

  • Get all visits

    Retrieve all visits for a specific lead.

  • Get company info by IP

    Retrieve company information based on an IP address.

  • Get custom feeds

    Retrieve all custom feeds configured for a Leadfeeder account.

  • Get tracking script

    Retrieve the website tracking script for a given account.

Ready to connect Leadfeeder?

Authorize the account and your agent has all 6 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot