@triagly/mcp

MCP (Model Context Protocol) server for Triagly. Lets Claude Desktop, Cursor, Claude Code, and any MCP-compatible AI agent query and act on your Triagly feedback data natively.

Once installed, an agent can ask "what are the top 5 critical bugs in my project?" and get a real answer from your feedback data.

Setup

Authentication

Set two environment variables — no separate login flow required:

TRIAGLY_API_KEY=tsk_live_...
TRIAGLY_PROJECT_ID=<your-project-uuid>

Get your API key from Settings → API in the Triagly dashboard.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "triagly": {
      "command": "npx",
      "args": ["-y", "@triagly/mcp"],
      "env": {
        "TRIAGLY_API_KEY": "tsk_live_...",
        "TRIAGLY_PROJECT_ID": "your-project-uuid"
      }
    }
  }
}

Cursor

Use the same config format in Cursor's MCP settings.

Claude Code

Add to your project's .claude/settings.json or global ~/.claude/settings.json:

{
  "mcpServers": {
    "triagly": {
      "command": "npx",
      "args": ["-y", "@triagly/mcp"],
      "env": {
        "TRIAGLY_API_KEY": "tsk_live_...",
        "TRIAGLY_PROJECT_ID": "your-project-uuid"
      }
    }
  }
}

Tools

Read tools (feedback:read scope)

| Tool | Description | |------|-------------| | list_feedback | List feedback with filters (status, classification, severity, tags, date range, etc.) | | get_feedback | Fetch a single item by ID with full AI analysis | | search_feedback | Semantic search using natural language | | get_stats | Aggregate stats: totals by status, classification, sentiment, top tags |

Write tools (feedback:write scope)

Write tools are only registered when your API key has feedback:write scope — they won't appear in the tool list otherwise.

| Tool | Description | |------|-------------| | update_feedback | Update status, tags, or assignment for one item | | bulk_update_feedback | Update up to 100 items at once |

Resources

| Resource URI | Description | |-------------|-------------| | triagly://feedback/recent | Last 20 open items (sorted by priority). Load as context. | | triagly://stats/summary | Current project stats as structured text |

Prompts

| Prompt | Description | |--------|-------------| | triage_session | Review critical/high feedback, identify top issues and duplicates | | weekly_review | Summarize this week's feedback, trends, and improvements |

Scope-aware registration

On startup, the server verifies your API key and detects its scopes. Write tools are only registered if feedback:write scope is present. This prevents confusing permission errors — the tool simply doesn't appear in the list.

Environment variables

| Variable | Required | Description | |----------|----------|-------------| | TRIAGLY_API_KEY | Yes | API key from /settings/api | | TRIAGLY_PROJECT_ID | Yes | Project UUID to query | | TRIAGLY_BASE_URL | No | Override API base URL (for self-hosted or local dev) |