đ§ȘBeta. The Leadfeeder MCP Server is in beta. Setup steps and the available tools may change.
The Leadfeeder MCP Server uses your own Leadfeeder account to connect your AI tool to Leadfeeder. Access follows the same permissions and credit rules as your Leadfeeder account and the Leadfeeder API.
How authentication works
When you connect an AI tool to Leadfeeder, you sign in through a secure OAuth flow and approve access. Your AI tool does not see your password, and you do not need to paste an API key into the tool.
This is different from the Leadfeeder REST API, which uses API keys. The MCP Server handles sign-in for you.
Required permission
To connect, your user must have the following access right:
Integrations â Manage API keys and use API
This is the same access right that controls API key generation and API use for the REST API. Without this permission, sign-in will not complete and your AI tool will not be able to call Leadfeeder tools.
If the connection does not complete, ask your Leadfeeder admin to check that this permission is enabled for your user.
What access you grant
When you approve access, the AI tool can call Leadfeeder tools on your behalf. It can only do what your Leadfeeder user and account are already allowed to do.
This can include:
Reading Leadfeeder data.
Searching companies or contacts.
Enriching company or contact records.
Creating or updating lists, tags, or custom fields, depending on available tools and your access.
Actions that change data ask you to confirm before they run.
How credits work
The MCP Server uses the same credit balance as the Leadfeeder API. Credit-consuming tools draw from that shared balance.
Not all actions use credits.
Usually no credits
Simple read, search, matching, list, tag, custom field, account, and usage actions are listed as no-credit tools in the MCP Server requirements. Examples include:
Listing accounts.
Getting account-level credit information.
Searching companies.
Matching companies.
Searching contacts.
Listing, creating, updating, or deleting lists, tags and custom fields.
Viewing API usage.
May consume credits
Enrichment-style tools may consume credits. Examples include:
Getting full company details.
Bulk-enriching companies.
Getting company financials.
Searching company signals.
Getting full contact details.
Bulk-enriching contacts.
The MCP Server requirements also state that credit-consuming tools should return metadata showing how many credits were used.
Disconnecting
You can disconnect the MCP Server from your AI toolâs connector settings. You can also revoke access in your Leadfeeder account settings.
Good to know
The AI tool connects to Leadfeeder from the AI providerâs cloud, not from your own computer.
You approve access when connecting and can disconnect later.
The MCP Server sits on top of the Leadfeeder API, so data, permissions, and credit rules are governed by the same account-level rules.