@promptjang/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPTJANG_API_KEY | Yes | PromptJang API key (pj_live_...) required to authenticate with the PromptJang platform |
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 |
|---|---|
| list_targetsA | List registered PromptJang webhook, mailbox, and A2A targets available to this API key. Call this before send_event; this tool never creates or changes targets. |
| list_mailboxesA | List durable agent mailboxes available to this API key. Returns registered mailbox IDs for list_unread and send_event. |
| list_unreadA | List unread messages in one registered PromptJang mailbox without claiming or changing them. |
| get_messageA | Read one mailbox message and its JSON payload without claiming or acknowledging it. |
| claim_messageA | Atomically claim one unread mailbox message for five minutes. The same PromptJang API key must acknowledge it after processing. |
| ack_messageA | Acknowledge a claimed mailbox message after successful processing. Only the API key that owns the active claim can acknowledge it. |
| send_eventA | Accept one JSON item for a registered webhook, mailbox, or A2A target. Requires target_id from list_targets and never accepts an arbitrary URL. Set idempotency_key when repeating the same logical item. |
| get_eventA | Read one PromptJang event and its delivery attempts by event ID. Use this to inspect current state, response codes, timing, retry count, and the last delivery error. |
| replay_eventA | Create a non-billable replay of an existing PromptJang event using its stored payload and registered target. Returns the new replay event ID. This changes delivery state but does not delete or overwrite the source event. |
| get_usageA | Read the current calendar-month accepted-item count, estimated USD charge, and pending meter-event count. Retries and replays are excluded. During the billing-disabled founder beta, usage remains local and exempt workspaces report a zero charge estimate. |
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 10 tools
Each tool targets a distinct resource or action, and the descriptions make the boundaries clear. The only mild overlap is between list_targets and list_mailboxes, since mailbox targets and durable mailboxes are related, but the descriptions differentiate them well.
Tool names consistently follow a verb_noun snake_case pattern: list_*, get_*, claim_*, ack_*, send_*, replay_*. This makes the set highly predictable and easy to navigate.
Ten tools is well-scoped for an event, mailbox, and usage monitoring server. Each tool serves a clear purpose without redundancy or bloat.
The core lifecycle is covered: send events, inspect delivery, replay failed events, list/read/claim/acknowledge mailbox messages, and check usage. A minorgap is the lack of a list-events endpoint to browse past events without knowing their IDs, but agents can work around this.