"Adding tickets to Trello from Cursor" matching MCP tools:

• list_products

  agentic-shelf

  List products from the connected store, paginated. Use this tool when an agent needs to DISCOVER products by browsing the catalog rather than VERIFYING a known SKU. The response includes the SKU for every product, so a follow-up ``check_stock(sku)`` or ``get_product_details(sku)`` is a natural next step. Args: limit: Number of products to return (1-50, default 10). cursor: Opaque cursor from a previous response's ``next_cursor``. Omit for the first page. Returns: Dictionary with: - products: list of {sku, title, description (≤400 chars), product_type, tags, price, currency, available, image_url, storefront_url} - next_cursor: str or null — pass to the next call to paginate - has_more: bool — whether more products exist - live / source: provenance flags

  Connector

• lifecycle_history

  Servicialo MCP Server

  Get the SCEvent stream for a session — all observed transitions reconstructed from status_history. Returns events[] with discriminated union by event_type (sc.scheduled, sc.confirmed, sc.completed, sc.delivered, sc.verified, sc.cancelled, etc.), plus stream_completeness ("complete" | "partial_pre_trigger") and pagination cursor. Events carry origin="reprojected_from_status_history" and canonical SCEvent shape per docs/protocol/sc-event-canonical-schema-2026-04-18.md §7.2. Filters: event_types (e.g. ["sc.delivered"]), from_sequence (cursor), limit (default 50, max 500). PII note: delivery_proof clinical fields (summary, outcome, next_steps) are returned only for admin-scoped keys. IMPORTANT: backfilled sc_resolved timestamps do NOT emit sc.resolved events in this stream (Forma B, see decisions log 2026-04-18-lifecycle-history-backfill-policy). For current resolution status, use lifecycle_get_state.sc_resolution. Requires X-Org-Api-Key.

  Connector

• automation_list

  Perspective AI

  Lists every automation configured on a perspective with its trigger, channel (sensitive details redacted), execution mode, enabled state, schedule description, and recent error/success metadata. Behavior: - Read-only. - Errors when the perspective is not found or you do not have access. - Sensitive parts of channel delivery (e.g., webhook auth headers, full URLs) are redacted before being returned. - has_error / last_error / last_error_at / failure_count appear only when there have been recent failures. When to use this tool: - Auditing what's wired up on a perspective before adding more automations. - Finding an automation_id to feed into automation_update, automation_delete, or automation_test. - Diagnosing a failing automation via last_error / failure_count. When NOT to use this tool: - Creating a new automation — use automation_create. - Toggling enabled or changing config — use automation_update. - Verifying delivery actually works — use automation_test.

  Connector

• perspective_get_conversations

  Perspective AI

  Returns a token-efficient batch of conversations for bulk analysis. Default output is summaries only (id, summary, trust_score, status, created_at) plus the perspective outline; opt in to full XML transcripts via include_transcripts=true. Default format is TOON (compact); JSON available. Behavior: - Read-only. - Errors when the perspective is not found or you do not have access. - Filters: period (7d/30d/90d/all, default 30d), status, trust_score range. Page size up to 50, default 10. Pass nextCursor back as cursor for the next batch. - Response includes total_matching, returned_count, has_more, nextCursor for sizing. - Citation format when transcripts are included: "conversation_id:message_index". When to use this tool: - Thematic analysis, sentiment distribution, or pattern detection across many conversations. - Building a research summary from many summaries cheaply, then drilling into specific transcripts. - Bulk export with filters. When NOT to use this tool: - Need one conversation in full detail (voice snippets, trust dimensions) — use perspective_get_conversation. - Just need a browsable list with metadata — use perspective_list_conversations. - Aggregate counts only — use perspective_get_stats (call first to size the dataset before batching).

  Connector

• perspective_list

  Perspective AI

  Lists perspectives — either browsing one workspace or searching by title across every workspace the user can access. Items include perspective_id, title, status, conversation count, and workspace info. Behavior: - Read-only. - Browse mode (workspace_id, no query): lists every perspective in that workspace. - Search mode (query): matches against the perspective title across accessible workspaces. Optional workspace_id narrows the search. Query must be non-empty and ≤200 chars. - Errors with "Please provide workspace_id to list perspectives or query to search." if neither is given. - Pass nextCursor back as cursor; has_more indicates further results. When to use this tool: - Resolving a perspective_id from a name the user mentioned (search mode). - Browsing a workspace's perspectives to pick or summarize. When NOT to use this tool: - Inspecting one known perspective in detail — use perspective_get. - Aggregate counts or rates — use perspective_get_stats. - Fetching conversation data — use perspective_list_conversations or perspective_get_conversations. Examples: - List all in a workspace: `{ workspace_id: "ws_..." }` - Search by name across all workspaces: `{ query: "welcome" }` - Search within a workspace: `{ query: "welcome", workspace_id: "ws_..." }`

  Connector

• remove_shopping_list_item

  scraps-kitchen-mcp

  Permanently remove an item from the shopping list. To remove all checked-off items at once, use clear_checked_shopping_items instead. Get item IDs from get_shopping_list first.

  Connector

• dns_check_spf

  DMARKOFF — DMARC, SPF & DKIM Analytics

  Live SPF DNS lookup — queries DNS in real time and returns the SPF record, DNS-lookup count, parsed include tree, TXT diagnostics, errors and warnings. Does NOT require a project — works for any domain, even ones not monitored. Use this to verify SPF configuration, diagnose "too many DNS lookups" issues, or check a domain before adding it to a project.

  Connector

• discover_commerce_tools

  AXIS Toolbox — Agentic Commerce Codebase Intelligence

  Discover AXIS install metadata, pricing, and shareable manifests for commerce-capable agents. Free, no auth, and no mutation beyond read access. Example: call before wiring AXIS into Claude Desktop, Cursor, or VS Code. Use this when you need onboarding and ecosystem setup details. Use search_and_discover_tools instead for keyword routing or discover_agentic_purchasing_needs for purchasing-task triage.

  Connector

• add_recipe_to_shopping_list

  scraps-kitchen-mcp

  Add all ingredients from a saved recipe to the shopping list. Use when the user wants to shop for a specific recipe. Requires the recipe to have structured ingredient data (most recipes do after enrichment). Get recipe IDs from get_recipes first.

  Connector

• workspace_list

  Perspective AI

  Lists every workspace the user can access, with workspace_id, uniqueName (slug), and display name. Behavior: - Read-only. Page size 20, sorted by name. Pass nextCursor back as cursor to fetch the next page. - Optional search matches against name, uniqueName (slug), member emails, and website (case-insensitive); empty results return an empty array. - Other perspective tools accept either workspace_id or uniqueName interchangeably. - Returns description for each workspace — use it to match the right workspace based on context. - Does NOT mark which workspace is the caller's default — call workspace_get_default once and compare ids client-side if you need to highlight it. When to use this tool: - The user names a specific workspace and you need its workspace_id (filter with search). - Showing the user the full set of workspaces they can pick from. When NOT to use this tool: - You just need the user's default workspace — use workspace_get_default. - You already have a workspace_id and want details — use workspace_get.

  Connector

• list_filings

  openregistry

  Return a company's filing history. Each filing has a `filing_id`, `filing_date`, `category`, `description`, and (when upstream exposes one) a `document_id` that round-trips to `get_document_metadata` / `fetch_document`. Raw upstream fields come through verbatim under `jurisdiction_data`. Results are newest-first. **When to use.** The general filing-history tool. Use this for cross-category browsing. Prefer `get_financials` when you specifically want annual-accounts filings (it normalises fiscal-period shape and pre-computes download URLs). Prefer `get_charges` when you want mortgages / secured debt (it returns structured charge fields, not filing metadata). Use `fetch_document` / `fetch_document_pages` on the returned `document_id` to read a filing's actual bytes; this tool does NOT return document content. **Behaviour.** Read-only, idempotent, no side effects. Anonymous rate limit: 20 req/min per IP (3-country fan-out cap in 60s); pro 180, max 900, enterprise 3000. Cached per upstream's policy (minutes to hours); pass no special flag to use cache. Upstream registries may impose their own rate limits (e.g. Companies House 600/5min) that can propagate as 429 errors. Use the optional `category` parameter to filter. Common normalized categories: 'accounts', 'annual-return', 'capital', 'charges', 'confirmation-statement', 'incorporation', 'insolvency', 'liquidation', 'mortgage', 'officers', 'persons-with-significant-control', 'resolution'. Some jurisdictions also accept native form codes directly - pass the upstream code through unchanged if you have one. Pagination: `limit` (default 25, max 1000). Some adapters use cursor pagination - pass back `next_cursor` as `cursor` to continue. Others use numeric `offset`. `has_document` flags whether the body can actually be retrieved via `fetch_document`; some registries expose only the metadata listing with the body paywalled or unavailable. Not every registry publishes a filing list; unsupported jurisdictions return 501. Per-country caveats (ID format, accepted category values, cursor vs offset, document availability and pricing, paid-tier gates) - call `list_jurisdictions({jurisdiction:"<code>"})`.

  Connector

• list_templates

  Carbone MCP

  List stored Carbone templates with filtering, search, and pagination. Filter by Template ID, Version ID, category, or upload origin. Use includeVersions to see the full version history of each template. Supports cursor-based pagination for large collections. Note: filtering by tags is not supported by the Carbone API — use list_tags to discover tags, then filter results manually.

  Connector

• devexpress_docs_get_content

  DevExpress Documentation

  Get full document content by URL from DevExpress documentation. Use this tool to retrieve the complete markdown content of a specific documentation page. PREREQUISITE: ALWAYS call `devexpress_docs_search` before using this tool to get valid URLs. The URL parameter must be obtained from the results of the `devexpress_docs_search` tool.

  Connector

• update_ticket

  Sweeppea MCP

  Update an open support ticket. Use fetch_open_tickets first to get the case_id. Only open tickets can be updated. FORMAT: Only these HTML tags are allowed in description: <b>, <strong>, <i>, <hr>, <br>. NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use <br>  — it creates ugly blank blocks in the UI. Use <br> for line breaks within text only. # update_ticket ## When to use Update an open support ticket. Use fetch_open_tickets first to get the case_id. Only open tickets can be updated. FORMAT: Only these HTML tags are allowed in description: <b>, <strong>, <i>, <hr>, <br>. NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use <br>  — it creates ugly blank blocks in the UI. Use <br> for line breaks within text only. ## Parameters to validate before calling - case_id (string, required) — The case number of the ticket to update - title (string, optional) — New ticket subject (max 200 characters) - description (string, optional) — New ticket description (max 20,000 characters). Allowed HTML: <b>, <strong>, <i>, <hr>, <br>. No scripts, iframes, or executable code.

  Connector

• search_products

  Correkt: The AI-Native Online Marketplace for Physical Products

  Search Correkt's catalog of over 10 million products. Use this tool to find products by name, description, or category. Always use this before adding anything to cart. Tips: - Include price filters when the user mentions a budget - Use sort=price_asc to find cheapest options - Check suggestion field if results seem off — it may correct spelling - Page through results if first page doesn't have what you need

  Connector

• register

  AI Agents Overflow

  Register your agent to start contributing. Call this ONCE on first use. After registering, save the returned api_key to ~/.agents-overflow-key then call authenticate(api_key=...) to start your session. agent_name: A creative, fun display name for your agent. BE CREATIVE — combine your platform/model with something fun and unique! Good examples: 'Gemini-Galaxy', 'Claude-Catalyst', 'Cursor-Commander', 'Jetson-Jedi', 'Antigrav-Ace', 'Copilot-Comet', 'Nova-Navigator' BAD (too generic): 'DevBot', 'CodeHelper', 'Assistant', 'Antigravity', 'Claude' DO NOT just use your platform name or a generic word. Be playful! platform: Your platform — one of: antigravity, claude_code, cursor, windsurf, copilot, other

  Connector

• get_officer_appointments

  openregistry

  Given an officer_id (from `get_officers` or `search_officers`), return every company in the registry where that person has held an appointment, with role, appointed_on, and resigned_on dates. The cross-company tracing endpoint - follow a person's full corporate footprint. **When to use.** Call `get_officer_appointments` - NOT `get_officers` - when you start from a PERSON and want to find every company they've run. Call `get_officers` when you start from a COMPANY and want to list its officers. The two tools are direction-opposite: company→people (`get_officers`) vs person→companies (this tool). Typical PEP-screening pipeline: `search_officers(name)` → `get_officer_appointments(officer_id)` → `get_company_profile(company_id)` for each hit. **Behaviour.** Read-only, idempotent, no side effects. Rate limits: anonymous 20/min, pro 180, max 900, enterprise 3000. Upstream limits (Companies House 600/5min etc.) propagate as 429. Results are paginated (default 35, max 50 per page); pass back `next_cursor` as `cursor` to continue.

  Connector

• update_workspace_member

  Dock

  Change an existing workspace member's role. Editor role required to caller. Owner-tier transitions (promoting to or demoting from owner) require an owner caller. Demoting the sole owner is blocked; promote someone else to owner first. No-op when the role is unchanged. Emits `member.role_changed` with from/to roles.

  Connector

• credentials-list

  Certifier MCP

  Use this endpoint to list credentials. It supports cursor-based pagination but doesn't have filtering capabilities - for this, please use the credentials-search tool.

  Connector

• search_companies

  SIC Codes UK

  Search UK companies with flexible filters. Combine name search, postcode, status, incorporation date range, SIC/GICS/ICB codes, accounts category, and company type. Returns enriched results with all SIC codes, GICS/ICB mappings, and address details. Cursor pagination for large result sets.

  Connector