loopquest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOOPQUEST_API_KEY | Yes | Your LoopQuest API key | |
| LOOPQUEST_BASE_URL | No | Base URL for a self-hosted LoopQuest deployment |
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 |
|---|---|
| create_review_taskA | Send content to LoopQuest for a human to review. Use mode=gate to BLOCK until a human approves (poll get_task_status for the verdict before acting), or mode=monitor to review in the background. Returns the task id, status and expiry. |
| get_task_statusA | Check the status and verdict of a LoopQuest review task by id. |
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 2 tools
Each tool has a clearly distinct purpose: one creates a review task, the other checks its status. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern in snake_case: create_review_task and get_task_status.
With only 2 tools, the server is lightly scoped but still covers the core review workflow. The count is slightly low but acceptable for a focused utility.
The tool surface covers creation and status polling, but lacks operations like canceling or listing tasks, which could be needed in real workflows.