@zappush/mcp

MCP server for Unrestrict — manage your store, compliant pages, routes, analytics, and Meta integrations through Claude.

Setup

1. Get your MCP key

Go to Settings > MCP Access in the Unrestrict dashboard and generate an API key. It starts with zp_mcp_. You'll only see the full key once — copy it.

2. Install

npm install -g @zappush/mcp

3. Configure Claude

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "unrestrict": {
      "command": "npx",
      "args": ["-y", "@zappush/mcp"],
      "env": {
        "ZAPPUSH_API_KEY": "zp_mcp_your_key_here"
      }
    }
  }
}

Or for Claude Code (.claude/settings.json):

{
  "mcpServers": {
    "unrestrict": {
      "command": "npx",
      "args": ["-y", "@zappush/mcp"],
      "env": {
        "ZAPPUSH_API_KEY": "zp_mcp_your_key_here"
      }
    }
  }
}

Environment variables

| Variable | Required | Description | |----------|----------|-------------| | ZAPPUSH_API_KEY | Yes | Your MCP key (zp_mcp_...) | | ZAPPUSH_API_URL | No | API base URL (defaults to https://unrestrict-api-user.zappush.com) |

Tools

Store & Analytics

| Tool | Description | |------|-------------| | get_store_info | Store name, URL, platform, plan, onboarding status, page/route counts | | get_analytics | Funnel metrics, revenue, conversion rates for a date range | | get_shoppers | Search shoppers by email, phone, or name with pagination |

Compliant Pages

| Tool | Description | |------|-------------| | get_landing_page | Get page config and all file contents (HTML, CSS, JS) | | update_landing_page | Replace all files and deploy to production (atomic batch) | | rollback_landing_page | List recent releases or rollback to a specific version |

Routes

| Tool | Description | |------|-------------| | list_routes | List all routes (marketing funnels) for the store | | create_route | Create a new route linking a compliant page to a destination | | update_route | Update route label, destination, page, integration, or status | | delete_route | Delete a route (soft-delete if it has existing sessions) |

Onboarding

| Tool | Description | |------|-------------| | create_store | Create a new store with default integrations and route | | create_compliant_page | Deploy a compliant page to a custom domain, returns DNS records | | check_domain | Check DNS verification status and trigger verification | | connect_meta | Connect Meta Conversions API with pixel ID and access token |

Multi-store

If you have access to multiple stores, pass store_id to any tool. Omit it to use your default store.

Releasing

Every push to main automatically publishes a new patch version to npm via GitHub Actions.

# Make your changes, then:
git add -A && git commit -m "your message"
git push

The workflow bumps the patch version and publishes. Check progress at Actions.

To publish manually:

bun install && bun run build
npm version patch --no-git-tag-version
npm publish --access public

License

MIT