MCP Tools
Reference for all Loop MCP tools available in any MCP-compatible AI tool.
The Loop MCP server exposes fourteen tools that your AI assistant can call. You do not invoke these directly — your AI tool uses them automatically when you ask questions about your feedback, tickets, or boards.
list_projects
List all projects in your organisation.
Parameters: None
Example prompt:
"Show me all my Loop projects"
Returns: Array of projects with id, name, url, type, and created_at.
list_feedback
Browse raw feedback items with optional filters.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | No | Filter by project ID |
status | enum | No | new, in_progress, review, done |
type | enum | No | bug, feature, general |
limit | number | No | Max results (1–100, default 50) |
Example prompts:
"Show me new bug reports for the Marketing Site project"
"What feedback have we received this week?"
Returns: Array of feedback items with total count.
update_feedback
Update a feedback item's status, title, description, or type. Use this to move feedback between status columns on website-type projects.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
feedback_id | string | Yes | The feedback item ID to update |
status | enum | No | new, in_progress, review, done |
title | string | No | New title |
description | string | No | New description |
type | enum | No | bug, feature, general |
Example prompts:
"Move feedback fb-001 to in progress"
"Mark that Safari button bug as done"
"Change feedback fb-042 from general to bug"
Returns: Updated feedback object.
list_tickets
List AI-generated developer tickets.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | No | Filter by project ID |
status | enum | No | open, in_progress, done |
limit | number | No | Max results (1–100, default 50) |
Example prompt:
"Show me open dev tickets for this project"
Returns: Array of tickets with total count.
get_ticket
Get full details of a specific developer ticket.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
ticket_id | string | Yes | The ticket ID |
Example prompt:
"Show me the details of ticket abc-123"
Returns: Complete ticket object with description, priority, labels, and AI context.
update_ticket
Update a developer ticket's fields.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
ticket_id | string | Yes | The ticket ID to update |
status | enum | No | open, in_progress, done |
priority | enum | No | low, medium, high, critical |
title | string | No | New title |
description | string | No | New description (markdown) |
labels | string[] | No | New labels array |
Example prompts:
"Mark ticket abc-123 as in progress"
"Update the priority of ticket abc-123 to critical"
Returns: Updated ticket object.
generate_ticket
Use AI to create a structured developer ticket from a feedback item or board card. This analyses the source content, including all comments, and generates a ticket with:
- A clear technical title
- Structured description with acceptance criteria
- Priority assessment
- Relevant labels
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
source_type | enum | Yes | feedback or board_card |
source_id | string | Yes | ID of the source item |
Example prompts:
"Generate a dev ticket from feedback item fb-001"
"Create a ticket from the board card about dark mode"
Returns: Newly created ticket object.
list_comments
List all comments on a feedback item, ordered by creation date.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
feedback_id | string | Yes | The feedback item ID |
Example prompts:
"Show me the comments on feedback fb-001"
"What's the conversation around feedback item fb-042?"
Returns: Array of comments with id, feedback_id, user_id, content, author, and created_at.
add_comment
Add a comment to a feedback item. Supports @mentions — include @DisplayName in the content to tag team members. Tagged users will receive a notification.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
feedback_id | string | Yes | The feedback item ID to comment on |
content | string | Yes | Comment text. Use @DisplayName to mention team members |
Example prompts:
"Reply to feedback fb-001 saying we're investigating the issue"
"Comment on fb-042 and tag @Alex Johnson to take a look"
"Add a comment to feedback fb-007: '@Sam Lee this is fixed in the latest deploy'"
Returns: The newly created comment object.
list_team_members
List team members who have access to a project. Use this to discover display names for @mentions in comments.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | The project ID |
Example prompts:
"Who has access to the Marketing Site project?"
"List team members for project abc-123 so I can tag the right person"
Returns: Array of members with user_id, display_name, email, and role.
list_board_lists
List all lists (columns) on a board project, ordered by position. Use this to discover list IDs when moving cards between columns.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | The board project ID |
Example prompts:
"Show me the columns on the Sprint Board"
"What lists does board project proj-002 have?"
Returns: Array of lists with id, project_id, name, position, and created_at.
list_board_cards
List cards on a board with optional filters.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | No | Filter by board project ID |
list_id | string | No | Filter by list/column ID |
limit | number | No | Max results (1–100, default 50) |
Example prompts:
"Show me all cards in the To Do column"
"What cards are on the Sprint Board?"
Returns: Array of cards with total count.
create_card
Create a new card on a board project. The card is appended to the end of the target list. Use list_board_lists first to find valid list IDs for the target column.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | The board project ID to create the card in |
list_id | string | Yes | The list/column ID to place the card in |
title | string | Yes | Card title |
description | string | No | Card description (markdown) |
labels | array | No | Labels — [{"color": "#8B5CF6", "text": "feature"}] |
author_name | string | No | Author name to display on the card |
Example prompts:
"Add a card to the To Do column for fixing the mobile header"
"Create a new card on the Sprint Board for the dark mode feature"
"Add a bug card to the Backlog column: login page crashes on Safari"
Returns: The newly created card object.
update_card
Update a board card's fields or move it to a different list (column).
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
card_id | string | Yes | The card ID to update |
title | string | No | New title |
description | string | No | New description (markdown) |
labels | array | No | Updated labels — [{"color": "#8B5CF6", "text": "feature"}] |
due_date | string | null | No | New due date (ISO format) or null to clear |
checklist | array | No | Updated checklist — [{"id": "1", "text": "Task", "checked": false}] |
list_id | string | No | Move card to this list/column ID |
position | number | No | New sort position within the list |
Example prompts:
"Move card-001 to the Done column"
"Update the title of card-005 to 'Fix header layout on mobile'"
"Set the due date on card-012 to 2026-04-01"
"Move all cards in the Review column to Done"
Returns: Updated card object.
Tips for effective use
- Start broad: Ask "What new feedback do we have?" to get an overview
- Reply to feedback: Ask your AI to comment on feedback items to keep your team in the loop
- Tag teammates: Use
@DisplayNamein comments to notify specific people — ask your AI to list team members first if you're not sure of the exact name - Generate tickets from feedback: After reviewing feedback, ask your AI to generate tickets for items you want to work on
- Update as you go: Tell your AI to mark tickets as done when you finish implementation
- Manage your board: Ask your AI to move cards between columns, update due dates, or check off items — use list_board_lists first to see available columns
- Filter by project: If you work on multiple projects, specify which one you are asking about