Leadfeeder

@leadfeeder show me all custom feeds for our main account so I can see which visitor segments we're tracking

Based on the Leadfeeder account data, you have 5 custom feeds configured: 'High-Intent Enterprise Visitors' (filtering for 5+ page views from companies with 500+ employees), 'Competitor Intelligence' (tracking visits from known competitor domains), 'Product Page Engagement' (visitors who spent 2+ minutes on /product pages), 'Returning Visitors - Last 7 Days', and 'EMEA Region Focus' (filtering by geographic location). Each feed includes its filter criteria, creation date, and current lead count. This illustrative example shows typical feed configurations teams use to segment anonymous website traffic.

This example demonstrates Leadfeeder's feed management capability, which is central to organizing visitor intelligence. Requires valid account_id from the Get Accounts tool first. Custom feeds are user-defined, so actual feed names and filters will vary significantly by organization. No write operations occur here—purely informational.

@leadfeeder look up the company behind IP address 203.0.113.45 that just hit our pricing page

The IP address 203.0.113.45 resolves to Acme Manufacturing Ltd, a mid-sized industrial equipment manufacturer based in Manchester, UK. Company details include 250-500 employees, estimated annual revenue of $50-100M, primary industry classification as Industrial Machinery, and website acme-manufacturing.co.uk. This illustrative lookup shows how Leadfeeder enriches anonymous IP traffic into actionable company profiles. Note that not all IPs resolve to companies—residential ISPs, VPNs, and small businesses often return 404.

This showcases Leadfeeder's core IP-to-company enrichment, useful for real-time visitor identification. Returns 404 if no company match exists (common for consumer ISPs, privacy tools, or small businesses without sufficient data). The enrichment quality depends on Leadfeeder's proprietary database coverage, which is strongest for B2B companies in North America and Europe.

@leadfeeder pull the full visit history for lead ID 789456 from the last 30 days and summarize their engagement pattern

Lead 789456 (TechCorp Solutions) made 8 visits over the past 30 days, showing escalating intent. Early visits (days 1-10) focused on blog content and general product pages with 2-3 minute sessions. Mid-period visits (days 12-18) shifted to pricing and case study pages with 5-8 minute sessions. Most recent visits (days 24-28) included multiple team members accessing technical documentation, integration guides, and the contact page—3 distinct IP addresses from the same company block. This illustrative pattern suggests a buying committee forming consensus. Total page views: 47 across all visits.

This example pairs Leadfeeder's visit retrieval with AI synthesis to extract buying signals from raw visit data. Requires a valid lead_id, which you'd typically obtain from a custom feed or previous query. Date range filtering is optional but recommended for performance. The AI's pattern analysis adds interpretive value beyond what the raw API returns—useful for sales teams prioritizing outreach.

When Leadfeeder MCP makes sense for outbound prospecting

A 6-person sales team runs outbound campaigns and wants to enrich inbound web traffic in real time during prospect calls. The Leadfeeder MCP is the right call if your team already uses Leadfeeder for visitor tracking and needs to pull company data into Switchy chats without tab-switching. The Get Company Info by IP tool lets you paste an IP from your logs and get firmographic data instantly. The Get All Visits tool surfaces visit history so you can reference which pages a prospect browsed before the call. This works best when your team handles 20-50 inbound leads per week and needs context fast. If you're doing high-volume cold outreach with no inbound signal, a CRM enrichment MCP is a better fit. For teams that live in Leadfeeder daily, this MCP cuts 3-4 context switches per call.

Using Leadfeeder MCP for campaign post-mortem analysis

A 3-person growth team wraps a paid campaign and needs to trace which companies visited the landing page, when, and how often. The Leadfeeder MCP shines here because the Get All Visits tool pulls timestamped visit logs for each lead, and the Get Custom Feeds tool surfaces segmented lists you've already configured in Leadfeeder (like 'Enterprise visitors' or 'Repeat traffic'). You can ask Switchy to compare visit patterns across two campaigns or identify drop-off points without exporting CSVs. This scenario assumes you're analyzing 50-200 leads per campaign and want narrative summaries, not pivot tables. If you need to join visit data with ad spend or conversion events, you'll still need a BI tool. For qualitative campaign retrospectives where you're asking 'who showed up and what did they care about', this MCP delivers the context in seconds.

When Leadfeeder MCP helps CS teams spot churn signals

A 4-person customer success team monitors product usage but also wants to track whether key accounts are still visiting the docs site or pricing page. The Leadfeeder MCP is useful if you're already tracking customer domains in Leadfeeder and need to surface visit activity during quarterly business reviews. The Get All Visits tool shows whether a customer's team has been researching competitors or revisiting onboarding content, which can flag expansion or churn risk. The Get Accounts tool helps you confirm which Leadfeeder workspace holds your customer data if you run multiple accounts. This works when you manage 20-80 accounts and want qualitative engagement signals, not quantitative product analytics. If your churn model relies on in-app events or support ticket volume, a product analytics MCP is more direct. For CS teams that treat web engagement as a leading indicator, this MCP surfaces the signal without a separate dashboard.