MCP Server

Manage your PackEdge store from any AI agent — Claude Desktop, Claude Code, Cursor, and other Model Context Protocol clients. Ask in plain language; the agent calls PackEdge for you.

"List my products." · "Issue a license for prd_… to [email protected]." · "Which licenses are expired?" · "What's my revenue this month?"

The server is a small program that runs locally and talks to the Developer API using your API key. Your data flows between your machine and PackEdge only — nothing extra is stored.

Install

1. Create an API key

1. Open the PackEdge Console
2. Go to Settings → API Keys → Create API Key
3. Copy the key (shown once) — it looks like pk_…

2. Add the server to your agent

The server runs via npx, so there's nothing to install globally. Add this to your agent's MCP configuration:

Claude Desktop

{
  "mcpServers": {
    "packedge": {
      "command": "npx",
      "args": ["-y", "@packedgedev/mcp"],
      "env": {
        "PACKEDGE_API_KEY": "pk_your_key_here"
      }
    }
  }
}

Cursor / .mcp.json

{
  "mcpServers": {
    "packedge": {
      "command": "npx",
      "args": ["-y", "@packedgedev/mcp"],
      "env": {
        "PACKEDGE_API_KEY": "pk_your_key_here"
      }
    }
  }
}

Restart your agent. You should see the PackEdge tools become available.

Configuration

Variable	Required	Default	Description
PACKEDGE_API_KEY	✅	—	Your pk_… API key.
PACKEDGE_BASE_URL		https://api.packedge.dev	API base URL (override for self-hosted/dev).
PACKEDGE_READONLY		off	Set to 1 to expose only read tools — no create/update/delete.

Safer by default

If you mostly want lookups and reports, set PACKEDGE_READONLY=1. The agent will then only be able to read your data, never change it.

What it can do

Read (always available)

• Products — list, get
• Licenses — list, get
• Customers — list, get
• Sites — list, get
• Account stats — product/license/site/customer counts + total revenue
• Revenue summary — all-time and rolling-window revenue with a daily series

Write (hidden when PACKEDGE_READONLY is set)

• Products — create, update, archive
• Licenses — issue, update (incl. revoke), delete
• Customers — create, update, delete
• Sites — deactivate

Write actions are marked so well-behaved agents ask you to confirm before running them. To revoke a license, update its status to revoked rather than deleting it — deletion is permanent.

Example prompts

• "How many active licenses do I have, and what's my total revenue?"
• "Issue a 3-seat license for product prd_abc to [email protected] expiring next year."
• "Find the customer [email protected] and list her licenses."
• "Revoke license lic_xyz."
• "Show revenue for the last 90 days."

Notes & limits

• Today the server manages products, licenses, customers, sites, and reads account stats & revenue. Releases, plans, and webhook management arrive as the Developer API expands.
• The Developer API is rate-limited (see Rate Limits); the server retries transient 429s automatically.
• The package is open source in the PackEdge repository under packages/mcp.