All releases

MCP: workspace routing that actually sticks, plus personal API keys

What shipped

Two changes that make Simple Product's MCP dramatically more reliable in every AI client — Claude Desktop, mobile, web, Code — plus a new auth path for headless setups.

Per-call workspace routing

Don't worry, its no extra work for you, just extra clarity for your agent.

Every workspace-scoped MCP tool now takes a required workspaceSlug parameter. Instead of relying on ambient session state — which drifted across chats on Claude Desktop / mobile / web, and reset between Claude Code invocations — the workspace is named explicitly on every call.

If you say "list boards in my Acme workspace", your agent passes workspaceSlug: acme. No guessing, no cross-session leakage, no wrong-workspace writes. And if the agent forgets, the call fails fast with a clear schema error the agent self-corrects from — silent wrong-workspace routing is impossible now.

The MCP server also hints your default workspace slug during the initialize response, so agents can route on the very first tool call without a whoami round-trip.

This fixes the long-standing "workspace switching doesn't stick" bug on Claude Desktop and mobile. Two bug reports on our Bugs board closed today.

Personal API keys for MCP

Skip the OAuth browser flow entirely. Create a personal token in Settings → API Keys → Personal (starts with sk_usr_), paste it as a Bearer token, and you're in.

Enables:

  • Headless setups — CI jobs, cron, agents running in containers
  • Faster local dev — no browser hand-off during setup
  • Editors without OAuth support — any MCP client that takes a raw API token works now

What to do

  • Already using MCP? Restart your MCP client (Claude Desktop, Cursor, Windsurf, Claude Code) once to pick up the new tool schemas. Anthropic Custom Connector users especially — the tool defs cache per client session.
  • Setting up MCP for the first time? Nothing changes. npx @simple-product/mcp --install and go.
  • Setting up MCP for a headless environment? See the new "Personal token" section in the MCP docs.

Why this matters

For agent-driven workflows, ambient session state was too confusing. Every AI client handles sessions differently, and none of them handled it in a way that let workspace-switching work reliably. Making the workspace an explicit part of every call — and enforcing it at the schema layer — means agents can't accidentally write to the wrong workspace ever again.

Full docs: simpleproduct.dev/docs/mcp