Integration

Simplesat integration

Simplesat collects customer satisfaction surveys (CSAT, NPS, CES) from help desks and email. Search and read survey responses and individual answers, update answers and responses, create or update customers (one at a time or in bulk) and team members, list surveys and questions, and send a survey to a customer by email. Authentication is an API key sent in the X-Simplesat-Token header; each key carries read or write scopes per resource, set on the Simplesat API keys page.

Connect Simplesat How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Simplesat.Built from the 17 Simplesat tools below, on the connection you add once.

What you can do with Simplesat

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Customer, 4 operations

create_or_update_customerCreate or update customerPOSTCreates a customer, or updates the one with the same email. Sending tags or custom_attributes overwrites the existing values. Needs the write customers scope.
get_customer_by_idGet customer by idGETReturns one customer by id: name, email, company, language, tags and custom attributes. Needs the read customers scope.
list_customersList customersGETLists customers, filtered by creation or modification date and subscription status. Paginated: pass page until next is null. Needs the read customers scope.
update_customer_by_idUpdate customer by idPUTUpdates a customer by id; leave out a field to keep it. Sending tags or custom_attributes overwrites the existing values. Needs the write customers scope.

Answer, 2 operations

get_answer_by_idGet answer by idGETReturns one survey answer by id: its choice, comment, follow-up answer, sentiment, question, survey, response_id and topics. Needs the read answers scope.
update_answer_by_idUpdate answer by idPUTUpdates an answer's choice, choices, comment or follow-up answer. Send at least one of choice, choices or comment; leave out a field to keep it. Needs the write answers scope.

Search, 2 operations

search_answersSearch answersPOSTSearches survey answers by date range and filters (key, values, comparison). Paginated: pass page until next is null. Needs the read answers scope.
search_responsesSearch responsesPOSTSearches survey responses by date range and filters (key, values, comparison, optional attribute). Paginated: pass page until next is null. Needs the read responses scope.

Team member, 2 operations

create_or_update_team_memberCreate or update team memberPOSTCreates a team member, or updates the one with the same email. Sending custom_attributes overwrites the existing ones. Needs the write team members scope.
get_team_member_by_idGet team member by idGETReturns one team member by id: name, email, custom attributes and groups. Needs the read team members scope.

Bulk, 1 operation

bulk_upsert_customersBulk upsert customersPOSTCreates or updates up to 1000 customers in one request, matched by email; customers with invalid data are ignored. Returns a request_id. Needs the write customers scope.

Create or update, 1 operation

create_or_update_responseCreate or update responsePOSTCreates a survey response, or updates the one with the same external id. A new response needs survey_id and answers. Customers and team members are matched or created by email. Needs the write responses scope.

Email, 1 operation

send_survey_by_emailSend survey by emailPOSTEmails a survey to a customer right away. Only surveys of type event_based_email are accepted. Needs the write surveys scope.

Question, 1 operation

list_questionsList questionsGETLists survey questions, optionally for one survey or one metric. Paginated: pass page until next is null. Needs the read questions scope.

Response, 1 operation

get_response_by_idGet response by idGETReturns one survey response by id with its survey, answers, customer, team members, ticket, tags and source. Needs the read responses scope.

Survey, 1 operation

list_surveysList surveysGETLists active surveys, newest first (archived surveys are not returned), optionally filtered by name. Paginated: pass page until next is null. Needs the read surveys scope.

Update, 1 operation

update_response_by_idUpdate response by idPUTUpdates a survey response by id. survey_id is required by the vendor; send the current one (get_response_by_id) with the fields to change. Tags and custom_attributes overwrite. Needs write responses scope.

Use Simplesat from Claude Code, Cursor or Codex

Connect Simplesat in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Simplesat operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Simplesat

Create your workspace
Sign up free. Nothing to install.
Connect Simplesat once
Add your Simplesat connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.