Okendo MCP server
Okendo in any MCP client, through Memtro: Okendo does not publish this server. Memtro's Okendo connector reads Okendo 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
Okendo reviews, surveys and loyalty for a Shopify store: product reviews by status with rating, text, reply and sentiment, survey and quiz results as counts, averages and NPS per question, and a loyalty member's status, tier, ways to earn and redeem and active coupons; when you ask, can reply to a review (emailing the customer only if told to), approve, hold or reject a review, adjust a member's points, redeem a reward for them, trigger a custom earning rule, set a minimum VIP tier and record achievement progress.
Reads
okendo_list_reviewsOkendo product reviews (published by default, or pending or rejected ones), newest first or by rating: product, rating, title, text, reply…okendo_get_reviewOne Okendo review in full: product and variant, rating, title, text, reply, attributes rated, sentiment, tags, status and source.okendo_list_surveysOkendo surveys: name, how many responses each has, when the last one came in, archived or not.okendo_survey_resultsResults of an Okendo survey over its most recent responses (up to 300): for each question, how many answered, the count per choice…okendo_quiz_resultsResults of an Okendo quiz over its most recent responses (up to 300): per question the count per choice and rating averages…okendo_loyalty_memberAn Okendo loyalty member, found by their email or loyalty customer id: membership status (pending, enrolled, blocked), VIP tier…okendo_loyalty_rulesThe store's Okendo loyalty programme: the ways to earn (points per order, per spend, for a review…
Acts, when you ask
These change something in Okendo. 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.
okendo_reply_to_reviewReplies to an Okendo review as the store.okendo_set_review_statusModerates an Okendo review: approved publishes it on the storefront, pending holds it back, rejected hides it.okendo_adjust_pointsAdds (positive) or removes (negative) loyalty points for an Okendo member: points are worth money off at the store.okendo_redeem_rewardSpends an Okendo member's points on a reward for them, issuing a coupon or store credit to their account; it cannot be undone.okendo_trigger_earning_ruleTriggers one of the store's custom Okendo earning rules for a member, awarding its points or reward (value multiplies a points-per rule).okendo_set_minimum_vip_tierGives an Okendo member a minimum VIP tier (they keep at least that tier's benefits, until the expiry if one is given)…okendo_track_achievementRecords an Okendo member's progress towards a custom loyalty achievement: delta adds to (or with a negative value subtracts from) their progress…
Connect it
First connect Okendo on Dashboard → Connections, then add Memtro to your client once. The Okendo 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 Okendo 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
- › Which reviews of one star or two came in this week?
- › What is the average rating for the linen shirt?
- › What was the NPS on last month's post-purchase survey?
- › What VIP tier is this loyalty member on, and how many coupons do they hold?
- › Reply publicly to the latest review of the travel mug to thank them.
Questions
- Is this an official Okendo MCP server?
- No. It is Memtro's MCP server with Memtro's Okendo connector behind it: the connector reads Okendo through its API with the credentials you connect on Dashboard → Connections, and Okendo 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 Okendo?
- Only when you ask, and only what it has been granted: reply to a review publicly or privately, emailing the customer only when asked; approve, hold for moderation or reject a review; add or remove a loyalty member's points; redeem a points reward for a loyalty member (issues a coupon or store credit); trigger a custom earning rule for a loyalty member; set or clear a loyalty member's minimum VIP tier; record progress towards a custom loyalty achievement. 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.