Creem MCP Server

Developer-friendly & type-safe Typescript SDK specifically catered to leverage _creem_ API.

Local serverstdioTypeScript

What is the Creem MCP server?

Developer-friendly & type-safe Typescript SDK specifically catered to leverage creem API. That is what the creem mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

CREEM is a Merchant of Record (MoR) that lets software companies sell globally without worrying about sales tax, VAT, compliance, or payment infrastructure. We act as the legal seller of your software, so you can focus on building.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — The Setup tool exposed by this server
  • Changesets — We use Changesets for versioning and publishing

Getting it running

The server ships on npm as creem, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: CREEM_API_KEY. 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.

How it compares

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. Creem's toolset — Prerequisites, Setup, Changesets — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Things to watch

  • 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.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
SetupThe Setup tool exposed by this server.
ChangesetsWe use [Changesets](https://github.com/changesets/changesets) for versioning and publishing.

How to install the Creem MCP server

{
  "mcpServers": {
    "creem": {
      "command": "npx",
      "args": ["-y", "creem"],
      "env": {
        "CREEM_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CREEM_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Creem to Prerequisites.
  • Use Creem to Setup.
  • Use Creem to Changesets.

Frequently asked questions

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