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]." · "Upload my new release and publish it." · "How are sales trending 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. Read-only mode exposes 37 of the 81 tools.

What it can do

The server registers 81 tools across 16 areas. Everything the Developer API can do, your agent can do.

Read (always available — these 37 tools are the full surface in read-only mode)

• Products — list, get
• Licenses — list, get
• Customers — list, get
• Sites — list, get
• Dashboard & analytics — account stats, revenue summary, revenue/license charts, sales reports (summary, trend, breakdown), usage analytics (downloads, domains, activations), per-product reports, feature-usage analytics, SDK connection status
• Releases — list, signed download URLs
• Plans — list
• Webhooks — list, get, delivery log (incl. full request/response capture)
• Payments — list, get
• Subscriptions — list
• Exports — CSV export of licenses, customers, payments, sales, and per-product data (preview inline or save to a local file)
• Events & logs — SDK/event feed, event analytics, audit logs
• Feedback — list, stats, tags
• Notifications — list with unread count
• Tickets — list, get with full thread
• Portal — settings, blocked-customer list

Write (hidden when PACKEDGE_READONLY is set)

• Products — create, update, archive
• Licenses — issue, update, revoke, bulk actions (revoke / suspend / activate / extend), delete
• Customers — create, update, delete, bulk delete
• Sites — deactivate, bulk deactivate
• Releases — inspect a local zip, upload + create, update, publish, set stable / roll back, delete
• Plans — create, update, sync to Stripe/Polar, delete
• Webhooks — create, update, regenerate secret, test, redeliver, delete
• Payments — record manual orders (issues the license too)
• Subscriptions — record manual subscriptions, cancel, bulk cancel
• Feedback — create/update/delete tags, assign/unassign tags
• Notifications — mark read
• Tickets — open, reply, close
• Portal — update settings, block/unblock customers

Write actions are marked so well-behaved agents ask you to confirm before running them. Destructive ones (deletes, revokes, secret regeneration) are flagged extra-loudly. To revoke a license, prefer the dedicated revoke tool — it also busts the edge validation cache and fires the license.revoked webhook.

Example prompts

• "Upload ~/dist/my-plugin-1.4.0.zip as version 1.4.0 and publish it."
• "Test my Slack webhook and show its recent deliveries."
• "Export all licenses to CSV and save them to /tmp/licenses.csv."
• "How are sales trending this month? Who are my top customers?"
• "Issue a 3-seat license for product prd_abc to [email protected] expiring next year."
• "Which features of my plugin were used most in the last 30 days?"

Notes & limits

• The Developer API is rate-limited (see Rate Limits); the server retries transient 429s automatically.
• Some operations are plan-gated on the PackEdge side (releases/webhooks need a paid plan; advanced analytics and product exports need Pro+; audit logs need Business). Gated calls return a clear upgrade message.
• Release uploads accept local .zip files up to 100 MB.
• The package is open source in the PackEdge repository under packages/mcp.