LabscoMCP early access ↗
BugHerdMCP SERVER · OFFICIAL PROJECT

BugHerd Website Feedback

Reads and files BugHerd tasks — assignees, tags, attachments — with per-client tokens you can revoke from settings.

by BugHerd ↗Project & Task Management✓ Official

LABSCO SUMMARY

Per-client tokens you can see and revoke is the governance detail most vendors skip.

When three different assistants are connected to the same account, one revoke-all switch is a blunt instrument. Listing tokens per client means you can cut off the one that misbehaved and leave the rest working. On the tools themselves: upload happens through generated URLs rather than by posting bytes through the server, which keeps large attachments out of the model's context entirely.

What it is

BugHerd's endpoint over their website feedback and bug-tracking product. Nineteen tools cover projects, tasks and the assets attached to them, and the documentation notes the set may grow.

What you get

  • Projects: list, read details, create, update settings, manage tracked site URLs
  • Tasks: list yours, list across projects, read one in full, create, update, comment
  • Task metadata: assignees, tags
  • Attachments and project assets, through generated secure upload URLs

Requirements

A BugHerd account. Your client signs in over OAuth and you choose which organization it can reach. Each client gets its own token, and you can list or revoke them under Settings → MCP Access Tokens.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen