MCP Server Suite
This suite provides five production-ready MCP servers for restaurant orders, web search, browser automation, and filesystem operations, supporting both stdio and HTTP/SSE transports.
README
MCP Server Suite
Five production-ready Model Context Protocol (MCP) servers built with the official Python SDK. Supports both stdio and HTTP/SSE transports.
This suite enables any MCP-compatible client (Claude Desktop, Cursor, OpenCode) to interact with restaurant data, web search, browser automation, and filesystem operations.
What is MCP?
MCP is an open standard that lets AI applications connect to external tools and data sources through a uniform interface. Think of it as USB-C for AI tools — write once, integrate everywhere.
Servers
1. restaurant_server (stdio)
Wraps restaurant ordering tools for MCP clients.
Tools: get_menu, check_dish_availability, check_quantity, add_item_to_cart, view_cart, get_suggestions, finalize_order
2. searxng_server (stdio)
Wraps a local SearXNG meta-search engine.
Tools: web_search, image_search
- Supports categories, language, safesearch, time range, and result count
- Uses
httpx.AsyncClientfor non-blocking requests
3. pinchtab_server (stdio)
Wraps a local PinchTab headless browser.
Tools: navigate, snapshot, click, fill, extract_text
- Enables LLM-driven web browsing and form interaction
- Communicates via PinchTab's REST API
4. filesystem_server (stdio)
Sandboxed filesystem operations with path traversal protection.
Tools: read_file, write_file, list_directory, search_files, file_stat, move_file, copy_file, delete_file
_resolve()enforces workspace sandboxing viaPath.relative_to()- Binary files returned as base64
5. filesystem_server_sse (HTTP/SSE)
The same filesystem server exposed over Server-Sent Events on HTTP.
- Built with Starlette + uvicorn + anyio memory streams
- Per-session JSON-RPC message routing
- Endpoints:
/(info),/sse(event stream),/messages(POST)
Quick Start
1. Install
pip install -r requirements.txt
2. Configure MCP Client
Copy mcp.json.example to your client's config directory and update URLs:
cp mcp.json.example ~/.config/claude/mcp.json # Claude Desktop
cp mcp.json.example ~/.config/opencode/mcp.json # OpenCode
3. Run Individual Servers
# stdio servers (spawned by MCP client)
python -m mcp_servers.restaurant_server
python -m mcp_servers.searxng_server
python -m mcp_servers.pinchtab_server
python -m mcp_servers.filesystem_server /path/to/workspace
# SSE server (runs as HTTP daemon)
python -m mcp_servers.filesystem_server_sse /path/to/workspace
# Then connect to http://localhost:3000/sse
SSE Transport Deep Dive
The SSE server is the most technically interesting component:
# Per-session memory streams
rx_send, rx_recv = anyio.create_memory_object_stream(100)
tx_send, tx_recv = anyio.create_memory_object_stream(100)
# MCP server runs in background asyncio task
await server.run(rx_recv, tx_send, server.create_initialization_options())
# SSE handler serializes messages as JSON events
yield f"event: message\ndata: {message.model_dump_json()}\n\n"
# Client POSTs to /messages, injected into receive stream
await SESSIONS[session_id]["rx_send"].send(JSONRPCMessage.model_validate(data))
Key design decisions:
- Memory streams decouple HTTP I/O from MCP protocol logic
- Session cleanup on disconnect prevents resource leaks
- JSON-RPC message validation ensures protocol compliance
Environment Variables
| Variable | Default | Description |
|---|---|---|
SEARXNG_URL |
http://localhost:8080 |
SearXNG base URL |
PINCHTAB_URL |
http://localhost:9867 |
PinchTab API URL |
RESEARCH_WORKSPACE |
~/workspace/research |
Research report output directory |
MCP_HOST |
0.0.0.0 |
SSE server bind host |
MCP_PORT |
3000 |
SSE server bind port |
Architecture
MCP Client (Claude Desktop / Cursor / OpenCode)
|
v
+-- stdio transport --+ +-- SSE transport --+
| python -m server | | http://host:3000 |
+--------------------+ +-------------------+
| |
v v
Restaurant Data Filesystem Ops
SearXNG Search (remote access)
PinchTab Browser
Security Notes
- Filesystem sandboxing:
_resolve()prevents path traversal above workspace root - stdio transport: No open network ports — most secure option
- SSE transport: Bind to
127.0.0.1or use reverse proxy with TLS for remote access - PinchTab IDPI: Restricts browsing to allowed origins by default
Testing
Each server can be tested manually:
# Test SearXNG MCP server
python -m mcp_servers.searxng_server
# Then send JSON-RPC messages via stdin
# Test filesystem SSE server
curl http://localhost:3000/
curl http://localhost:3000/sse
Tech Stack
| Component | Technology |
|---|---|
| MCP Framework | mcp Python SDK |
| HTTP Client | httpx (async) |
| SSE Server | starlette + uvicorn + anyio |
| Data Format | JSON / JSON-RPC |
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。