MCP Troubleshooting

Fixes for the most common problems when connecting or using an MCP client with Funnelfeedr

This page collects the problems people run into with the Funnelfeedr MCP server, grouped by when they happen.

While connecting

The client cannot find or reach the server

Check the address is exactly https://mcp.funnelfeedr.com/mcp. No extra path, https not http.
Make sure the client supports remote MCP servers over Streamable HTTP with OAuth. Clients that only support local servers or static API keys cannot connect.
If you are on a corporate network, ask IT whether mcp.funnelfeedr.com, app.funnelfeedr.com and api.funnelfeedr.com are reachable. The OAuth flow needs all of them.

The browser opens but shows an error instead of the approval screen

Message	Cause	Fix
This connection request has expired or has already been used.	More than 10 minutes passed, or the page was reloaded after approving.	Start the connection again from the client.
We could not find this connection request.	The link was truncated or edited.	Start again from the client and let it open the browser itself.
The link is missing its request reference.	The approval page was opened directly rather than through the client.	Start from the client.

The approval screen says "Unverified application"

The client registered itself without a verifiable identity. This is normal for some clients, especially command-line tools and self-hosted agents. Continue only if you started the connection yourself just now. If you did not, click Cancel and check Settings → MCP Connections for connections you do not recognize.

I approved, but the client says authorization failed

The client may have timed out while waiting. Try connecting again.
Claude Code listens on a random local port. A local firewall that blocks incoming connections on localhost can prevent the return step. Allow the connection or try from another machine.
Check the return address on the approval screen matched the client you were using. If it did not, do not approve; instead remove the connector in the client and re-add it.

While using the assistant

The assistant does not see any Funnelfeedr tools

Make sure the connector is enabled in the current chat. Most clients let you toggle connectors per conversation.
Check Settings → MCP Connections in Funnelfeedr. If the connection is missing, it was revoked; connect again from the client. A connection that has not been used for 30 days stays listed, but its tokens have expired and the client has to connect again.

A specific tool is missing

Tools the connection lacks the scope or seat for are hidden. Common cases:

The prospecting tools (search_organizations, search_contacts, the list and saved-search tools, and the write tools) require a Prospect seat. An administrator assigns seats under Settings → Users. See Seats.
The write tools (create_list, add_organizations_to_list, remove_organizations_from_list, add_contacts_to_list, remove_contacts_from_list, save_search, create_ideal_customer_profile) require the Write scope. If the connection only holds Read, remove the connector in the client and connect again, and check that Write is listed on the approval screen. switch_account is the exception: it works on a read-only connection.
The reveal tools (quote_reveal, reveal_contacts) require the Reveal scope (mcp:spend). They are always hidden or shown together, so if the assistant cannot even price a reveal, the scope is missing. See below.

The assistant answered from the wrong account

Check the first line of the reply: for a user who belongs to several Funnelfeedr accounts, answers start with the account they came from. If it is the wrong one, either tell the assistant "switch to Example AB" or change the Account column under Settings → MCP Connections. Asked in the chat, the switch takes effect on the assistant's next request. Changed in the Account column it can take up to about two minutes, so wait that long before asking again. Either way the answer you already have was produced in the old account, so ask your question again afterwards.

"The assistant says it cannot switch accounts"

If the assistant reports that the connection was authorized before account switching existed, it is running on a connection made by an older version of Funnelfeedr. Remove the connector in the client and connect again; on the approval screen you can pick the account directly. You can also point the existing connection at the right account from Settings → MCP Connections without reconnecting.

If instead it says the account is not one you belong to, use the exact account name as it appears in Settings → MCP Connections, or ask the assistant to list the accounts it can switch to.

"The search matched too much to rank"

A plain-language description ranks every company the filters leave, so it needs the filters to leave a workable set. Add something concrete (an industry code, a tag, an employee or revenue range, a region, municipality or city) and ask again. For example, "dental clinics in Skåne with at least 5 employees" works where "dental clinics" does not.

"query was supplied with no filter other than the market"

The same rule, refused before the search runs: a description on its own is not a search. Add at least one ordinary filter besides the market. If you truly want everything in one industry, drop the description and just filter. An unranked search needs no ranking source.

The assistant found nothing for a tag, technology or municipality

Those filters match exactly, so a guessed value returns an empty result rather than an error. Ask the assistant to check the valid values first (it has get_filter_vocabulary for tags, technologies, legal forms, municipalities, regions, contact areas and target roles). Note also that several tags or keywords match a company carrying any of them, not all. To narrow, pass fewer values or exclude something.

"The connection is not authorized for … the required OAuth scope was not granted"

The connection has the Read scope but the assistant tried a write. Reconnect, and check that the Write scope is listed on the approval screen. See Authorizing an MCP client with OAuth.

"… requires the … permission, which this user's role does not grant"

Your Funnelfeedr role lacks the permission the tool mirrors (the message names it, for example leads:read or leads:write). An administrator can change your role under Settings → Users. The MCP server never grants more than the web app would.

"… requires the … capability"

See A specific tool is missing above.

"… was rate limited"

You hit a per-minute limit (60 requests, 20 searches, 10 writes or 5 reveals per minute per user; looking up several companies at once with find_organization counts as one search). The error tells the assistant how many seconds to wait, and most assistants retry on their own. If it happens often, ask the assistant to use larger page sizes or fewer, broader searches. Reveals have the tightest limit on purpose, because each one spends credits. For a big batch, expect the assistant to work through it a call at a time.

The connector says it cannot reveal, or asks me to reconnect

Revealing contact details needs its own approval: the Reveal scope (mcp:spend), which is separate from Read and Write because it spends your account's credits. A few different symptoms all come back to the same causes.

The assistant says it has no way to reveal contacts, or does not mention revealing at all. The connection does not have the Reveal scope, so both reveal tools are hidden from it. This is what you see on every connection approved before revealing existed, and there is no way to add the scope in place. Remove the connector in the client and add it again, and check that Reveal is listed on the approval screen. Approving Write earlier does not cover this.
"The connection is not authorized for 'reveal_contacts': the required OAuth scope 'mcp:spend' was not granted." The same thing, said explicitly. Same fix.
"This reveal costs … credits and the account has …" The account cannot afford it, so nothing was revealed and nothing was charged. Buy credits under Settings → Billing and ask again.
"The confirmation expired" / "no longer matches" / "is not valid." The confirmation a reveal runs on works once and lasts five minutes, and it is tied to the exact contacts and the exact price you were shown. If you took a while to answer, or the set changed in between, the reveal is refused rather than charged at a price you did not approve. Just ask again: the assistant re-quotes and you confirm the fresh figure.
Your client keeps asking you to confirm. That is intended. reveal_contacts is marked as a spending action, so clients such as Claude prompt on every call. The free quote_reveal does not prompt, because it charges nothing.

Contact emails and phone numbers are masked

This is expected until the contact is revealed. A masked email keeps only its domain and a masked phone only its first five digits. You have two ways forward: reveal the contact in the web app, and the assistant sees the details on its next call, or ask the assistant to do it. It will quote the cost first and reveal once you approve. Contacts your account revealed within the past year are already unmasked and cost nothing.

The assistant returns stale results

Tool results are cached briefly by some clients. Ask again, or start a new conversation.

The connection stopped working after a few weeks

Refresh tokens expire after 30 days without use. Connect again from the client; your previous approval is remembered. The screen shows the scopes as Already granted, or is skipped entirely if you belong to only one account and the client asks for nothing new.

Still stuck?

Check Settings → MCP Connections, revoke the connection, remove the connector in the client, and set it up again from scratch following Connect Claude, ChatGPT or another MCP client. If it still fails, contact Funnelfeedr support and include the client you are using, the exact error text and roughly when it happened, so we can find the corresponding log entry.