bookstore-mcp-server
An MCP server that exposes tools for querying a bookstore inventory, allowing AI agents to search and retrieve book information via the Model Context Protocol.
README
Simple MCP Server for an Online Bookstore with Custom AI Agent - POC
ποΈ Overview
This project is a proof-of-concept implementation of a Model Context Protocol (MCP) server and a custom AI-powered bookstore agent. It demonstrates how an LLM can call structured tools exposed by an MCP server (e.g., search books) and how a separate agent process can communicate with that server to provide conversational responses.
The repo contains:
-
An MCP server
- Built using
@modelcontextprotocol/sdk - Exposes a sample of bookstore-related tools (e.g., fetching books)
- Includes a seeding script to populate mock bookstore data
- Built using
-
A custom bookstore AI Agent
- Connects to the MCP server as a client via a dedicated MCP client service:
- Uses
@modelcontextprotocol/sdkwith an STDIO-based process transport to talk to the MCP server. - Discovers available MCP tools at runtime and invokes them dynamically
- Uses
- Uses OpenAI to answer user queries
- Decides when to call MCP tools to fetch inventory data
- Can respond normally or stream responses token-by-token
- Connects to the MCP server as a client via a dedicated MCP client service:
-
A lightweight Express API provides endpoints for:
- non-streaming LLM answers
- streaming LLM answers (chunked over HTTP)
- Demonstrates how a backend service can expose the agent to external clients
π οΈ Tech Stack
- Model Context Protocol (MCP) β structured tool calling using
@modelcontextprotocol/sdk - OpenAI API β LLM responses + streaming output
- Express 5 β simple HTTP layer
- TypeScript β typed agent + server
- Zod β schema validation
- Firebase Firestore - for bookstore database
GitHub Branches
-
mainβ Production branch. This branch represents the stable and production-ready version of the code. It is used for deployments to the live environment. -
devβ Development branch. This is the default branch for ongoing development work. It is where new features and bug fixes are implemented and tested before being merged into the main branch. It is used for deployments to the staging environment.
Development
Scripts
npm run dev:serverβ Run the MCP server in development mode with hot-reloadingnpm run dev:agentβ Run the Bookstore Agent in development mode with hot-reloadingnpm run buildβ Compile the TypeScript code to JavaScriptnpm run start:serverβ Start the MCP server in production modenpm run start:agentβ Start the Bookstore Agent in production modenpm run seed:bookstoreβ Seed the Firestore database with mock bookstore data
Testing the MCP server locally using Claude Client
-
Download Claud Desktop
-
Locate the config file
From Claud App -> Settings > Developer -> Edit config
The path is probably:
code "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
- Prepare the config file
# check the absolute path to the server
β― pwd
Ensure Claude will run the correct version of Node:
which node
# should output smt like
> /Users/mistergreen/.nvm/versions/node/v22.17.0/bin/node
Use this path as command in the server config below (instead of using simply node)
Option A β Use the built JS file
If you run npm run build and want Claude to call the compiled JS:
{
"mcpServers": {
"demo-server": {
"command": "/Users/mistergreen/.nvm/versions/node/v22.17.0/bin/node",
"args": ["<ABSOLUTE-PATH>/dist/mcp-server/index.js"],
"env": {
"LOG_LEVEL": "info"
}
}
}
}
Option B β Run TypeScript directly (good for dev)
If you donβt want to build every time, Claude can launch your server through tsx:
{
"mcpServers": {
"demo-server": {
"command": "/Users/mistergreen/.nvm/versions/node/v22.17.0/bin/node",
"args": ["<ABSOLUTE-PATH>/node_modules/tsx/dist/cli.js", "<ABSOLUTE-PATH>/src/mcp-server/index.ts"],
"env": {
"LOG_LEVEL": "info"
}
}
}
}
- Test
-
Save the config.json.
-
Quit and restart Claude Desktop.
-
Testing tools: Start a new chat and try:
- Use the add tool with a=2 and b=3
- Claud should discover the add tool.
- Debug
- From Claud App -> Settings > Developer -> Logs
Testing the agent API
- Start the MCP server
npm run dev:server
- Start the agent API
npm run dev:agent
- Send requests to the agent API
E.g. using curl:
curl -X POST http://localhost:5000/ask \
-H "Content-Type: application/json" \
-d '{"question": "Can you recommend me a sci-fi book?"}'
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.