All releases

MCP V1: hosted endpoint, thin bridge, and tools that ship without reinstalling

MCP V1: hosted endpoint, thin bridge, and tools that ship without reinstalling

We rebuilt the Simple Product MCP. Tool definitions now live on simpleproduct.dev itself, served from a hosted MCP endpoint at /api/mcp/v1. The npm package becomes a thin stdio↔HTTP bridge that authenticates and forwards.

Why this matters

Until today, every change to an MCP tool — adding one, fixing a description, tightening an input schema — meant publishing a new npm version and asking everyone to reinstall. That's a long feedback loop for something that should be invisible.

Now, when we add or improve a tool server-side, every existing install picks it up on the next session. No npx … --install, no version bump, no nag to upgrade. We used this immediately to ship two new tools — whoami and list_workspaces — that don't appear in any npm package. They just showed up in everyone's installed bridge.

What's in 0.2.x

@simple-product/mcp@0.2.0 is the bridge. It:

  • Reads ~/.simple-product/config.json for auth (same install flow as before)
  • Connects to simpleproduct.dev/api/mcp/v1 over HTTPS
  • Forwards tools/list → server returns the live tool catalog
  • Forwards tools/call → server runs the tool and returns the result
  • Stays out of the way otherwise

The install path is unchanged. npx @simple-product/mcp@latest --install still detects every supported AI client (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, etc.) and writes config; only the runtime behavior is different.

0.2.1 adds back switch_workspace. Tools that mutate local state (rewriting your project's workspace pinning) still need to live in the bridge code itself, so this one did need a publish. The bridge advertises it in tools/list and intercepts the call locally instead of forwarding it.

New tools available right now

Live for every 0.2.x install with no reinstall:

  • whoami — Confirms which user and workspace your MCP is authenticated as. Quick sanity check when juggling multiple workspaces.
  • list_workspaces — Every workspace you're a member of, with the active one flagged.
  • switch_workspace — Bumps to 0.2.1 of the bridge, but functionally unchanged from 0.1.x.

Try them: in any AI client connected to Simple Product, ask "use whoami to confirm which workspace I'm in."

Coexistence and rollback

@simple-product/mcp@0.1.x (with tools baked into the package) is still on npm and still works. The legacy /api/mcp/execute endpoint stays alive indefinitely — both 0.1.x and 0.2.x clients have a stable, supported home.

If the new bridge misbehaves on your machine:

# Drop back to the legacy bundled-tools build
npx @simple-product/mcp@0.1.19 --install

Or, in-place, without reinstalling — pass --legacy to the 0.2.x runtime to switch to the old bundled-tools mode for the current session.

What's next

With tool changes shipping server-side, the bottleneck for new MCP capabilities is now the SP server, not the npm release cycle. Expect more tools, faster, with no install nag — and a few quality-of-life additions to the install flow itself as we use it more.

This release ships in @simple-product/mcp@0.2.1.