MCP Chaos Rig MCP Server

A local MCP server that breaks on demand. Test your client against auth failures, disappearing tools, flaky responses, and token expiry.

Local serverstdio

What is the MCP Chaos Rig MCP server?

MCP Chaos Rig MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A local MCP server that breaks on demand. Test your client against auth failures, disappearing tools, flaky responses, and token expiry.

Setting it up

Installation goes through your MCP client rather than a global install: point it at mcp-chaos-rig on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once MCP Chaos Rig is connected, these are the calls the assistant has available:

  • echo — returns your message (v2 adds format options)
  • add — sums two numbers (v2 accepts an array)
  • get-time — current server time as ISO 8601
  • random-number — random integer in a range
  • reverse — reverses a string
  • typeEcho — echoes one optional parameter per JSON Schema primitive, to check a client round-trips every type
  • dispute-charge — files a billing dispute, returns a JSON receipt
  • list — contacts, get-contact-by-id, get-contact-by-email, search-contacts, create-contact, update-contact, delete-contact: SQLite CRUD
  • Server — Configure auth mode, slow mode (random latency), and flaky tools (% failure rate)
  • Tools — Toggle tools on/off. Disabling sends tools/changed to connected clients. Some tools (echo, add) support version switching
  • Contacts — View and reset the SQLite database backing the contact tools. Starts with three seed records

Configuration and credentials

You will need 3 environment variables: BASE_URL, STATIC_CLIENT_ID, STATIC_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Chaos Rig.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp chaos rig mcp server does with a few real requests.

Choosing this one

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Chaos Rig's toolset — echo, add, get-time and 8 more — is a fair guide to whether it matches your workflow. It is maintained by typewise; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Chaos Rig's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
echoreturns your message (v2 adds format options)
addsums two numbers (v2 accepts an array)
get-timecurrent server time as ISO 8601
random-numberrandom integer in a range
reversereverses a string
typeEchoechoes one optional parameter per JSON Schema primitive, to check a client round-trips every type
dispute-chargefiles a billing dispute, returns a JSON receipt
listcontacts, get-contact-by-id, get-contact-by-email, search-contacts, create-contact, update-contact, delete-contact: SQLite CRUD
ServerConfigure auth mode, slow mode (random latency), and flaky tools (% failure rate).
ToolsToggle tools on/off. Disabling sends tools/changed to connected clients. Some tools (echo, add) support version switching.
ContactsView and reset the SQLite database backing the contact tools. Starts with three seed records.

How to install the MCP Chaos Rig MCP server

{
  "mcpServers": {
    "chaos-rig": {
      "command": "npx",
      "args": ["-y", "mcp-chaos-rig"],
      "env": {
        "BASE_URL": "your-value",
        "STATIC_CLIENT_ID": "your-value",
        "STATIC_CLIENT_SECRET": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
BASE_URLEndpoint or connection string the server talks to.Yes
STATIC_CLIENT_IDConfiguration value read at startup.Optional
STATIC_CLIENT_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Chaos Rig to echo.
  • Use MCP Chaos Rig to add.
  • Use MCP Chaos Rig to get-time.

Frequently asked questions

It connects MCP Chaos Rig to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (echo, add, get-time, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Chaos Rig directly.