Leadfeeder MCP Server: now available in Google Gemini

The Leadfeeder MCP Server now supports Google Gemini Enterprise. You can connect it as a custom MCP server and work with your Leadfeeder data from Gemini in plain language.
What’s new
Google Gemini is now a supported client for the Leadfeeder MCP Server (https://mcp.leadfeeder.com/mcp), alongside Claude, Claude Code, ChatGPT, Microsoft 365 Copilot, Perplexity, Codex and Cursor.
Gemini connects through OAuth 2.0 with an OAuth application you create in Leadfeeder under Companies → Applications. You need the OAuth Applications right under Company Access Rights.
The scopes you select for the application control what Gemini can access. Use the same scopes in the Gemini MCP configuration.
Get started: follow the step-by-step guide in Connect your AI tool.

October 27, 2026

new

Leadfeeder API - Deprecation notice for next_reset_on attribute on Accounts endpoint

We are improving the /accounts endpoint in the Leadfeeder API so you get a clearer view of your credits. As part of this, the next_reset_on
 field is being deprecated on November 17, 2026.
What’s new
The /accounts response now shows your credits in two separate pools.
recurring: the credits included in your subscription
one_off: any extra credits you purchased on top
Each pool has its own renews_at
 date. You can see exactly when each type of credit refreshes, instead of relying on a single date for everything.
What’s changing
Until November 17, 2026: nothing changes. next_reset_on keeps working as it does today. The new renews_at
 dates are already available in each credit pool.
From November 17, 2026: next_reset_on
 stays in the response, but it is marked as deprecated and no longer returns a value. It will be removed fully at a later date.
What you need to do
If your integration reads next_reset_on
, switch to renews_at
 from the relevant credit pool before November 17. Otherwise, your integration will receive an empty value from that date. recurring.renews_at holds the same value next_reset_on returns today.
If your integration does not use next_reset_on, there is nothing you need to do.
For questions, reach out to our support team at support@leadfeeder.com

October 19, 2026

new

Leadfeeder API 2026-10-19

🆕
[New]:
Added a Goals endpoints for creating, retrieving, updating, and deleting web visit goals. It covers
GET
,
POST
and
DELETE
on
/v1/web-visits/goals
, and
GET
and
PATCH
on
/v1/web-visits/goals/{id}
.
🆕
[New]
The
locations
filter in
[POST /v1/companies/search](https://docs.leadfeeder.com/api/public/search-companies-4008955e0)
now accepts additional input formats, giving more flexibility in how location criteria are specified.
⚡
[Improved]
Added an optional
label
field to the geo filter in advanced search criteria on the batch job endpoints (
POST /v1/companies/enrichment-jobs
,
POST /v1/lists/batch-add-to-list-jobs
,
POST /v1/lists/batch-remove-from-list-jobs
,
POST /v1/tags/batch-add-tags-jobs
,
POST /v1/tags/batch-remove-tags-jobs
). The field is also returned in the job creation and status responses.
🆕
[New][MCP]
Added the web visit goal tools
create_web_visits_goal
,
get_web_visits_goal
,
get_web_visits_goals
,
update_web_visits_goal
, and
delete_web_visits_goal
, so AI assistants can create, list, retrieve, update, and remove goals on your behalf.
⚡
[Improved][MCP]
The
get_web_visits_custom_feeds
tool accepts a new
filter_has_connected_list
parameter to return only feeds that have a connected list.
⚡
[Improved][MCP]
The
get_web_visits_custom_feeds
and
get_web_visits_custom_feed
tools accept
"connected_list"
as a value for
include
, so connected list data comes back with the feed.- ⚡ - -⚡
[Improved][MCP]
The
create_batch_add_tags_job
,
create_batch_add_to_list_job
,
create_batch_remove_from_list_job
,
create_batch_remove_tags_job
, and
create_company_enrichment_job
tools accept an optional
label
field on geo filters in advanced search, to attach a readable place name to the center point.

September 23, 2026

new

improved

Leadfeeder API - 2026-09-23

🆕
[New]
The GET /v1/companies/ips response now includes a meta object on each IP entry, providing additional metadata alongside the existing IP data.
🆕
[New]
ICP objects returned by the ICP endpoints (GET /v1/icps, POST /v1/icps, GET /v1/icps/{id}, PATCH /v1/icps/{id}) now include a
relationships
field in the response.
🆕
[New]
Custom feeds now expose a
connected_list
relationship in responses from GET /v1/web-visits/custom-feeds, POST /v1/web-visits/custom-feeds, GET /v1/web-visits/custom-feeds/{custom_feed_id}, and PATCH /v1/web-visits/custom-feeds/{custom_feed_id}.
🆕
[New]
Added
connected_list
as a supported value for the include query parameter on GET /v1/web-visits/custom-feeds and GET /v1/web-visits/custom-feeds/{custom_feed_id}, allowing you to sideload connected list data in a single request.
🆕
[New]
Added a filter[has_connected_list] query parameter to GET /v1/web-visits/custom-feeds, enabling you to filter custom feeds by whether they have a connected list.
🆕
[New]
Campaign responses from GET /v1/campaigns, GET /v1/campaigns/{id}, and PATCH /v1/campaigns/{id} now include a connected_list relationship on the associated custom feed when one is present.
⚡
[Improved]
The
job_ads
category is available again in the signals endpoint. It now runs on our new signals system, and you don't need to change anything: requests that filter on job_ads work as they did before the pause.
⚡
[Improved]
The max_ip_addresses parameter on GET /v1/companies/ips is now capped at a maximum value of 500.

September 16, 2026

new

improved

Leadfeeder API - 2026-09-16

🆕
[New]
Added the GET /v1/industries endpoint for retrieving industry reference data.
🆕
[New]
Added GET /v1/settings/cookie-consent endpoint to retrieve your account's cookie consent settings.
🆕
[New]
Added PATCH /v1/settings/cookie-consent endpoint to update your account's cookie consent settings.
🆕
[New]
Added GET /v1/settings/data-processing endpoint to retrieve your data processing settings.
🆕
[New]
Added PATCH /v1/settings/data-processing endpoint to update your data processing settings.
⚡
[Improved]
The GET /v1/web-visits/tracker response now includes four new fields:
data_processed
,
last_event_received_at
,
status
, and
visiting_companies
.
🆕
[New] [MCP]
The
get_industries
tool is now available, letting AI assistants retrieve the list of supported industries.
🆕
[New] [MCP]
The
get_cookie_consent_settings
,
get_data_processing_settings
,
update_cookie_consent_settings
and
update_data_processing_settings
tools are now available, allowing AI assistants to retrieve and manage those account settings.

August 28, 2026

new

Leadfeeder API - 2026-08-28

🆕
[New]
Added POST /v1/icps and POST /v1/buyer-personas to create ICPs and buyer personas; PATCH and DELETE to update and delete them.
🆕
[New]
Added GET /v1/countries and GET /v1/geo-suggestions for reference data and location suggestions.
🆕
[New]
Added POST /v1/icps/companies to retrieve companies matching your ICP, and POST /v1/lists/companies and POST /v1/lists/contacts to browse your saved lists.
🆕
[New]
Added bulk tagging: POST /v1/tags/batch-add-tags-jobs and POST /v1/tags/batch-remove-tags-jobs, with GET .../{job_id} to check job status.

All above operations are supported on the MCP Server - Tools

August 24, 2026

new

Leadfeeder API - 2026-08-24

🆕 [New]

Added

OAuth 2.0 authentication

alongside API keys. Register an OAuth application in Settings > Company > Developer Access > Applications, and each user authorises it with their own Leadfeeder account. Find more details here

August 18, 2026

new

improved

Leadfeeder API - 2026-08-18

🆕
[New]
Added an app_url field to company schema - CompanyV1. This is an example of the returned value
https://app.leadfeeder.com/h/company/129011
.
⚡
[Improved]
The
unknown_department
value has been removed from the departments filter parameter and from departments response fields across the contacts search, contacts list, single contact, and list batch-add/remove-job endpoints — sending or expecting this value will no longer be accepted or returned.
⚡
[Improved]
The
unknown_hierarchy
value has been removed from the
hierarchy_levels
filter parameter and from the hierarchy_level response field across the contacts search , contacts list , single contac, and list batch-add/remove-job endpoints — sending or expecting this value will no longer be accepted or returned.
⚡
[Improved] [MCP]
The
unknown_department
value has been removed from the departments filter enum in
search_contacts
,
create_batch_add_to_list_job
, and
create_batch_remove_from_list_job
; any saved prompt or automation passing that value will now be rejected.
⚡
[Improved] [MCP]
The
unknown_hierarchy
value has been removed from the hierarchy levels filter enum in
search_contacts
,
create_batch_add_to_list_job
, and
create_batch_remove_from_list_job
; any saved prompt or automation passing that value will now be rejected.

August 11, 2026

improved

new

Leadfeeder API - 2026-08-11

🆕
[New]
Added an optional
advanced_search
parameter to POST /v1/lists/batch-add-to-list-jobs and POST /v1/lists/batch-remove-from-list-jobs letting you target records via a search query instead of providing explicit item IDs. The maximum number of companies is set to 100,000.
🆕
[New]
The POST /v1/web-visits response now guarantees
id
and
time
fields on all engagement types (page-view, form-submit, file-download, and video-view).
⚡
[Improved]
The POST /v1/companies/match and POST /v1/companies/search response now includes
address
,
employee_range
,
industries
,
revenue
,
logo_url
and
url
fields in the
company_summary
relationship.
⚡
[Improved]
The GET /v1/accounts gained an optional
include
query param and a relationships object on each account that returns the assigned company.
⚡
[Improved]
The POST /v1/lists/batch-add-to-list-jobs and POST /v1/lists/batch-remove-from-list-jobs responses configuration.items field in responses is now optional and will be absent when the job was created using
advanced_search
.
⚡
[Improved]
The GET /v1/ip/enrich response schema for
data/relationships
now includes an additional
oneOf
variant

July 24, 2026

improved

Leadfeeder API - Company Signals API - 2026-07-24

As announced in our previous update, the changes to the POST /companies/signals endpoint went live today, July 24, 2026.

What changed:

job_ads
category has temporarily stopped returning signals while we migrate it to our new signals system. No action needed — expect it back in early September.
Three categories have been permanently removed and no longer return data: financial_struggles, corporate_challenges, register_updates. If your integration still filters on these, remove them now to avoid unexpected behaviour.
Two categories have been renamed:

partnerships_and_collaborations
→
partnerships_collaborations
regulatory_compliance_updates
→
regulatory_and_compliance_updates

Update any references in your integration to the new names.

→