loupe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOUPE_API | Yes | Base URL of the Loupe API server | |
| LOUPE_ADMIN_KEY | Yes | Admin secret key for authentication | |
| LOUPE_PROJECT_KEY | Yes | Project key for the Loupe project |
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_commentsA | List Loupe product-feedback comments for the project as a task backlog. Use this to see what a PM has flagged, then work through the items. |
| get_commentA | Get the full context for one comment: the request, the page, the target element's HTML, and its computed styles — everything needed to make the change. |
| update_statusA | Update a comment's status. Set to in_progress when you start it and done when the change is shipped — this closes the loop back to the PM. |
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
Each tool targets a distinct operation: retrieving a single comment's full context, listing all comments, and updating a comment's status. There is no functional overlap.
All tool names follow a consistent verb_noun pattern with snake_case: get_comment, list_comments, update_status. Singular/plural usage is correct for each operation.
Three tools is slightly low but appropriate for a focused server that handles comment viewing and status management. The set is concise without being insufficient.
The tools cover listing, detail retrieval, and status updates, which are core for working through feedback. However, creation and deletion of comments are absent, leaving notable lifecycle gaps.