Oneshot MCP Server

Search receipt-verified agent build packs, with each pack's real M-of-N pass rate.

Local serverstdioTypeScript

What is the Oneshot MCP server?

Connect Oneshot to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Search receipt-verified agent build packs, with each pack's real M-of-N pass rate. The oneshot mcp server is what makes that connection.

What the server does

An MCP server that lets your coding agent query the OneShot catalog of receipt-verified build packs without you leaving your editor. Mid-build, your agent can ask "is there a verified pack for this?" instead of you having to remember to check the storefront.

Installation

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Cursor — Once published to npm, same swap as above ("command": "npx", "args": ["-y", "oneshot-mcp"])

Credentials and setup notes

Configuration is passed through the environment: ONESHOT_CATALOG_URL, ONESHOT_SITE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Node >= 22.6 (uses Node's built-in TypeScript type-stripping to run .ts source directly -- no build step, no bundler, no tsc in the loop).

Worth knowing first

  • 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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Oneshot's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by com.oneshotpacks; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
CursorOnce published to npm, same swap as above ("command": "npx", "args": ["-y", "oneshot-mcp"]).

How to install the Oneshot MCP server

{
  "mcpServers": {
    "oneshot": {
      "command": "node",
      "args": ["/absolute/path/to/oneshot/oneshot-mcp/src/index.ts"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

Node >= 22.6 (uses Node's built-in TypeScript type-stripping to run .ts source directly -- no build step, no bundler, no tsc in the loop).

VariableDescriptionRequired
ONESHOT_CATALOG_URLEndpoint or connection string the server talks to.Yes
ONESHOT_SITE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Oneshot to Cursor.

Frequently asked questions

It connects Oneshot to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Cursor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Oneshot directly.