Skip to main content
Glama
TomPhillipsLabs

loopquest-mcp

README.md
# loopquest-mcp

A [Model Context Protocol](https://modelcontextprotocol.io) server for [LoopQuest](https://loopquest.tomphillips.uk). Lets any MCP-capable agent (Claude Desktop, Cursor, Windsurf, custom agents) send its output for gamified **human-in-the-loop review** and get a verdict back.

## Tools

- **create_review_task** — send content for a human to approve or flag. Returns a task id; the verdict arrives via webhook (`callback_url`) or `get_task_status`.
- **get_task_status** — check a task's status / verdict.

## Configure

Set `LOOPQUEST_API_KEY` (Workspaces → API keys). Optionally `LOOPQUEST_BASE_URL` for a self-hosted deployment.

### Claude Desktop

In `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "loopquest": {
      "command": "npx",
      "args": ["-y", "loopquest-mcp"],
      "env": { "LOOPQUEST_API_KEY": "lq_your_key" }
    }
  }
}
```

Cursor / Windsurf use the same `command` / `args` / `env` shape in their MCP settings.

## Develop

```bash
npm install
npm test          # unit tests
npm run build     # tsc -> dist/
node dist/index.js
```

## License

MIT

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: one creates a review task, the other checks its status. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern in snake_case: create_review_task and get_task_status.

Tool Count4/5

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.

Completeness3/5

The tool surface covers creation and status polling, but lacks operations like canceling or listing tasks, which could be needed in real workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues