Skip to main content
Usertick hosts a Model Context Protocol server, so nothing needs to be installed. An AI assistant that supports MCP connects to its URL, and you sign in to Usertick and choose what it may do. When you ask in plain language, the assistant reads your surveys, responses and metrics, triages responses, pauses surveys and manages webhook subscriptions. It can do only what you allowed and what your own role can do.
Every member can connect an assistant for themselves. The sign-in follows the MCP authorization spec, so no key or token is copied anywhere. The server takes only the access tokens Usertick issues when an assistant signs in. API keys are for the REST API, and the MCP server refuses them.

​
Connect an assistant

In Claude on the web, the desktop app or mobile, open Settings → Connectors, select Add custom connector and enter https://mcp.usertick.com/mcp. Claude opens the Usertick sign-in.
Members who can manage developer settings find the same setup under Settings → Developers → API keys, in Connect an AI assistant, where Cursor and VS Code also get an install link.

​
Sign in and choose the access

When the assistant first connects, Usertick asks you to sign in and shows what the assistant asks for.
1

Pick the organization

The assistant reaches one organization. Any organization you belong to can be picked, as long as your role reaches every survey in it.
2

Choose what it may do

Reading surveys, responses, metrics and webhooks is selected to start. Select more only when the assistant should change something, such as pausing surveys or updating responses.
3

Allow access

Usertick sends you back to the assistant, which can now use the tools your choice allows.
If Usertick doesn’t recognize the assistant, the sign-in says so and names where it sends you after you answer. Allow access only to an assistant you are connecting yourself. The assistant acts as you: what you allowed limits it, and so does your role. A change your role can’t make fails with AUTHZ-001-002, whatever you allowed. To change what it may do, connect it again and choose its access anew: the new choice replaces the old one.

​
Disconnect an assistant

Under Settings → Security, Connected assistants and apps lists the assistants you connected in the active organization. Select Revoke access to disconnect one at once. Members who can manage integrations or developer settings see every member’s assistants under Settings → Developers → API keys and can revoke any of them. Usertick also disconnects an assistant when you leave the organization or your account is deleted, and when it goes unused: a connection that never finished signing in after a day, and one without a usable refresh token after 90 days.

​
Test the connection

Ask the assistant something like “Use Usertick to pull the latest responses and summarize the main complaints.” The assistant calls get_recent_responses and answers from your data. If a tool fails, ask the assistant to run test_auth, which shows what you allowed. An APK-004-004 error means you didn’t allow the access that tool needs.

​
Tools

Each kind of access you allow unlocks its own tools. A tool whose access you didn’t allow returns APK-004-004. Every tool tells the assistant whether it only reads or changes something. delete_response, erase_respondent, delete_response_note and unsubscribe_webhook are marked as removing data, so an assistant that confirms risky actions asks before it runs them. Responses are returned as the Response resource, with the survey, every answer with its question text, the respondent’s email when there is one, the status and assignees, and the AI’s type, urgency, theme, category and sentiment. Deliveries to a subscribed URL carry the same resource in data, except theme.spiking deliveries, which carry the spike. Deliveries are signed as Verify signatures describes. The time window of list_responses and get_metrics (from and to) and updatedSince take an RFC 3339 time, such as 2026-10-14T09:30:00Z, or a date alone, such as 2026-10-14. A time without an offset reads as UTC. A date alone starts at that day’s midnight in UTC, and as to it includes that whole UTC day. Any other value is refused before a request reaches the API. The server is a thin layer over the REST API. The API itself enforces what you allowed, your role, the plan, retention windows and rate limits. When a call fails, the tool’s error carries the API’s error code with its message, or every invalid field with its message. When the API sends Retry-After, as it does with a 429, the error also says how long to wait. The assistant can react to each of these.

​
Limits

  • One message per request. The server takes one JSON-RPC message per request, and a batch (a JSON array of messages) returns 400.
  • 120 requests per minute to the server from one IP address. A request over the limit returns 429, and the client can try again after a minute.
  • 15 seconds per API call. When the API doesn’t respond in time, the tool returns an error that asks the assistant to try again.
  • The API’s own rate limits also apply to the connection.
  • The organization’s plan must include the API (Pro and up). After a move to a lower plan, the connection stays and its calls are refused, and the approval isn’t revoked, so it works again after an upgrade.
Every connection belongs to the person who signed in. To give a script or a server Usertick access without a person, use an API key with the REST API instead.