bearing-local-business
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., "@bearing-local-business What are your hours and what's on the menu?"
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.
bearing-local-business
bearing-local-business is a Bearing reference stdio MCP server for a fictional bakery, Cypress & Crumb. It makes a local business agent-queryable so a customer's AI agent can check hours, inspect the menu, ask about custom-order timing, and initiate a demo inquiry.
All data is fictional demo data. The server makes no network calls, persists nothing, and is intended as a reference for the agentic economy: a local business exposing a clean, typed MCP surface for discovery and transaction initiation.
Tools
get_business_profile
Input: none
Output: bakery name, tagline, weekly hours, address, phone, pickup details, delivery details, and custom-order lead time
get_menu
Input:
{ category?: string }Output: the full menu grouped by category, or the filtered category if provided
check_custom_order_availability
Input:
{ date: string, orderType?: string }Output: whether the requested date is far enough out for a custom order, the integer days out, and the earliest available date
submit_order_inquiry
Input:
{ name: string, contact: string, details: string, date?: string }Output: a demo inquiry reference plus the captured request details
Related MCP server: agent-storefront
Run
Development:
bun run devBuild and run the compiled server:
bun run build
bun run startThe server reads src/data/demo-bakery.json at runtime with readFileSync and import.meta.url path resolution. The loader checks both the source-layout path used by bun run src/index.ts and the built-layout path used by node dist/index.js, so the JSON file does not need to be copied into dist/.
MCP Client Config
Example Claude Desktop or compatible stdio client config:
{
"mcpServers": {
"bearing-local-business": {
"command": "node",
"args": [
"/absolute/path/to/bearing-mcp/dist/index.js"
]
}
}
}For local development, you can also point a client at Bun:
{
"mcpServers": {
"bearing-local-business": {
"command": "bun",
"args": [
"run",
"/absolute/path/to/bearing-mcp/src/index.ts"
]
}
}
}Point It At A Real Business
To adapt this for a real business, replace the fictional demo-bakery.json source with a consented, authenticated system of record such as a POS, ordering backend, or inventory service. In a real deployment:
keep the MCP tool contracts stable
add authentication and authorization
persist inquiries into the business's system
fetch live hours, menu, and availability from an approved source
This demo intentionally does none of that. It persists nothing and only echoes a simulated inquiry capture.
Available Tools
4 toolscheck_custom_order_availabilityCheck custom-order availabilityA
Given a requested YYYY-MM-DD date, report whether it meets the custom-order lead time, how many days out it is, and the earliest available date.
Inputs: date (required), orderType.
get_business_profileGet business profileA
Return the bakery's core profile: name, tagline, weekly hours, address, phone, and pickup/delivery details.
Inputs: no named parameters.
submit_order_inquirySubmit an order inquiry (demo)A
Capture a demo custom-order inquiry and return a reference. This is a demo: nothing is persisted or transacted.
Inputs: name (required), contact (required), details (required), date.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct concern: business profile, menu, availability check, and inquiry submission. There is no functional overlap between any pair of tools.
All tool names follow a consistent verb_noun pattern: check_, submit_, get_, get_. The verbs are specific and the pattern is uniform.
With only 4 tools, the set is tightly scoped to the server's purpose of providing business info and handling custom-order inquiries. Each tool earns its place.
The tool surface covers the core domain: discovering the business (profile), exploring offerings (menu), verifying order feasibility (availability), and initiating an order (inquiry). No essential operation is missing for the stated demo scope.
Maintenance
Related MCP Connectors
AI agent platform: manage leads, conversations, bots, calendar and CRM via MCP.
Phone, SMS and email for AI agents. One remote MCP endpoint, OAuth login, zero install.
Hosted MCP for e-commerce: live product catalog, stock, and pricing for AI agents.
Turn your offers into an AI agent. Set it up from your MCP assistant, answer customer questions, collect enquiries and connect with other agents via A2A. OAuth sign-in; free plan available.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for managing bakery recipe technical sheets with Postgres. Enables AI agents to search, create, update, approve, and compare recipe versions through secure tools.-
- FlicenseNot gradedqualityDmaintenanceEnables any AI agent to discover, query, and order from a restaurant's storefront via MCP tools. It handles menu lookup, modifier validation, and enforces a mandatory confirmation gate before payment, replacing the human-operated phone line.-
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes tools to query DulceGestion business data (orders, stock, customers) and retrieve documentation via RAG, enabling Claude to assist with pastry shop management.ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage products, shopping carts, and orders in an online store through a well-defined MCP API.-