AfterShip Channels for TikTok Shop
Read a TikTok Shop catalog, orders and performance, and publish to a live storefront.
MCP connectors
618 MCP servers with 12,363+ tools, ready to connect to Claude, ChatGPT, Cursor and Agentman agents over the Model Context Protocol.
10 of 618 connectors in E-commerceShow all
E-commerce connectors
Domino's India
Browse the Domino's India menu, build a cart and place a real food order.
Helium 10
Query Amazon keyword research, listing scores, P&L and ad performance.
idealista
Search property listings in Spain, Italy and Portugal.
Mercado Libre Inmuebles
Search Latin American property listings and render them on a map.
ShipBob
Query orders, inventory, shipments and returns across every ShipBob fulfillment center, and create or cancel records.
Shipt
Build a same-day grocery cart.
Ticketmaster
Search Ticketmaster's live event catalog and browse ticket prices.
Tixel
Search live events, browse fan-to-fan ticket resale listings and check prices and seats.
Zomato
Find restaurants, browse menus and place a real, paid food order.
Product names and logos belong to their owners. Each connector is built by its own developer, and Agentman is not affiliated with them. The ones Agentman builds and runs are marked “Built and run by Agentman”.
FAQ
Common questions about MCP servers
What is an MCP server?
A server that exposes a tool’s capabilities over the Model Context Protocol, so an AI agent can call them directly. It is the standard way to let an assistant act in a system rather than just describe it.
How do I connect one of these to Claude or ChatGPT?
Each server page carries its connection URL, which works in any MCP-compatible client. In Agentman Studio connecting is one click and there is no config file to edit.
Are these servers built by Agentman?
Most are not. Each is built by its own developer, and each page names them and links to their documentation. The few Agentman builds and runs are marked “Built and run by Agentman”. Every page lists what the server exposes and cites the sources its factual claims come from.
How do I know what a server can actually do to my data?
Each page lists the tools the server exposes. Where we could read the server directly, every tool carries the safety label its vendor gave it: read-only, acts, or destructive. Each page also has a Limits section; read both before connecting anything to a production system.
Use them in an agent
Put these connectors to work.
Connect any of these once and your agents call their tools on their own: on a schedule, in a workflow, with nobody at the keyboard.