@jabee/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JABEE_API_KEY | Yes | Your Jabee API key. Create one under Management, then Approvals, at app.jabee.ai. It starts with `jak_`. | |
| JABEE_PERMISSION_EXPIRY_MINUTES | No | Permission request expiry in minutes for the Claude Code channel. Defaults to 15, with a floor of 5. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_personA | Ask a named person to approve, reject or amend something, on WhatsApp, and wait for their answer. Use this before doing anything that is expensive or impossible to undo: issuing a refund, sending a quote, posting publicly, emailing a list, deleting data. The person gets buttons on their phone and can also reply with free text to amend what you proposed. Returns their decision, or the request id if nobody has answered yet. |
| check_approvalA | Read the current state of a request you asked earlier, by its id. Use this when ask_person returned while still pending. |
| tell_personA | Send a one-way notification to your own phone on WhatsApp: a build failed, an order shipped, a job finished. This reaches your own verified people, never your customers. Returns once it has been sent; it does not wait for a reply. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: ask_person initiates a blocking human approval, check_approval polls an existing request, and tell_person sends a one-way notification. The descriptions make the waiting/blocking versus notification-only distinction explicit.
All tool names follow a consistent snake_case verb_noun pattern: check_approval, ask_person, tell_person. There are no mixed conventions or vague standalone verbs.
Three tools are well-scoped for a focused human-in-the-loop WhatsApp approval/notification server. Each tool earns its place: initiate approval, check pending approval, and send non-blocking notification.
The core approval lifecycle is covered: create a request, poll its state, and notify without waiting. Minor gaps exist around listing all pending approvals or canceling/revoking a request, but these are not fatal for the stated workflow.