Integration

Ybug integration

Ybug is a visual bug-reporting and website feedback tool. Read and manage teams, projects, feedback items (status, priority, assignee, tags), feedback comments and public replies, team tags, status workflows and project webhooks for new feedback. The REST API is limited to Ybug Company and Enterprise plans, with a rate limit of 100 requests per minute per client. Authentication is a personal API token generated in the Ybug dashboard (Profile settings, API, Generate token; it is shown only once), sent as a Bearer token in the Authorization header.

Connect Ybug How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ybug.Built from the 31 Ybug tools below, on the connection you add once.

What you can do with Ybug

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Tag, 7 operations

add_feedback_tagsAdd feedback tagsPOSTAdds the provided tags to the feedback item without removing existing ones. Tag names that do not yet exist are auto-created at the team level. Tags already present are ignored.
create_tagCreate tagPOSTCreates a new tag in the team. The tag name must be unique within the team.
delete_tagDelete tagDELETEPermanently removes the tag. Any feedback associations are also removed.
get_tagGet tagGETRetrieves details for a specific tag.
list_tagsList tagsGETReturns all tags in the team.
remove_feedback_tagRemove feedback tagDELETERemoves the specified tag from the feedback item. If the tag is not currently assigned, the operation is a no-op.
update_tagUpdate tagPATCHRenames an existing tag. The new name must be unique within the owning team.

Project, 6 operations

create_projectCreate projectPOSTCreates a project in a team from a name and returns the new project, including its id.
delete_projectDelete projectDELETEPermanently removes the specified project. Only projects the token can manage may be deleted.
get_projectGet projectGETFetches full details for the specified project, including identifiers, status, and timestamps.
list_projectsList projectsGETRetrieves a paginated list of projects available to the API token across all teams. Use the `archived` query parameter to switch between active and archived projects.
list_team_projectsList team projectsGETRetrieves a paginated collection of projects within the specified team that the token may access. Supports toggling archived projects with the `archived` query parameter.
update_projectUpdate projectPATCHUpdates editable fields on the project, such as the name or archived status. Send only the attributes that should change.

Comment, 4 operations

create_feedback_commentCreate feedback commentPOSTAdds a comment to a feedback item, authored by the token's user. It is a private team note unless internal is false, which makes it a public reply that notifies the reporter. The body is at most 500 characters.
delete_commentDelete commentDELETEDeletes the specified comment.
list_feedback_commentsList feedback commentsGETReturns a paginated list of non-deleted comments on the specified feedback item. Supports ordering by `created_at`.
update_commentUpdate commentPATCHUpdates the text of an internal (private) comment. Public replies cannot be edited, returns 400 if attempted.

Feedback, 4 operations

delete_feedbackDelete feedbackDELETEPermanently removes the feedback record. Linked assets and references are also cleared.
get_feedbackGet feedbackGETRetrieves the full feedback record, including metadata, reporter context, and any associated assets.
list_project_feedbackList project feedbackGETLists a project's feedback items, paginated (page, page_size up to 100), oldest first unless order_by is set. Filter with tag[], assignee[] and status[] (values within one filter are combined with OR).
update_feedbackUpdate feedbackPATCHUpdates a feedback item; send only the fields to change (at least one): status_id (from list_project_statuses), priority_id, type_id, assignee_id (from list_project_members), title or description. Returns the updated item.

Hook, 4 operations

create_project_hookCreate project hookPOSTSubscribes an HTTPS url to a project's feedback.created event (one webhook per event per project, else 409). With a secret, deliveries are signed in an X-Ybug-Signature header (see secret); the secret is never returned.
delete_project_hookDelete project hookDELETERemoves the specified webhook subscription from the project. After deletion, no further events are sent to the target URL.
get_project_hookGet project hookGETRetrieves configuration details for a specific webhook on the project, including the target URL and activation state.
list_project_hooksList project hooksGETReturns all webhook subscriptions configured for the project, allowing clients to inspect existing destinations and statuses.

Status, 2 operations

list_project_statusesList project statusesGETLists the statuses valid for feedback in this project, ordered by position: exactly the status_id values update_feedback accepts. Same list as list_team_statuses (statuses hidden from the board are still listed).
list_team_statusesList team statusesGETLists the team's whole feedback status workflow, ordered by position. Every status is valid in every project of the team. Status ids are per team, so a status id only means something together with its team.

Me, 1 operation

get_meGet meGETReturns the profile information for the user associated with the API token, including basic identity fields and timestamps.

Member, 1 operation

list_project_membersList project membersGETReturns the list of project members. These users can be used for feedback assignment.

Team, 1 operation

list_teamsList teamsGETLists every team accessible to the current API token, reflecting the user’s membership and plan entitlements.

Test, 1 operation

test_project_hookTest project hookPOSTQueues a synthetic feedback.created event to the webhook's target url, to check that the receiving endpoint is reachable and handles the payload.

Use Ybug from Claude Code, Cursor or Codex

Connect Ybug in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ybug operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Ybug

Create your workspace
Sign up free. Nothing to install.
Connect Ybug once
Add your Ybug connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.