What is the 3Dsellers MCP server?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools and data sources. The 3Dsellers MCP server gives AI agents secure access to your 3Dsellers account, so you can ask things like "show me my unshipped eBay orders" or "publish these products to my Etsy store" and get real results from your live data.
One connection covers your whole 3Dsellers company, including every connected marketplace account. If you have more than one seller account, you scope a request to a specific one with its seller ID (just ask the AI to "list my sellers" to see them).
What can the AI do with 3Dsellers?
Once connected, an AI agent can work across the areas below. Most tools read your data; the ones marked write can change it.
Products (read + write)
List and filter your products by SKU or segment, with variants included
Create a product with variants, pricing, inventory, images, dimensions, and identifiers (UPC, ASIN, EAN, and more), and optionally auto-generate its SKU from a SKU template
Fully replace a product, or partially update it (change just the title, price, inventory, or images without touching other fields)
Add or remove product tags
Publishing & listings (read + write)
Get product listings, the per-channel, per-seller view of a product. Filter by channel (eBay, Amazon, Etsy), seller, SKU, linked product, status (Active, Library, Ended), or segment, and follow a listing back to its catalog product
Publish products to a marketplace using the same add-to-channel flow as the app, to create new listings or revise existing ones
Add or remove listing tags
Orders (read + tag)
List and filter orders for a seller by status, channel (eBay, Amazon, Shopify...), SKU, or marketplace order ID
Add or remove order tags
Product categories (read + write)
List your categories, and create new ones
Listing & SKU templates (read + write)
View mapping templates and see how each one maps your product fields onto a channel
Bulk-apply channel field mappings (item specifics) across categories, with a dry run first
Look up the fields a channel category accepts and your saved custom attributes
List, create, and delete SKU templates (reusable formulas that build SKUs from product attributes, text, and random parts)
Sellers & policies (read only)
List your connected marketplace accounts, filter by channel, and get details for one
Read a seller's marketplace business policies (payment, shipping, return) for use when publishing
Segments (read only)
Get your saved segments (saved filter sets), and use a segment's ID to scope product or listing queries to it
CSV imports (read only)
List import jobs and their status (pending, processing, done, error)
Get a specific import with its row-level errors, or search validation errors by SKU or item ID
Bulk actions (write)
Run large batch operations from the built-in action catalog, for example tag a whole segment, generate SKUs, or publish in bulk. These run in the background, and the AI can track progress and tell you when they finish
Step 1: Get your MCP token
You only need this token for the developer setups in Step 2 (Claude Code, and the JSON config for Cursor and similar tools). If you are connecting through claude.ai, Cowork, or Claude Desktop (Option A in Step 2), you can skip this step and sign in instead.
1. Open your Integrations settings
Log in to your 3Dsellers account and open Settings > Integrations, then choose All Integrations. (You can also click your account name in the sidebar to reach Integrations.)
2. Find the MCP 3Dsellers tile
Scroll down to the tile labelled MCP 3Dsellers (marked NEW) and click it to open the connection dialog.
3. Copy your token
The dialog shows your personal bearer token. Click Copy next to the token field and keep it somewhere safe, you will need it in the next step.
Keep your token private. Anyone with it can read and change your 3Dsellers data. Do not commit it to code or share it in public channels. If it is ever exposed, regenerate it from this same dialog to invalidate the old one.
Step 2: Connect to your AI tool
Pick the path that matches how you use AI. Option A is the easiest and needs no token; Options B and C are for developer tools and use the token from Step 1.
Option A - claude.ai, Cowork, or Claude Desktop (easiest, no token)
3Dsellers is now listed in Claude's connector directory, so you can add it in a couple of clicks. This path signs you in instead of using a token, so you can skip Step 1.
Open the 3Dsellers connector in Claude's directory and click Connect. (You can also get there from Settings or Customize > Connectors > Browse connectors and search for 3Dsellers.)
Sign in to your 3Dsellers account and approve access. There is no token to copy for this path.
Turn the connector on inside a chat or Project from the + > Connectors menu.
The listing is marked Community, which means it is built and maintained by 3Dsellers rather than by Anthropic. That is expected.
Prefer to add it manually? You can still use + > Add custom connector with the server URL https://api.3dsellers.com/mcp. The result is the same.
Option B - Claude Code (CLI)
Run this command in your terminal, with your token from Step 1 in place of YOUR_TOKEN_HERE:
claude mcp add --transport http 3dsellers https://api.3dsellers.com/mcp --header "Authorization: Bearer YOUR_TOKEN_HERE"
That registers the server with Claude Code. Next time you open a session, the tools are available automatically.
New to Claude Code? See the official setup guide: docs.anthropic.com/en/docs/claude-code/mcp
Option C - Cursor, VS Code, and other MCP clients (JSON config)
Open your client's MCP settings file and add this block, with your token from Step 1 in place of YOUR_TOKEN_HERE:
{ "mcpServers": { "3dsellers": { "type": "http", "url": "https://api.3dsellers.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN_HERE" } } }}
Save the file, restart your AI tool, and the 3Dsellers server will appear in its connected tools list.
Cursor config file:
All projects:
~/.cursor/mcp.jsonOne project:
.cursor/mcp.jsonin the project root
Or open Cursor Settings > Tools & MCP and add the server there.
Claude Desktop config file (if you prefer editing the file to Option A):
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Official guide: modelcontextprotocol.io/quickstart/user
Other clients. Any tool that supports remote MCP servers over HTTP can connect with the same URL and bearer token, including VS Code (through GitHub Copilot's MCP support), with support in other assistants expanding over time. Only the place you enter the server differs; the url and Authorization header stay the same. Check your client's MCP documentation for where its config lives.
Step 3: Ask the AI what it can do
Once connected, the fastest way to start is to ask the AI to describe its tools. Try one of these:
What 3Dsellers tools do you have access to?
What can you help me with in 3Dsellers?
List the available 3Dsellers MCP tools
The AI reads the tool manifest and explains each capability in plain English. From there you can start asking real questions about your store.
Example things to try
Show me my unshipped eBay orders from the last 7 days
Which of my listings are out of stock?
What orders came in today on Shopify?
Show me all active eBay listings for seller 123
Get products in my "Summer Sale" segment
Create a new product with SKU ABC-123, price $19.99, quantity 50
Update the title and description on product ID 456
Tag every order from today as "priority"
Publish products 101, 102, and 103 to my eBay store
Show me any CSV import jobs that failed this week
Step-by-step guides
Once you are connected, these guides walk through the most common tasks, with example prompts and more advanced multi-step requests:
Building your own integration, or need webhooks? See Working with the 3Dsellers developer API.
Frequently asked questions
Can the AI make changes to my store?
Yes, and more than it used to. The AI can create and update products and categories, manage SKU templates, tag products, listings, and orders, apply channel mapping templates, publish products to a marketplace (which creates or revises live listings), and queue bulk actions across many records at once. It only ever acts on your own account's data, and it cannot delete your products, orders, or listings. Reading is available across every area; the marketplace-facing writes (publishing and bulk actions) change live listings, so give those prompts the same care you would the app's own bulk tools.
Which AI tools are compatible?
Any client that supports MCP. You can connect through claude.ai, Cowork, and Claude Desktop as a custom connector (sign in, no token), or through developer tools like Claude Code, Cursor, and VS Code (via GitHub Copilot) using your token. The connection details are the same everywhere; only where you enter them differs.
Do I need the token or can I just sign in?
Both work. Connecting inside claude.ai, Cowork, or Claude Desktop (Step 2, Option A) uses sign-in, so there is no token to manage. Developer tools that read a config file (Claude Code, Cursor, VS Code) use the bearer token from Step 1.
Is my data secure?
Yes. Requests go directly to the 3Dsellers API over HTTPS, and the AI tool only sees the data returned by the specific tool it calls. Keep any token you generate private, and regenerate it any time from the settings dialog. Regenerating immediately invalidates the previous token.
I have several marketplace accounts. Does one connection cover them all?
Yes. One connection works for your whole 3Dsellers company. Ask the AI to "list my sellers" to see each connected account and its seller ID, then include a seller ID in a request to scope it to one account.
Where do I find the full API documentation?
Full endpoint documentation is available at api.3dsellers.com/docs. For an overview aimed at developers, see Working with the 3Dsellers developer API.
Something is not working. Who do I contact?
First check the basics: if you used a token, that you pasted the whole thing after "Bearer " with no extra spaces; that the URL is exactly https://api.3dsellers.com/mcp; and that you restarted your AI tool (or reopened the connector) after setting it up. If it still will not connect, use the "Need more MCP tools?" button in the integration dialog to reach the 3Dsellers team, or use your normal support channel.
Need more MCP tools?
The 3Dsellers MCP server is growing. If there is a resource or action you wish the AI could access, such as shipping management or feedback, you can request it directly from inside the app.
Go to Settings > Integrations > MCP 3Dsellers and click "Need more MCP tools?". Your request goes straight to the 3Dsellers team and helps prioritize what gets built next.


