acmeshop
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
AcmeShop MCP AI Summit workshop
A small, local demonstration of an AI agent using MCP to investigate AcmeShop operational data and create an incident. The MCP server wraps a mock REST API; the API alone reads and writes JSON files.
User → AI client → MCP → MCP server → Mock REST API → JSON dataPrerequisites
Node.js 20 or later (Node 22 LTS recommended) and npm. No credentials or external services are needed.
Related MCP server: machine-mcp
Install and run
npm install
npm run devThis starts the API at http://localhost:3000 and starts the MCP process over stdio. Open the API URL for the tiny live dashboard. To run them separately, use npm run api and, in another terminal, npm run mcp.
Reset the workshop after a write demo:
npm run resetTest the REST API
curl http://localhost:3000/customers/C001
curl 'http://localhost:3000/deployments?service=checkout'
curl http://localhost:3000/incidents
curl -X POST http://localhost:3000/incidents -H 'content-type: application/json' -d '{"service":"checkout","severity":"SEV-2","title":"Demo incident","description":"Created through the mock REST API","assignedTo":"E-42"}'Connect an MCP client
The server uses the standard local stdio transport. Start the mock API first, then configure a local MCP-capable client with this command, from the repository directory:
{
"mcpServers": {
"acmeshop": {
"command": "npm",
"args": ["run", "mcp"],
"cwd": "/Users/prateeksharma/Documents/ChatGPT/Confrence"
}
}
}For ChatGPT specifically, local stdio processes and localhost are not automatically reachable from every ChatGPT product or deployment. Use the local Codex desktop MCP configuration if available, or expose the server through a supported remote MCP transport only after adding appropriate authentication. This workshop intentionally keeps the default configuration local and credential-free.
The MCP process forwards every tool call to http://localhost:3000; it never reads the data files directly. The eight tools are intentionally independent so the model chooses how to investigate.
See the workshop guide and presenter script.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Hosted MCP for e-commerce: live product catalog, stock, and pricing for AI agents.
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA demo MCP server built with Node.js and TypeScript that showcases tools, resources, and prompts via stdio, including product search, stock checks, and order placement for a mock store.-
- AlicenseAqualityDmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseNot gradedqualityBmaintenanceEnables compatible agents to call registered local tools and read resources through one stdio server, including harness preparation, knowledge search and document management, memory retention/recall, correction proposals, advisory decisions, tool/skill discovery, and log/source inspection.2Apache 2.0
- AlicenseAqualityCmaintenanceEnables building and evaluating shopping/support agents against a deterministic synthetic retail store with in-memory fixtures. Provides tools, resources, and prompts for product search, cart and order flows, inventory, and policy retrieval over stdio or Streamable HTTP.639 PyPIMIT