rifts.to

rifts.to MCP server

Ask your AI client to poll your audience, then read the answers back without leaving the chat.

claude mcp add --transport http rifts https://mcp.rifts.to/mcp

That is Claude Code. Claude Desktop and claude.ai take the same URL as a custom connector.

$11.99 a month

Creating and answering surveys on rifts.to is free and needs no account. The subscription buys programmatic access: an API token, this server, and the REST API underneath it. It is checked on every call, so a lapsed subscription stops the connector on the next request rather than at renewal.

See the plan

Four tools

The whole survey loop and nothing else. Editing questions, theming, collaborators and CSV export stay in the browser dashboard, where each one already has its own permission check.

create_survey

Builds a survey from a title and a list of questions, then returns the public link and the admin link. Takes an optional custom slug.

list_surveys

Lists the surveys on your account with title, status and response count. Admin links come back only if you ask for them, so a routine listing does not hand a model a pile of credentials it did not need.

get_survey_results

Returns a survey's questions and every response.

close_survey

Stops a survey accepting new responses. Reopening and retitling stay in the dashboard.

Setting it up

The hosted server signs you in through the browser. There is no token to paste and nothing to copy out of your account settings.

  1. Subscribe from your billing page. Without an active subscription there is no token to issue, on the consent screen as well as in account settings.

  2. Add the server to your client. In Claude Desktop and on claude.ai that is Settings, then Connectors, then Add custom connector, with this URL. In Claude Code it is one command.

    claude mcp add --transport http rifts https://mcp.rifts.to/mcp

  3. Approve the connection when rifts.to opens in your browser. Your client registers itself, you approve it, and it keeps the token it gets back.

  4. Revoke it whenever you want, under Connected applications on your account page.

Or run your own copy

The server is Apache-2.0 and holds no credentials of its own. Every request carries your token straight to the rifts.to API, so the copy you run stores nothing, caches nothing and logs nothing.

It needs the same token from the same paid account. The subscription pays for access to the account rather than for the hosting, so there is no separate self-hosting tier and no discount to ask for.

RIFTS_TOKEN=rifts_pat_... npx @rifts_to/mcp

Reference

Back to home