Rystic

Registre officiel Cartes, voyage et météo

Start, seed, clock, inspect and diff Rystic API simulators from your agent.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

MCPB package https://github.com/Rystic-Inc/rystic/releases/download/v0.0.54/rystic-mcp_0.0.54.mcpb

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Rystic MCP server
  2. Install
  3. Install as a plugin
  4. Configure by hand
  5. Tools
  6. What leaves your machine
  7. Run in a container
  8. Cline
  9. Documentation
  10. License

Rystic MCP server

rystic mcp is a local MCP server that lets your coding agent run Rystic simulators of real APIs (Stripe, GitHub, Slack and more) on your machine. Through MCP tools the agent starts a simulator, loads a scenario, seeds records, moves the clock, reads state and the calls and webhooks the simulator saw, diffs state against where it started, and saves the run as a test case.

The server speaks MCP over stdio: your client launches rystic mcp as a subprocess. It ships inside the rystic CLI.

Install

Mac or Linux, 64-bit.

curl -fsSL https://www.rystic.ai/install.sh | sh

The install ends by signing you in through the browser. A new account starts on the Free plan. For CI or a machine without a browser, create an API key and run rystic login rys_….

Then add the server to your client:

rystic mcp install --client claude-code   # or cursor, codex, vscode, windsurf

Restart the client and approve the rystic server when it asks.

Install as a plugin

The repository is also a plugin for each client below. Each plugin starts rystic mcp, so install the CLI first. When Claude Code cannot find rystic on its PATH, the Claude Code plugin says how to install it, or which folder to add to PATH, as a session starts or resumes.

ClientCommand
Claude Codeclaude plugin marketplace add Rystic-Inc/rystic, then claude plugin install rystic@rystic
Codexcodex plugin marketplace add Rystic-Inc/rystic
Gemini CLIgemini extensions install https://github.com/Rystic-Inc/rystic
Antigravity CLIagy plugin install https://github.com/Rystic-Inc/rystic

Configure by hand

Claude Code (.mcp.json) and Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "rystic": {
      "type": "stdio",
      "command": "rystic",
      "args": ["mcp"]
    }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "rystic": {
      "type": "stdio",
      "command": "rystic",
      "args": ["mcp"]
    }
  }
}

Codex (.codex/config.toml):

[mcp_servers.rystic]
command = "rystic"
args = ["mcp"]

If the client cannot find rystic, set command to its absolute path (command -v rystic prints it).

Tools

ToolWhat it does
list_twinsthe simulators running on this machine
start_twinstarts a simulator, optionally with a scenario, and returns its URL
stop_twinstops a simulator
list_scenariosthe named starting worlds a simulator ships
load_scenariowipes state and loads a scenario
seedmerges records into state
set_clockpins the simulator's clock
advance_clockmoves the clock forward or back
resetempties state and clears the logs
inspect_statereads the whole state or a named view
list_callsthe API calls served since the last reset
list_sentwebhooks, emails and other outbound effects
diff_staterows created, changed and deleted since the baseline
save_test_casesaves the run as a regression test

The tool names say "twin", meaning a simulator.

What leaves your machine

The plugin itself sends nothing: it starts rystic mcp on your machine. The rystic CLI calls www.rystic.ai to sign in, check for updates and download a simulator the first time you start it, and registry.rystic.ai when it runs a simulator in Docker. On the Free and Pro plans a running simulator checks in with lease.rystic.ai at start, every 30 seconds and on exit, carrying your API key and the windows in which it was in use, never your requests, data or hostname. Full list: https://www.rystic.ai/docs/cli#what-leaves-your-machine

Run in a container

The Dockerfile builds an image that runs rystic mcp on stdio. It installs the Linux build of the rystic CLI that www.rystic.ai names for the image's platform and checks its SHA-256 before installing it: the value you pass as RYSTIC_SHA256, or else the one the release names.

docker build -t rystic-mcp .
docker run -i --rm rystic-mcp

The image installs the newest CLI when it is built. Add --build-arg RYSTIC_VERSION=<version> to pin a release, or --no-cache to pick up a newer one on a rebuild. A version pins a name; to pin the bytes, add --build-arg RYSTIC_SHA256=<sha256> with the archive's checksum, and the build checks the download against your value. The checksum is the rystic_<version>_linux_<arch>.tar.gz line of checksums.txt on the release, with the version written without its leading v, as 0.0.38. One checksum covers one platform, so a build that pins it is for that platform alone.

Building pulls the Debian base image from Docker Hub, installs packages from Debian's mirrors and downloads the CLI. Starting the server and listing its tools need no network or sign-in. A simulator the server starts inside the container is reachable only from inside it, and needs a signed-in CLI there, so for everyday use install the CLI on your machine as above.

Cline

Cline can install the server for you by following llms-install.md, which covers installing the CLI, signing in and adding the server to Cline's MCP settings.

Documentation

Full reference: https://www.rystic.ai/docs/mcp-server

License

MIT. See LICENSE.

Questions fréquentes

Qu'est-ce que Rystic ?

Start, seed, clock, inspect and diff Rystic API simulators from your agent.

Comment installer Rystic ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

Faut-il une clé API pour Rystic ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Rystic est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Rystic ?

Il est publié par Rystic-Inc. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.