KW
OfficialAPI Integration

Kweenkl MCP Server: Natural Language Push Notifications

Send natural-language push notifications from AI assistants using the MCP server—try the pre-launch demo with an example webhook token.

View on GitHub
Quick Install
npx -y @antoinedelorme/kweenkl-mcp

Overview

Kweenkl MCP Server lets AI assistants send natural-language push notifications to the Kweenkl mobile app via the Model Context Protocol (MCP). Instead of building a custom push pipeline, an assistant can call the MCP endpoint and deliver human-readable notifications (reminders, alerts, confirmations) directly to a registered device token. The original local MCP server has been deprecated — a hosted endpoint is available so you can integrate without installing or maintaining infrastructure.

This guide is aimed at developers new to MCP-style integrations. It shows how to connect an AI client (Claude, ChatGPT or any MCP-enabled tool) to the hosted Kweenkl MCP endpoint, how to test with a demo token, and where to find the full API reference.

Features

  • Send natural-language push notifications from AI assistants
  • Simple, hosted MCP endpoint (no server install required)
  • Authentication via a single device token header (X-Kweenkl-Device-Token)
  • Works with any MCP-capable client (Claude, ChatGPT Apps & Connectors, custom MCP clients)
  • Pre-launch demo token support for quick testing
  • Full API reference available on the Kweenkl docs site

Installation / Configuration

No server install is required for the hosted service. Integration consists of adding the MCP endpoint to your AI client and supplying your device token.

  1. Install the Kweenkl iOS app (TestFlight) and copy your Device Token from Settings.

    • TestFlight: https://testflight.apple.com/join/achwt8Jt

  2. Add the MCP endpoint to your AI client:

  • Claude (example)
claude mcp add kweenkl https://api.kweenkl.com/mcp --transport http --scope user --header "X-Kweenkl-Device-Token: YOUR_DEVICE_TOKEN"

  • ChatGPT (Apps & Connectors)

    • Go to Settings > Apps & Connectors
    • Add the MCP endpoint: https://api.kweenkl.com/mcp
    • During setup, provide your device token when prompted

  • Any MCP client (manual)

    • Point the client at: https://api.kweenkl.com/mcp
    • Set header: X-Kweenkl-Device-Token: YOUR_DEVICE_TOKEN

Replace YOUR_DEVICE_TOKEN with the value copied from the Kweenkl app.

Example Requests

Minimal curl example to send a push-style notification. Replace DEMO_TOKEN with your device token (or use the demo token below for a quick test).

curl -X POST "https://api.kweenkl.com/mcp" \
  -H "Content-Type: application/json" \
  -H "X-Kweenkl-Device-Token: DEMO_TOKEN" \
  -d '{
    "type": "push",
    "title": "Stand-up Reminder",
    "body": "Daily stand-up in 10 minutes — join via Zoom: https://zoom.us/j/..."
  }'

Pre-launch demo token (example)

  • DEMO_TOKEN: demo_token_12345
  • Note: demo tokens are for quick testing only. Replace with your actual device token for production use.

For the complete request schema and available fields (actions, deep links, attachments), see the full docs listed in Available Resources.

Available Resources

  • GitHub repository (server source / deprecated): https://github.com/antoinedelorme/kweenkl-mcp
  • Hosted MCP endpoint: https://api.kweenkl.com/mcp
  • Full API reference / skill documentation: https://kweenkl.com/skill.md
  • Kweenkl website: https://kweenkl.com
  • iOS app (TestFlight): https://testflight.apple.com/join/achwt8Jt

Use Cases

  • Personal reminders: An assistant can generate and push human-friendly reminders (e.g., “Take out the trash at 7 PM”).
  • Calendar nudges: When an assistant detects a meeting change, it can push a concise natural-language summary to the user’s device.
  • Approval workflows: Send a push asking the user to confirm or reject an action (accept/decline buttons can be modeled via the docs’ actionable fields).
  • Device/IoT alerts: AI-generated summaries of sensor events or status changes delivered as readable notifications.
  • Emergency notices: Critical messages that need attention with optional deep links to relevant app screens.

Each of these flows benefits from letting the model craft the exact wording, tone, and contextual detail of the notification.

Notes and License

  • The original local MCP server code on GitHub is deprecated in favor of the hosted endpoint at https://api.kweenkl.com/mcp.
  • Consult https://kweenkl.com/skill.md for the authoritative API specification and actionable fields.
  • License: MIT (see repository for details)

If you’re integrating an MCP client for the first time, start by adding the endpoint and testing with a demo token, then swap in your app’s Device Token for production notifications.

Tags:api-integration