SurveySparrow MCP server

What the model can do

SurveySparrow surveys and feedback: surveys by type and date, a survey's responses with each question's answer, comment and sentiment, NPS, CSAT and CES scores, help-desk tickets with requester and agent and their comments, contacts and contact lists, the account's users, and reputation reviews by platform and rating. Can add an internal note or a public comment to a ticket, open or update a ticket, create or edit a contact, and create a contact list, each only when asked.

Reads

• surveysparrow_list_surveysList SurveySparrow surveys: id, name, type (Conversational, ClassicForm, NPS, CSAT, CES …), folder, archived, created and updated.
• surveysparrow_list_responsesResponses to one SurveySparrow survey: when completed, the channel, the contact id, and each question with the respondent's answer (scores, ratings…
• surveysparrow_metricsNPS, CSAT or CES score from SurveySparrow for one survey, or across every CX survey of that kind when no survey is given, optionally for a date range.
• surveysparrow_list_ticketsSurveySparrow help-desk tickets: subject, status, priority, requester (name and email), agent (name and email), team, due times, created and updated…
• surveysparrow_get_ticketOne SurveySparrow ticket with its description and its comments (newest page first as SurveySparrow returns them): who wrote each…
• surveysparrow_list_contactsSurveySparrow contacts (and employees): id, name, email, job title, type, whether unsubscribed or active, and lists.
• surveysparrow_list_usersThe SurveySparrow account's users (staff): id, name, email, whether admin or owner, verified, and role id.
• surveysparrow_list_contact_listsSurveySparrow contact lists: id, name and description.
• surveysparrow_list_review_platformsThe review sources SurveySparrow's reputation management watches (app platforms): id, location, whether active, and the address it reads reviews from.
• surveysparrow_list_reviewsPublic reviews SurveySparrow has collected from one review platform: rating, title, text (truncated), date and the reviewer's display name.

Acts, when you ask

These change something in SurveySparrow. 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.

• surveysparrow_add_ticket_noteAdd an internal note to a SurveySparrow ticket.
• surveysparrow_post_ticket_commentPost a public comment on a SurveySparrow ticket.
• surveysparrow_create_ticketOpen a SurveySparrow ticket for a requester (a contact, by id or email; an unknown email may create the contact).
• surveysparrow_update_ticketChange a SurveySparrow ticket's status, priority, assignee or team.
• surveysparrow_create_contactCreate a SurveySparrow contact (or employee).
• surveysparrow_update_contactChange a SurveySparrow contact's name, email, phone, mobile or job title.
• surveysparrow_create_contact_listCreate an empty SurveySparrow contact list.

Connect it

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

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

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

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

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 SurveySparrow 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 NPS this quarter?
• › What did detractors say in last month's survey?
• › Which open tickets are assigned to Tom?
• › What are our latest one-star reviews?
• › Add an internal note to ticket 4182 that a fix ships Friday

Questions

Is this an official SurveySparrow MCP server?

No. It is Memtro's MCP server with Memtro's SurveySparrow connector behind it: the connector reads SurveySparrow through its API with the credentials you connect on Dashboard → Connections, and SurveySparrow 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 SurveySparrow?

Only when you ask, and only what it has been granted: add an internal note to a ticket (seen only by the team); post a public comment on a ticket (may reach the requester); open a ticket for a contact (the requester may be told); change a ticket's status, priority, assignee or team; create a contact; change a contact's name, email, phone, mobile or job title; create a contact list. 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.

Other MCP servers · Marketing automation

• ActiveCampaign MCP server
• Brevo MCP server
• Customer.io MCP server
• Marketo Engage MCP server
• Account Engagement (Pardot) MCP server
• Mailchimp MCP server