Skip to content

MCP server

Terminal.shop MCP Server

MCP server for the Terminal.shop coffee store API, letting an AI client browse products, manage a cart, place orders and handle subscriptions.

  • Community
  • Runs locally
  • API key

Repository and documentation last checked Built from public product pages and documentation. SourcesClaim this listing

Not listed in the ecommerce MCP directory

It orders from a single retailer on a shopper's behalf, rather than serving store operators.

Browse the MCP servers that are listed

ecommerceguide summary

Terminal.shop MCP server exposes the Terminal.shop coffee storefront to AI agents, letting them browse SKUs, manage carts, handle subscriptions, and process payments through natural language calls. Aimed at developers building agentic commerce prototypes or Claude-based shopping assistants, it acts as a reference implementation for how a niche DTC catalogue can be wired into the Model Context Protocol without building custom tool schemas from scratch.

Why it stands out

A public MCP server wired to the Terminal.shop storefront API, covering carts, orders and coffee subscriptions.

What Terminal.shop MCP Server does

ecommerceguide editorial
  • Exposes Terminal.shop catalogue and cart actions as MCP tool calls
  • Checkout converts the cart to an order, with subscription tools
  • Connects Claude Desktop to the Terminal.shop storefront API
  • Ships as an open-source reference for agentic commerce experiments
  • Handles product browsing, cart state, and recurring coffee orders

How ecommerce teams could use it

ecommerceguide editorial

Illustrative scenarios written by ecommerceguide from the product's documented capabilities. They are not customer case studies.

  1. Developer-led DTC startup exploring agentic commerce

    Engineering team wants a working reference for wiring a storefront into Claude before committing to a custom integration for their own catalogue

    Intended outcomeWorking agentic checkout demo: cart, subscription and payment flow runnable end to end against a real storefront rather than a mock

  2. AI platform or agent-framework vendor building commerce demos

    Team needs a live MCP-wired catalogue to showcase conversational shopping in sales demos, conference talks, or developer documentation

    Intended outcomeReusable demo surface showing natural-language browse-to-purchase, avoiding the cost of standing up a throwaway store

  3. Commerce engineer at a coffee or niche DTC brand

    Evaluating whether MCP is viable for their own subscription catalogue by studying a schema for products, carts and recurring orders

    Intended outcomeConcrete tool-schema blueprint to adapt for their own headless stack, shortening MCP integration scoping

Who it suits

ecommerceguide editorial

Best for

You're a developer or AI vendor prototyping agentic commerce and want a live, open-source MCP reference tied to a real storefront rather than a mock.

Probably not for

You're a brand looking to deploy agentic commerce on your own catalogue, since this is a Terminal.shop-specific integration, not a general-purpose MCP commerce layer for Shopify, BigCommerce, or custom backends.

Business size
Small businesses, 1-5 engineersThis is a reference implementation for a single niche coffee storefront, useful primarily to developers prototyping agentic commerce rather than operators running revenue through it at scale.
Verticals
Food and beverage

Technical details

From the vendor's own pages

From the server's repository, documentation and MCP directory listings.

What an agent can do
Agentic shopping, Orders, Manage products, Payments
Transport
stdio (local)
Authentication
API keyCreate a token via 'ssh terminal.shop -t tokens' and set TERMINAL_API_TOKEN in the Claude config env.
Package
terminal-mcp-server
Language
JavaScript
Licence
MIT
Repository last updated
27 May 2025

Connect Terminal.shop MCP Server

Third-party data

Setup documented for

Install command
npm install

Command as listed on the repository README, not tested by ecommerceguide. Check the repository README (opens in a new tab) for configuration and credentials before running it.

Often used alongside

ecommerceguide editorial

Categories and use cases

Sources

ecommerceguide profiles are built from public product information and written for ecommerce teams. We do not test products, and paying never changes where a listing ranks.

Also listed on PulseMCP.

See something incorrect? Report an update