Connect an AI tool to your Feedmind data
Feedmind runs a read-only Model Context Protocol server. Any AI tool that speaks MCP can read your scores, products, insights and proof metrics with a token you create. This article covers creating the token, adding the server, and checking that it worked.
Before you start
No AI tool is named here. The steps are the same everywhere: an address, a token, and a place to put both.
You need
A Feedmind account with a connected store, and an AI tool that supports MCP servers. Every plan including Free can create tokens. You do not need Merchant Center connected, though without it the proof questions have nothing to answer from.
What cannot happen
Nothing you do here can change your Feedmind account, your store or your Merchant Center. The server has no writable operation. The worst outcome of a mistake is a tool that cannot read anything.
Four steps, one of which is copying.
Create a read-only token
Settings, then AI access, then Create a read-only token. Name it after the machine or the person who will hold it, so the list stays meaningful later. The token appears once. Copy it before you leave the screen: we store only a hash and cannot show it again.
Add the server
Find where your tool lists MCP servers or connectors. Give it the address below and your token as a bearer token. Some tools ask for a name as well; call it Feedmind.
Use the remote option instead
Some tools expect a local command rather than a URL. Ours is a remote server, so choose the remote, HTTP or URL option where one exists. If a tool only supports local commands, it cannot connect to us today.
Ask it something you can verify
Ask for your catalog score. Compare the number with your dashboard. If they match, the connection is right and everything else the server offers is working too.
https://mcp.getfeedmind.com
When it does not work
- Authentication failed
- The token is wrong, or it was revoked. Check the token list under AI access: a revoked token is gone from it. Create a new one and paste it again.
- The tool connects but returns nothing
- Your account has no scanned catalog yet. Run a scan first: there is nothing to read until a score exists.
- Proof numbers are missing
- Merchant Center is not connected, or it was connected in the last few days and Google has not reported enough yet. The score and product data are unaffected.
- The token shows as never used
- The tool never reached us. That is usually a local command option chosen where a remote one was needed, or a proxy blocking the request.
- You lost the token
- Revoke it and create another. We cannot recover one, by design.
We suggest what to lead with. Your tool decides how it looks.
The server suggests an order: the score first, then the four dimensions, then the proof trend, then the one thing worth doing next. Every number arrives with the sentence it needs, so an answer stays honest even if your tool renders it as plain paragraphs.
- Score and grade band
- The four dimensions
- Proof trend, with its delay note
- One thing to do next
Approving a fix is not something a token can do, so that step always links back into the dashboard.