Readyset Claude Code Plugins

A Claude Code plugin marketplace for Readyset.

Two plugins are available — pick one based on whether you operate the Readyset server:

Plugin	Transport	Auth	When to use
readyset-mcp	HTTP (Streamable)	Bearer token with scopes	You operate the Readyset server (or your operator has enabled the MCP HTTP listener for you)
readyset-mcp-stdio	stdio	Database credentials	You don't control the Readyset server and can't restart it with the MCP HTTP listener enabled — the binary connects over the SQL wire protocol like any other client

Add the marketplace

/plugin marketplace add readysettech/readyset-claude-plugins

Option 1: HTTP plugin (recommended)

/plugin install readyset-mcp@readyset

Claude Code will prompt for two values:

• Readyset MCP URL — the Streamable HTTP endpoint exposed by your Readyset server. Defaults to http://127.0.0.1:6035/mcp (Readyset's default --mcp-address mounted at /mcp).

• Bearer token — issued in Readyset with:

  CREATE MCP TOKEN '<name>' WITH SCOPE <read_only|cache_admin|full>;

  Stored as a sensitive value by Claude Code. Read tools require read_only or higher; create_cache and drop_cache require cache_admin or full.

Option 2: stdio plugin

Use this plugin when you want to run MCP tools against a Readyset server you don't control — for example, a shared deployment where you can't restart the process to enable the MCP HTTP listener. The standalone readyset-mcp binary connects to Readyset over the SQL wire protocol just like any other database client, so it works as long as you have SQL credentials.

/plugin install readyset-mcp-stdio@readyset

Prerequisite: download the readyset-mcp binary for your platform from the Readyset releases page and put it on your PATH.

Claude Code will then prompt for the SQL connection details (host, port, user, password, db type, optional database and TLS mode).

Trade-offs vs. the HTTP plugin

• No scopes. Stdio authenticates with raw database credentials, so any caller can invoke create_cache / drop_cache. Restrict at the database grant level if that matters.
• Per-session process. Each Claude Code session spawns its own readyset-mcp process and its own SQL connection.
• More config. Six fields vs. URL + token.
• Manual install. The binary doesn't ship with the plugin; you install it from GitHub Releases yourself.

If you operate the Readyset server, prefer Option 1.

Tools exposed

Both plugins expose the same MCP tool surface:

• readyset_status, readyset_version
• show_caches, show_proxied_queries, show_proxied_supported
• explain_cache_support
• create_cache, drop_cache