"How to execute trading operations on KuCoin" matching MCP servers:

Helps a commerce operations analyst investigate stuck synthetic orders, diagnose blockers from stored facts, and create auditable human-review escalations without changing fulfillment state.

Enables AI agents to independently investigate and resolve e-commerce order issues, particularly refund processing, with tools for order search, refund eligibility checks, and safe refund execution.

MCP server providing business tools for customer support and account management, integrated with SQLite, OpenAI, and Streamlit.

Laya-MLX as an MCP server (and plain-HTTP API). It answers typed decisions — choose an option / score a rubric / is this true? — on your own machine (Apple Silicon / MLX), with no cloud and ~10ms after warm-up. Not a chatbot. No token-by-token text, no JSON that can break. One forward pass returns a structured answer you can branch on. Ideal for routing, triage, classification, lead scoring, and g

Provides MSP support tools (ticket search, draft response, KB search, update) with a deterministic security guardrail that refuses to draft responses for security tickets based on content scanning, even if mislabeled.

Enables AI agents to discover and call Xyte's device management API endpoints with typed validation, supporting fleet investigation, ticket management, and routine operations through natural language.

Enables Turkish e-commerce sellers to manage Trendyol marketplace store operations through AI assistants, including viewing products, orders, returns, and customer questions, with optional guarded write actions for answering questions and updating stock and prices.

Enables AI agents to create, query, search, and manage Movidesk tickets directly via natural language.

MCP server for Zammad that focuses on workflows the standard Zammad API tooling does not cover well — primarily shared drafts with strict reply-HTML validation, fresh signature rendering and German-localised quote blocks.

Enables AI agents to read monitors and incidents and to create, update, and resolve incidents on Kener v4 status pages, with read-only tools marked safe and write operations available when permitted.

A production-grade MCP server for Zendesk that provides ticket management, search, user/group operations, and knowledge base access with support for local stdio and remote HTTP transports, authentication via API keys or OAuth, and multi-tenancy.

MCP server for managing support tickets on Concrete CMS sites via REST API. Enables listing, reading, replying to tickets, and handling projects, attachments, and moderation.

Enables LLMs to interact with Jira Cloud through the official REST API v3, supporting operations like creating issues, searching with JQL, fetching issue details, and managing transitions.

Enables natural language interaction with the Movidesk public API for managing tickets and persons/organizations, including CRUD operations and file attachments.

A ServiceNow MCP server that enables natural language management of incidents via the Table API, with tools to create, read, update, search, comment on, and resolve incidents.

Enables Claude Code and Claude Desktop to automate order operations through the Chatea Pro API, including reading contacts, orders, tags, flows, and agents, and acting on individual contacts via tagged writes with dry-run and opt-in safety gates.

Enables MCP clients to read a Mercado Livre seller's account, listings, questions, orders and daily visits, and to perform a small set of changes such as updating a listing, uploading an image, or answering a buyer question. Write operations return a preview of the exact request unless explicitly confirmed.

Enables AI assistants to manage PagerDuty incidents, view alerts, and check on-call schedules with both read-only and write operations.

Enables Codex to interact with the Atera REST API, including reading customers, agents, tickets, and alerts, checking health, and listing capabilities, with optional write operations when explicitly enabled.

Enables interaction with Pega case operations through a metadata-driven tool layer, allowing users to fetch, update, and manage cases. It supports standard Pega actions such as retrieving case details, attaching documents, and submitting case actions via API.