Tickets, boards, sprints and docs. Every tool below was read from that server's own
tools/list, so the name and arguments are what the server exposes, not what
its description claims.
| Tool | Server |
|---|---|
| ticket_archiveanswers Retire an owned ticket from the working set, or restore one. Archiving is a different axis from status: the ticket keeps whatever status it had, so a done ticket stays done and a blocked one comes back still blocked —... arguments: ticket_id, action | Meta Council com.meta-council |
| generate_ticket_timelineanswers Generate a Mermaid diagram showing the history of a single Jira ticket using its changelog. Two views are available:
- **state**: stateDiagram-v2 showing all status transitions with dates and authors, nodes coloured b... arguments: ticketKey, view, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| generate_ticket_dependency_treeanswers Generate a Mermaid flowchart that visualises Jira issue dependency links for a project. Each node shows the ticket key, summary, and status, and is a clickable link to the ticket. Dashed nodes represent issues linked ... arguments: projectKey, status, assignee, reporter, sprint, createdAfter | com.mermaidchart/mermaid-mcp com.mermaidchart |
| generate_jira_kanban_boardanswers Generate a Mermaid kanban board from Jira issues. Issues are grouped into columns by their current status and ordered by workflow stage (To Do → In Progress → Done). Each card shows the issue summary and is a clickabl... arguments: projectKey, sprint, assignee, issueType, maxResults, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| generate_ticket_diagramanswers Generate a Mermaid flowchart centred on a single Jira ticket. Fetches the ticket's subtasks, parent, issue links, and recent comments in one call. The focal ticket is highlighted in indigo; subtasks are grouped in a s... arguments: ticketKey, colorMode, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| create_support_ticketanswers File a support ticket. Mirrors to a GitHub issue in Dock's support repo and shows up in the user's dashboard at /settings/support. Use this for bugs (you hit an error), feature requests (Dock is missing something), bi... arguments: kind, title, body, context, attachmentUrls | Dock ai.trydock |
| list_support_ticketsanswers List support tickets (READ-ONLY) from Dock's support repo. These are the SAME tickets create_support_ticket files, so the list reflects ALL tickets — whether routed through chat or filed directly via the support API/f... arguments: state, limit | Dock ai.trydock |
| get_support_ticketanswers Read ONE support ticket by its number (as shown in list_support_tickets), including the full body/description. Read-only, scoped to Dock's support repo. Returns not-found for a number that isn't a support ticket. arguments: number | Dock ai.trydock |
| create_upload_ticketanswers Get a presigned upload URL for a LOCAL image file — the one case a URL can't cover. PUT the file to uploadUrl with the same Content-Type, then pass the returned r2Path to a generation tool instead of imageUrl. Ticket ... arguments: filename, contentType, sizeBytes | Pixly app.pixly |
| preview_accounting_ticket_syncanswers Preview, without writing, how one completed owned Accounting run's WRITEOff work plan would map to stable Meta Council tickets. Reports creates, updates, unchanged tickets, human-edited generated fields that will be p... arguments: run_id | Meta Council com.meta-council |
| sync_accounting_ticketsanswers Commit a previously previewed completed Accounting run's WRITEOff work plan to stable owner-private Meta Council tickets. The expected_plan_hash from the preview is required, retries are idempotent, stable references ... arguments: run_id, expected_plan_hash | Meta Council com.meta-council |
| ticket_plananswers Preview or idempotently commit an owner-private ticket tree generated from a planning prompt or supplied structured plan. Requires tickets:write. A preview without a supplied plan invokes the planner model and additio... arguments: mode, idempotency_key, preview_token, prompt, context, model | Meta Council com.meta-council |
| ticket_batch_createanswers Preview or idempotently commit one atomic owner-private batch of structured tickets and nested subtickets. Preview is non-mutating and returns the normalized commit payload, exact preview_token, and deterministic pred... arguments: mode, idempotency_key, preview_token, parent_id, tickets | Meta Council com.meta-council |
| ticket_listanswers Page through the caller's tickets on the Meta Council board. The opaque next_cursor is owner- and filter-bound; keep every filter unchanged on the next call. Immutable cursor ordering keeps a stable full-board travers... arguments: status, assignee, action_type, priority, parent_id, session_id | Meta Council com.meta-council |
| ticket_getanswers Full detail for one owned ticket: description, acceptance criteria, subticket progress, and the recent activity/comment trail. ticket_id is required. arguments: ticket_id | Meta Council com.meta-council |
| get_ticket_projectsanswers Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (bac... | Meta Council com.meta-council |
| get_ticket_burndownanswers Daily burndown series replayed from the append-only ticket ledger: per-day scope (existing, non-cancelled), remaining, done levels plus added/completed flows, with a summary. Optionally scope to one epic's current sub... arguments: days, root_id, target_date | Meta Council com.meta-council |
| ticket_validation_finalizeanswers Finalize one immutable validation run for an exact owned ticket scenario revision. Requires the opt-in tickets:validate scope. The server derives owner and actor only from the authenticated API key. Evidence payloads ... arguments: ticket_id, scenario_id, scenario_version, scenario_hash, verdict, runner | Meta Council com.meta-council |
| ticket_scenario_createanswers Author one Given/When/Then scenario on an owned ticket. This is the specification an epic must carry before it can be completed: record a passing run against it with ticket_validation_finalize, then transition the epi... arguments: ticket_id, name, given_steps, when_steps, then_steps, scenario_key | Meta Council com.meta-council |
| ticket_scenario_reviseanswers Replace an owned scenario's content, compare-and-swapping on expected_version. Revisions are append-only: validation runs already recorded keep naming the exact version and hash they were proven against, so revising n... arguments: ticket_id, scenario_id, expected_version, name, given_steps, when_steps | Meta Council com.meta-council |
| ticket_scenario_listanswers List an owned ticket's scenarios with their exact current revisions, including the current_version and current_definition_hash that ticket_validation_finalize requires. Read-only. Use it before recording a run to conf... arguments: ticket_id, include_archived | Meta Council com.meta-council |
| ticket_dependency_addanswers Record that an owned ticket cannot complete until another owned ticket is done. The edge is never erased: correct a mistake with ticket_dependency_remove, which marks the edge removed and appends to a ledger rather th... arguments: ticket_id, depends_on_ticket_id | Meta Council com.meta-council |
| ticket_dependency_removeanswers Stop an owned ticket from waiting on a prerequisite. Removing the last unsatisfied edge can allow this ticket to close, so this is a gate-opening action. Nothing is deleted: the edge is retained, marked with who remov... arguments: ticket_id, dependency_id | Meta Council com.meta-council |
| ticket_dependency_listanswers List the prerequisites an owned ticket waits on. Read-only. Each edge reports satisfied, which is true only when the prerequisite is done, plus active/removed_at/removed_by_actor. Removed edges are omitted unless incl... arguments: ticket_id, include_removed | Meta Council com.meta-council |
| ticket_createanswers Create a ticket on the caller's board — optionally as a subticket via parent_id. Recommend degree of difficulty with effort (trivial|small|medium|large|epic) and the kind of work with action_type (strategy|implementat... arguments: title, description, status, priority, effort, action_type | Meta Council com.meta-council |
| ticket_updateanswers Update fields on an owned ticket — status moves (each one is auto-logged to the ticket's audit trail), reassignment, priority/effort/action_type recommendations, title/description edits, safe reparenting, opaque sessi... arguments: ticket_id, title, description, status, priority, effort | Meta Council com.meta-council |
| ticket_commentanswers Add a comment to an owned ticket's activity trail. Use kind='progress' for work updates while a ticket is in progress. The authenticated API-key UUID is stamped as author; callers cannot supply or spoof it. Open the c... arguments: ticket_id, body, kind | Meta Council com.meta-council |
| ticket_claimanswers Claim a ticket to work on: sets assignee to your agent name and moves it to in_progress in one step (the move is audit-logged). Refuses if another agent already has it in progress unless force=true. Follow up with tic... arguments: ticket_id, assignee, force | Meta Council com.meta-council |
| get_notion_page_mermaid_diagramsanswers Extract all Mermaid code blocks from a Notion page. Returns block ID, diagram code, and optional caption for each block. arguments: pageUrl, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| get_notion_mermaid_diagram_by_block_idanswers Retrieve a single Mermaid diagram block by its block ID. Returns the diagram code and optional caption. arguments: blockId, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| update_notion_mermaid_diagramanswers Update the Mermaid source code (and optional caption) of an existing mermaid code block by its block ID. arguments: blockId, code, caption, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| insert_notion_mermaid_diagramanswers Append a Mermaid diagram as a code block to a Notion page. The block is added at the end of the page content. arguments: pageUrl, code, caption, clientName | com.mermaidchart/mermaid-mcp com.mermaidchart |
| list_ticketsanswers List support tickets with optional filters. arguments: status, priority, category, accountId, search, limit | FavCRM io.favcrm |
| get_ticket_statsanswers Get ticket counts grouped by status. | FavCRM io.favcrm |
| create_ticketanswers Create a support ticket for a member issue. arguments: subject, description, category, priority, source, accountId | FavCRM io.favcrm |
| update_ticket_statusanswers Update the status of an existing support ticket. arguments: ticketId, status | FavCRM io.favcrm |
| create_ticketanswers Open a support ticket with EQVPS. `subject` and `message` are required; optional `service_id` ties it to one of your VPS. The response includes the ticket `code` — use that with get_ticket / reply_ticket / close_ticket. arguments: subject, message, service_id | EQVPS — Crypto VPS for AI agents io.github.poiuyhje |
| list_ticketsanswers List your support tickets with status and last-message info. `last_message_author: "staff"` means support has replied since you last looked. | EQVPS — Crypto VPS for AI agents io.github.poiuyhje |
| get_ticketanswers Read one ticket and its full message thread. Each message has an `author`: `you` or `staff` — a `staff` message is a reply from support. Poll this to see new answers. The ticket code comes from create_ticket / list_ti... arguments: ticket_code | EQVPS — Crypto VPS for AI agents io.github.poiuyhje |
| reply_ticketanswers Post a reply on one of your tickets. Use the ticket code from create_ticket / list_tickets. arguments: ticket_code, message | EQVPS — Crypto VPS for AI agents io.github.poiuyhje |
| close_ticketanswers Close one of your tickets. `rating` (1-5) and `comment` are OPTIONAL — you can close without rating. Use the ticket code from create_ticket / list_tickets. arguments: ticket_code, rating, comment | EQVPS — Crypto VPS for AI agents io.github.poiuyhje |
| search_notion_docsanswers Search across the Notion Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Notion Docs, find specific documentation, und... arguments: query | notion.com MCP server ora.ai |
| query_docs_filesystem_notion_docsanswers Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Notion Docs documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing ru... arguments: command | notion.com MCP server ora.ai |
| collectionTicketsAllanswers List Tickets List Tickets Tickets | Issue Tracking API apideck.com |
| collectionTicketsAddanswers Create Ticket Create Ticket Tickets | Issue Tracking API apideck.com |
| collectionTicketsOneanswers Get Ticket Get Ticket Tickets | Issue Tracking API apideck.com |
| collectionTicketsUpdateanswers Update Ticket Update Ticket Tickets | Issue Tracking API apideck.com |
| collectionTicketsDeleteanswers Delete Ticket Delete Ticket Tickets | Issue Tracking API apideck.com |
| collectionTicketCommentsAllanswers List Comments List Comments Comments | Issue Tracking API apideck.com |
| collectionTicketCommentsAddanswers Create Comment Create Comment Comments | Issue Tracking API apideck.com |
| collectionTicketCommentsOneanswers Get Comment Get Comment Comments | Issue Tracking API apideck.com |
| collectionTicketCommentsUpdateanswers Update Comment Update Comment Comments | Issue Tracking API apideck.com |
| collectionTicketCommentsDeleteanswers Delete Comment Delete Comment Comments | Issue Tracking API apideck.com |
| evaluateJiraExpressionanswers Evaluate Jira expression Evaluates a Jira expression and returns its value. This resource can be used to test Jira expressions that you plan to use elsewhere, or to fetch data in a flexible way. Consult the [Jira exp... | The Jira Cloud platform REST API atlassian.com |
| SupportTickets_CheckNameAvailabilityanswers Check the availability of a resource name. This API should to be used to check the uniqueness of the name for support ticket creation for the selected subscription. SupportTickets | Microsoft.Support azure.com |
| SupportTickets_Listanswers Lists all the support tickets for an Azure subscription. <br/><br/>You can also filter the support tickets by <i>Status</i> or <i>CreatedDate</i> using the $filter parameter. Output will be a paged result with <i>next... | Microsoft.Support azure.com |
| SupportTickets_Getanswers Gets details for a specific support ticket in an Azure subscription. <br/><br/>Support ticket data is available for 12 months after ticket creation. If a ticket was created more than 12 months ago, a request for data ... | Microsoft.Support azure.com |
| SupportTickets_Createanswers Creates a new support ticket for Quota increase, Technical, Billing, and Subscription Management issues for the specified subscription. <br/><br/>A paid technical support plan is required to create a support ticket us... | Microsoft.Support azure.com |
| SupportTickets_Updateanswers This API allows you to update the severity level or your contact information in the support ticket. <br/><br/> Note: The severity levels cannot be changed if a support ticket is actively being worked upon by an Azure ... | Microsoft.Support azure.com |
| POST /ticketanswers Creates a new trouble ticket Use this service to create a new trouble ticket. Use this to include relevant information about the order, comunicate with the customer or marketplace team. Whenever possible message will ... | BrandLovers Marketplace API V1 brandlovers.com |
https://neuronto.com/tools?q=..., or connect an agent to
https://neuronto.com/mcp and call find_tool. No key, no signup.