kweenkl-mcp
Server Details
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- antoinedelorme/kweenkl-mcp
- GitHub Stars
- 0
- Server Listing
- kweenkl MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 6 of 6 tools scored.
Each tool has a clearly distinct purpose: fetch retrieves specific details, kweenkl sends notifications, kweenkl_login starts authentication, kweenkl_login_check checks auth status, kweenkl_status checks server health, and search finds channels and messages. No overlap in functionality.
Tool names mix generic verbs (fetch, search) with a 'kweenkl_' prefix strategy (kweenkl, kweenkl_login, etc.). While all use lowercase and underscores, the pattern is inconsistent, making it harder to predict tool names.
With 6 tools, the set is well-scoped for a notification service. It covers essential operations without being too sparse or bloated.
The tool set covers the core notification lifecycle: sending, retrieving details, searching, authentication, and status checking. Minor gaps like updating or deleting notifications exist but are not critical for basic usage.
Available Tools
6 toolsfetchRead-onlyIdempotentInspect
Fetch details about a specific kweenkl channel or notification by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the channel or notification to fetch | |
| type | Yes | Type of resource to fetch: 'channel' or 'notification' |
kweenklInspect
Send a push notification using kweenkl. The verb 'kweenkl' means to send a notification. Use this to notify users about important events, updates, or information that requires immediate attention.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Optional title for the notification. Should be brief (max 50 chars recommended). If omitted, only the message will be shown. | |
| glance | No | Optional structured visualization rendered as a card inside the kweenkl iOS app. Must include a 'type' field. v1 supports type='line_chart' with required fields {labels: string[], values: number[]} (same length, ≥2 points) and optional fields {subtitle, accent (#hex), comment, x_label, y_label}. Example: {type:'line_chart', subtitle:'Évolution 2015→2024', labels:['2015','2016','2017'], values:[670,720,780], accent:'#ff6b6b', comment:'tendance haussière'} | |
| message | Yes | The notification message content. Should be clear, concise, and actionable. Maximum recommended length: 500 characters for optimal mobile display. | |
| payload | No | Optional custom JSON payload for additional metadata. Can include any structured data that your app might process (e.g., action buttons, deep links, custom data). | |
| priority | No | Priority level for the notification. 'high' = urgent/critical alerts, 'normal' = standard updates (default), 'low' = non-urgent information. | |
| webhook_token | Yes | The webhook token for your kweenkl channel. Format: UUID-like string. Can be found in the kweenkl iOS app by opening a channel and viewing 'Channel Info'. |
kweenkl_loginInspect
Start the kweenkl login/onboarding flow. If the user provides their device_token (from the iOS app), this will immediately create their webhook. Otherwise, guides them to download the app or join the waitlist.
| Name | Required | Description | Default |
|---|---|---|---|
| No | User's email address for waitlist subscription (only used if has_app is false) | ||
| has_app | No | Whether the user already has the kweenkl iOS app installed. If true and no device_token, starts device auth flow. | |
| device_token | No | The user's device token from the kweenkl iOS app. If provided, immediately creates a webhook for them. |
kweenkl_login_checkRead-onlyIdempotentInspect
Check the status of a device authorization flow. Call this after kweenkl_login to see if the user has approved the connection in their iOS app.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The session ID returned from kweenkl_login |
kweenkl_statusRead-onlyIdempotentInspect
Check kweenkl server connectivity and status. Use this to verify the connection is working before sending notifications. No authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
searchRead-onlyIdempotentInspect
Search kweenkl notification channels and messages. Use this to find channels by name or search through notification history.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query to find channels or notifications |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.