AfterShip Channels for TikTok Shop MCP server icon

AfterShip Channels for TikTok Shop

by AfterShip Channels for TikTok Shop

HIPAA CompliantSOC2 ReadyISO 27001 Ready
E-commerce11 tools

Read a TikTok Shop catalog, orders and performance from an AI agent, and publish products to a live storefront. Anthropic lists 11 read-shaped tools; the server's own OAuth descriptor advertises an edit scope none of them carries.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect AfterShip Channels for TikTok Shop via MCP

https://mcp.aftership.com/channels

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

AfterShip Channels for TikTok Shop Tools & Capabilities (11)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The listed tool count is a floor, and the gap is on the write side. The server advertises mcp:feed/product-listings:edit and AfterShip documents creating publish tasks, yet all 11 listed names are read-shaped. At least one write tool exists that Anthropic's listing does not name, and we could not enumerate it.
  • AfterShip publishes no tool list for this server. We checked its documentation site, its help centre and its public repositories. The capability documentation is genuinely useful and describes what the connector does, but it names no tools, so no name-level diff was possible.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail, readOnlyHint or destructiveHint is published here.
  • Publishing changes a public storefront and is not cleanly undone. A listing goes live under your brand after TikTok's review, product-level customisation detaches the source store's auto-sync, and bulk publishing reaches 50,000 products. The confirmation prompt AfterShip describes is a vendor claim we did not observe.
  • The scope grant does not separate a routine publish from a catalog-wide one. One product-listings:edit permission covers editing a single title, overriding prices across variants, and a bulk push. There is no narrower grant to choose at consent.
  • The authorization server advertises no MCP scopes. AfterShip's Keycloak realm publishes only OpenID identity scopes such as openid, profile and email. Every mcp: scope comes from the resource server's own descriptor, so the two documents describe different vocabularies and only the resource descriptor constrains this connector.
  • The nominated documentation URL is a generic MCP explainer. Anthropic's directory points at AfterShip's "What is MCP" page, which describes the protocol rather than the connector. The capability documentation is one page over, linked below, and it is where every AfterShip claim on this page comes from.
  • AfterShip's docs host blocks non-browser clients. www.aftership.com returned HTTP 403 with a Cloudflare challenge to every command-line and server-side fetch we attempted, including robots.txt itself. We read the documentation in a real browser instead. We were therefore unable to read AfterShip's robots.txt or any Content-Signal directive, and cannot confirm the host's stated preferences on AI use; we have synthesised and linked rather than reproduced.
  • Rate limits are not published. AfterShip documents none for this MCP server, and we did not probe for them.
  • Refund and buyer-field detail is unresolved. Refund rate is a documented metric; whether per-order refund records or specific buyer fields reach the agent is not documented, and we did not test it.

Frequently asked questions

Yes. AfterShip's documentation describes the agent confirming which products to publish and to which shop, then creating the publish task and reporting back when listings go live. The server's OAuth descriptor also advertises an edit permission over product listings. No tool among the 11 Anthropic lists carries a publish verb, so the write path is real but unnamed in the listing.

No tool and no OAuth scope permits it. The descriptor grants only view over orders, with no edit counterpart, and none of the 11 listed tools carries a ship, cancel, fulfil or refund verb. AfterShip's wider Feed platform does sync tracking numbers and cancellations to TikTok Shop, but those run as background sync jobs outside this connector's permission grant.

No. No tool name carries a send, message, reply or notify verb, and no OAuth scope covers buyer communication or conversations. AfterShip's own capability documentation for this connector describes publishing, sync monitoring and performance reporting, and never mentions buyer messaging. Publishing a listing is outbound to a public storefront rather than to an individual customer.

Eleven is the directory's count and it is almost certainly a floor. AfterShip publishes no tool list anywhere, and all 11 listed names begin with check, get or smart-list. The server's own OAuth descriptor advertises an edit permission over product listings that no listed name could exercise, so at least one write tool exists that the listing does not show.

Nine, and eight of them are read-only. The server's RFC 9728 descriptor advertises view permissions over product listings, orders, subscription billing, analytics, onboarding, categories, products and store connections, plus one edit permission over product listings. That single edit scope is the only write authority in the grant, which puts a real boundary around the catalog.

No. AfterShip states that a single OAuth connection links one chosen organization to the agent, and that access is scoped to that organization and isolated from your others. The install guides confirm you pick the organization during the OAuth flow. Connecting the wrong one is fixed by removing the connector and re-running OAuth.

The OAuth flow most likely did not finish. AfterShip's troubleshooting for Claude Code says to re-run the login command, because the flow may not have completed on the first attempt. In Claude Desktop the equivalent symptom is a missing OAuth window, which AfterShip attributes to the browser blocking pop-ups from the app.

Order records, and the connector's own tooling does not narrow which fields. A tool reads orders under a view scope, and TikTok Shop orders carry buyer and shipping details by construction. AfterShip publishes no field-level schema for this connector and the endpoint would not list schemas to us, so treat the order surface as containing personal data.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
E-commerce
Developer
AfterShip Channels for TikTok Shop
Tools
11
Domain
mcp.aftership.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.