2,500+ MCP servers ready to use
Vinkius

Linnworks (E-commerce Ops) MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Linnworks (E-commerce Ops) and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "linnworks-e-commerce-ops": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Linnworks (E-commerce Ops)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Linnworks (E-commerce Ops) MCP Server

Connect your Linnworks account to any AI agent and take full control of your multi-channel e-commerce inventory and order management through natural conversation.

Claude Desktop is the definitive way to connect Linnworks (E-commerce Ops) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Order Orchestration — List all open orders across your integrated marketplaces (Amazon, Shopify, eBay) and retrieve detailed line items and shipping info directly from your agent
  • Inventory Intelligence — Query specific product details by exact SKU, including weights, categories, and extended property mappings required for accurate listings
  • Multi-Location Stock — Retrieve real-time stock levels across all your physical warehouses and virtual locations to identify shortages or surplus inventory
  • Logistics Audit — List configured postal services, shipping methods, and carriers to understand your fulfillment network and cost structures
  • Sales Channel Monitoring — Enumerate active sales channels and their integration statuses to ensure your multichannel synchronization is healthy
  • Supplier & PO Management — List configured suppliers and monitor recent returns and refunds from the last 30 days to maintain supply chain visibility

The Linnworks (E-commerce Ops) MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Linnworks (E-commerce Ops) to Claude Desktop via MCP

Follow these steps to integrate the Linnworks (E-commerce Ops) MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Linnworks (E-commerce Ops)

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Linnworks (E-commerce Ops) MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Linnworks (E-commerce Ops) through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Linnworks (E-commerce Ops) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Linnworks (E-commerce Ops) MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Linnworks (E-commerce Ops) MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Linnworks (E-commerce Ops) to Claude Desktop via MCP:

01

execute_custom_rpc

Example path: /api/Inventory/GetInventoryItemTitles. All Linnworks APIs are POST-based RPC. Refer to apps.linnworks.net/Api for the full endpoint list. Execute any custom fallback POST RPC method exposed by Linnworks API

02

get_inventory_item

Use this to check product details, pricing, weight, and category assignment for a specific product. Get Linnworks inventory item details by exact SKU

03

get_stock_level

Returns available, in-order, due, and minimum quantities per location. Get Linnworks stock levels across all locations by Item ID

04

list_categories

Returns category IDs, names, and parent-child hierarchy. Use to understand product organization and filter inventory. Get Linnworks active product grouping categories

05

list_channels

) and their properties via /api/Inventory/GetChannels. Returns channel ID, source name, subchannel info, and integration status. Get Linnworks active sales channel properties (Amazon, Shopify, etc)

06

list_locations

Returns location ID, name, address, and configuration settings for each warehouse. Get Linnworks explicitly configured inventory locations/warehouses

07

list_open_orders

Pass limit to control pagination. Returns order details including order IDs, customer info, shipping, and item lines. Get Linnworks open orders including lines and customer info

08

list_postal_services

Returns service names, carriers, tracking capabilities, and cost configuration. Get Linnworks explicitly configured postal services

09

list_returns

Returns return IDs, reason codes, refund amounts, order references, and processing status. Get Linnworks recent returns from the last 30 days

10

list_suppliers

Returns supplier names, codes, contact details, and currency settings. Get Linnworks configured purchase order suppliers

Example Prompts for Linnworks (E-commerce Ops) in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Linnworks (E-commerce Ops) immediately.

01

"List the last 10 open orders from Linnworks"

02

"Show me the stock levels for SKU 'CL-NV-001' across all locations"

03

"What sales channels are currently connected to our account?"

Troubleshooting Linnworks (E-commerce Ops) MCP Server with Claude Desktop

Common issues when connecting Linnworks (E-commerce Ops) to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Linnworks (E-commerce Ops) + Claude Desktop FAQ

Common questions about integrating Linnworks (E-commerce Ops) MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect Linnworks (E-commerce Ops) to Claude Desktop

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.