katyayani-core-mcp

MCP server for Katyayani Core (Customer Engagement Platform). Add it to Claude / Cursor / any MCP client and ask anything about the platform — live data and how the SDKs work.

What you can ask

• Live data (needs a token): "How many installs from google-play last 30 days?", "Top referrers", "Revenue by source", "Show the acquisition funnel", "Find user 6261414316".
• How-to / docs (no token needed): "How do I add referral sharing?", "How to set user attributes?", "What does trackAttribution do?", "How to install the Flutter SDK?", "Does the RN SDK auto-ask push permission?"

Tools

| Tool | Purpose | |------|---------| | kc_docs | Platform + SDK knowledge (install, identify/attributes, events, attribution, referral, push). Works with no token. | | kc_get | Read live dashboard data (users, attribution, revenue, referrals, funnels…). Needs KC_TOKEN. | | kc_action | Write actions (create smart link, send message…). Needs KC_TOKEN. |

Install (Claude Code)

claude mcp add katyayani-core \
  -e KC_TOKEN=<shared-token> \
  -e KC_TENANT_ID=<project-tenant-id> \
  -- npx -y katyayani-core-mcp

• KC_TOKEN — the shared access token (ask whoever gave you this MCP). Omit it and only kc_docs works.
• KC_TENANT_ID (optional) — scopes all data to one project. Omit → the API's default project.
• KC_API_BASE (optional) — defaults to https://8.231.80.238.nip.io.

Cursor / other clients (mcp.json)

{
  "mcpServers": {
    "katyayani-core": {
      "command": "npx",
      "args": ["-y", "katyayani-core-mcp"],
      "env": { "KC_TOKEN": "<shared-token>", "KC_TENANT_ID": "<tenant-id>" }
    }
  }
}

Security

KC_TOKEN is a full-access dashboard token — share it only with people you trust. It is never baked into this package; it is read from your MCP config at runtime. kc_docs needs no token, so you can share the docs experience openly.

License

MIT