Jot MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOT_API_TOKEN | Yes | Your agent token, created from Settings → Agents in Jot. A token sees one project and nothing else and can be revoked at any time. | |
| BACKEND_API_URL | No | The Jot API to talk to. Change it only if you self-host Jot. | https://api.usejot.co |
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 |
|---|---|
| fetch_feedbackA | List feedback comments for a project. Filter by status to find work to do. Public visitor feedback is left out unless |
| get_commentA | Full detail for one comment: the repro context, the thread, and — when a session was recorded — a text timeline of what happened, since an agent cannot watch a replay. |
| update_statusA | Move a comment to IN_PROGRESS or RESOLVED. Agents cannot approve — only the person who reported a problem can confirm it is fixed. |
| post_replyB | Add a note to a comment thread so the reporter can see what happened, e.g. 'Fixed in PR #204'. |
| create_batch_noteA | Report one action that spanned several comments (e.g. 'resolved 3 comments in PR #204') as a single note, linked across every thread it names. Atomic: one unknown id and nothing is posted. |
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 5 tools
Each tool has a clearly distinct purpose: listing feedback versus retrieving one comment, changing status versus adding a reply, and posting a single reply versus a batch note across threads. The descriptions explicitly distinguish single-thread and multi-thread actions, so misselection is unlikely.
All tool names follow a consistent snake_case verb_noun pattern: get_comment, fetch_feedback, update_status, post_reply, create_batch_note. The verbs are varied but appropriate, and the structure is predictable throughout.
Five tools is well-scoped for a feedback/comment management server. Each tool earns its place by covering a distinct part of the agent workflow without redundancy.
The surface covers listing, reading, updating, replying, and batch-noting feedback comments, which handles the core agent workflow. Minor gaps exist, such as no bulk status update or edit/delete operation for replies, but these are workable around.