Is this an official Feefo MCP server?

No. It is Memtro's MCP server with Memtro's Feefo connector behind it: the connector reads Feefo through its API with the credentials you connect on Dashboard → Connections, and Feefo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Feefo?

Only when you ask, and only what it has been granted: publish a public reply to a Feefo review, under a named author. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Social and reputation

Feefo MCP server

Feefo in any MCP client, through Memtro: Feefo does not publish this server. Memtro's Feefo connector reads Feefo through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Feefo reviews for one merchant: the overall service and product ratings with star breakdowns, and recent service and product reviews with their ratings and text; can publish a reply to a review (needs an App Key).

Reads

feefo_review_summaryThe merchant's Feefo rating: overall score, service and product ratings with counts per star, for a period.
feefo_list_reviewsFeefo reviews, most recently updated first: one row per sale with the service rating and review and any product reviews (product, SKU, rating, text)…

Acts, when you ask

These change something in Feefo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

feefo_reply_to_reviewPublishes a reply to a Feefo review (a service review or one product review, by its id from feefo_list_reviews)…

Connect it

First connect Feefo on Dashboard → Connections, then add Memtro to your client once. The Feefo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Feefo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What is our Feefo rating right now?
› How many 1-star reviews did we get this month?
› What did customers say about delivery in the last month?
› Which products got low ratings in recent Feefo reviews?
› Reply to yesterday's 2-star review apologising for the late delivery

Questions

Is this an official Feefo MCP server?: No. It is Memtro's MCP server with Memtro's Feefo connector behind it: the connector reads Feefo through its API with the credentials you connect on Dashboard → Connections, and Feefo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Feefo?: Only when you ask, and only what it has been granted: publish a public reply to a Feefo review, under a named author. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.