Ecommerce Investigation Agent
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ecommerce Investigation AgentInvestigate why CUP-BLUE-500 sales dropped last week and suggest fixes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ecommerce Investigation Agent
A read-only ecommerce investigation prototype: query sales, inventory, promotions and advertising for an exact SKU, inspect source evidence, and produce constrained action drafts.
The business module can run independently as a CLI or stdio MCP server. A bundled investigation Skill supports integration with CraftAgents; the desktop application and model runtime are upstream dependencies and are not included here. Developed with AI assistance as a learning project.
Quick start
Tested with Bun 1.3.8. After cloning, enter the repository and run:
bun install --frozen-lockfile
bun run typecheck
bun test
bun run demo
bun run previewOpen http://127.0.0.1:4317/ to view eight cases. artifacts/report.html is also a self-contained generated report. The CLI and HTML demo do not call a model.
bun run investigate CUP-BLUE-500
bun run mcpThe MCP process speaks protocol on stdio; use a compatible client for model-driven investigation. See MCP setup.
Related MCP server: Acmezone Data MCP
Demonstrated case
All data is synthetic, fixed at 2026-10-12. The recent window is October 5–11, compared with September 28–October 4.
Metric | Baseline | Recent |
Blue 500ml cup units | 140 | 60 |
Sales change | — | -57.1% |
Unavailable selling hours | 0 | 96 |
Advertising orders | 70 | 30 |
Advertising click conversion | 5.00% | 2.14% |
Stockout and sales decline overlap. Lower advertising conversion may share that explanation; these observations do not prove causality or establish that an ad creative caused the decline. Sample metrics are not business improvements achieved by this software.
Nine read-only tools
Tool | Purpose |
| Confirm exact SKU and variant |
| Product costs, margin floor and daily ad limit |
| Units, revenue and original daily rows |
| Closing inventory and available selling hours |
| Promotion state and effective price |
| Clicks, attributed orders, spend and revenue |
| Manually scan window changes; no scheduler |
| Run a fixed five-query investigation baseline |
| Recompute and compare a structured report |
Reliability and verification
Zod input contracts, exact SKU matching and equal complete windows.
Evidence contains source, refresh date, window, row IDs and original rows.
Missing, stale or conflicting data is exposed; unavailable metrics are null.
Fixed-workflow call budget, timeout, cancellation and ordered JSONL events.
Margin-constrained promotion suggestions and unexecuted action drafts.
Eight synthetic SKU cases and 24 business/real-stdio-MCP tests. This is not an LLM accuracy benchmark.
See architecture and limitations, verification, and sample report.
Repository layout
src/ Domain, data queries, analysis, runtime, MCP and reports
tests/ Business cases, failure paths and real MCP integration
data/ Reproducible synthetic dataset
craft/ Source guide and investigation Skill
integrations/ Portable CraftAgents source and permission templates
examples/ Generated synthetic report examples
docs/ Architecture, setup and verificationUpstream and scope
This project originated as a business extension in a CraftAgents 0.11.4 checkout. It reuses the client's model execution, Skill loading, source discovery and permission checks when integrated. It does not claim to implement the upstream Agent platform.
Upstream: craft-ai-agents/craft-agents-oss. The upstream license and notice are retained in LICENSE and NOTICE.
No real shop or ad account is connected. No production outcome, autonomous business write, scheduled monitoring, RAG or independent LLM reviewer is claimed. Local accounts, credentials, conversations, course materials and monorepo build artifacts are not part of this repository.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP server for the OPERANT AI operating-agent calibration benchmark.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Read-only Remote MCP for externally grounded AI agent trust receipts.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight, local inventory-intelligence MCP server that enables querying structured inventory schemas with read-only, zero-config tools for stock levels, velocity metrics, and purchase orders.1 npmMIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for internal Amazon business data, exposing 19 tools to query sales, inventory, and financial metrics.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable agents to query a read-only 18-SKU product registry and verified 24-track catalog, with evidence-tied lookups, momentum scoring, skin configurations, and a hash-chain-verified ledger over stdio.MIT
- AlicenseNot gradedqualityAmaintenanceExposes three read-only tools over stdio — guarded SQL querying, SKU status lookup, and document retrieval — plus a schema resource. This lets MCP clients such as Claude Code answer stock and policy questions without any write access.MIT