Jeero MCP

Jeero MCP is a local Model Context Protocol server for Jeero subscriptions and event data. It synchronizes with Mother and keeps its local event cache in SQLite; it does not require WordPress or a hosted MCP service.

Install

Use Node.js 20 or later and configure your MCP client to run the published package:

{
  "mcpServers": {
    "jeero": {
      "command": "npx",
      "args": ["-y", "jeero-mcp"]
    }
  }
}

The server communicates over stdio. Do not write application logs to stdout.

Related MCP server: tg-mcp-spy

First use

Create a subscription with create_subscription. Mother first returns its Ticketing solution field; set that value with config_subscription, which returns the connector-specific fields. Send those completed settings through config_subscription. One subscription can be the default; tools use it when subscription is omitted. Multiple active subscriptions are supported.

get_events synchronizes the selected subscriptions at most once a minute. While the server is running, active subscriptions are also checked every minute. Use sync_subscription or sync_subscriptions with force: true when an immediate refresh is needed.

Tools

• Subscription management: list_subscriptions, create_subscription, get_subscription, config_subscription, set_default_subscription, activate_subscription, deactivate_subscription

• Synchronization: sync_subscription, sync_subscriptions

• Event data: get_events, get_event, list_event_categories, get_ticket_snapshots, get_logs

Local data and configuration

By default Jeero MCP stores its SQLite cache and persistent site identity in ~/.jeero-mcp/. Keep that directory private: the identity is used for Mother requests.

Mother remains the upstream source of truth. Jeero MCP stores processed event records and synchronization state, not raw inbox payloads.

Development

npm install
npm test
npm pack --dry-run

The tag-based publish workflow requires an explicit repository release approval before a version tag can publish.

License

MIT