mcp-rest-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STORE_API_KEY | Yes | Bearer token/API key used to authenticate requests to the store REST API. | |
| STORE_API_URL | Yes | Base URL of the store REST API, for example http://127.0.0.1:4000/api. | |
| MCP_HTTP_TOKEN | No | Bearer token required when running the MCP server over Streamable HTTP. Clients must send Authorization: Bearer <token>. | |
| STORE_ALLOW_WRITES | No | Set to true to register the write tools adjust_stock and create_order. Write tools are only available when this is true. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for a store's inventory, orders and sales via its REST API. Find SKUs with search_products before calling get_product. All money values are integer cents (12999 = $129.99).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search the catalog by name or SKU fragment and/or exact category. Returns a page of products and the total match count. All money values are integer cents (12999 = $129.99). |
| get_productA | Full details and current stock for one product. All money values are integer cents (12999 = $129.99). |
| list_low_stockA | Products that need restocking: stock at or below each product's own reorder level, or at or below |
| get_orderB | Status, customer, line items and total of one order. All money values are integer cents (12999 = $129.99). |
| list_customer_ordersA | A customer's profile and all their orders, newest first. All money values are integer cents (12999 = $129.99). |
| sales_summaryA | Order count, revenue, average order value, orders by status and top products for a date range (inclusive, UTC). Cancelled orders are excluded from revenue. Defaults to the last 30 days. All money values are integer cents (12999 = $129.99). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| restock_report | Draft a purchase list for products that are running low. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| categories | Every catalog category with its product count and units in stock. |
TDQS
Scored across 6 tools
Each tool targets a distinct resource+action pair: product search vs single product fetch, low-stock filtering, single order fetch, per-customer order history, and aggregate sales reporting. The two order-reading tools (get_order vs list_customer_orders) are clearly separated by scope (one order vs a customer's profile plus all orders), and descriptions reinforce the boundaries.
Five of six names follow a clean verb_noun pattern (search_products, get_product, list_low_stock, get_order, list_customer_orders). sales_summary breaks the pattern by dropping the verb, a minor but noticeable deviation.
Six tools is a tight, well-scoped set with no filler and no overlap. It leans slightly thin for a commerce bridge, with no write-side tools at all, but every included tool earns its place.
Read coverage is solid (catalog search/detail, stock alerts, orders, customer history, sales aggregation), but the surface is entirely read-only: no product creation, no stock adjustment/restock, and no order status or fulfillment updates. Agents can answer questions but cannot complete inventory or order lifecycle operations.