Quotations MCP Server
A read-only MCP server that provides conversational querying of quotations data (counts, values, lookups) via tools like quotation_stats, search_quotations, and find_by_number.
README
Quotations MCP Server
Standalone MCP server exposing the quotations-app backend as tools. It's a thin HTTP client over the quotations REST API — no database of its own — so it stays decoupled and can point at local dev or the live Render backend.
MCP agent ──MCP──► server.py ──HTTP──► quotations-app backend ──► MongoDB
Tools
Purpose is conversational intelligence — let an agent answer natural-language questions about quotations (counts, values, who-has-what, lookups) and take actions.
Conversational / query (read):
| Tool | Answers |
|---|---|
quotation_stats() |
"how many are pending?", "total pipeline value?", "who has the most?" — counts by status + value by assignee |
search_quotations(company?, status?, assignee?, number?, min_total?, max_total?) |
"show quotations assigned to Vijender over ₹10k" — filtered list + total value |
find_by_number(quotation_number) |
resolves a human number like QT-2026-000005 to the full quotation |
list_quotations() |
all quotations (compact) |
get_quotation(quotation_id) |
one full quotation by internal id |
health() |
backend reachability + count |
READ-ONLY by design. This MCP only queries the customer's data and answers questions — it never writes (no create/reassign). Creating or modifying quotations is the customer app's job. The backend exposes only list + get, so filtering/aggregation is done here; prices/totals come only from the server-computed data — never invented.
Completion / status
A quotation is "completed" only if the customer's data stores that state. Today
their backend hard-codes status:"draft" and never changes it, so quotation_stats
/ search_quotations(status=...) will only ever report draft. The moment their
app writes a real status (e.g. completed/sent), these read tools surface it
automatically — no change here.
Install
pip install -r requirements.txt # mcp[cli], httpx
Run
# stdio (dev / desktop MCP clients)
python server.py
# HTTP endpoint (for the MCP agent to connect to)
MCP_TRANSPORT=http MCP_PORT=8200 python server.py
# → MCP endpoint at http://<host>:8200/mcp
# inspect/try tools
mcp dev server.py
Env
| Var | Default | Purpose |
|---|---|---|
QUOTATIONS_API_URL |
https://quotations-app.onrender.com |
backend base URL |
QUOTATIONS_TIMEOUT |
30 |
HTTP timeout (bump for Render cold start ~50s) |
MCP_TRANSPORT |
stdio |
stdio or http |
MCP_HOST / MCP_PORT |
127.0.0.1 / 8200 |
bind for http transport |
Notes
- Deployed separately from the quotations backend and from Oscar.
- The Oscar agent will later connect to this server (as an MCP client) via a new endpoint — this repo/folder does not depend on Oscar.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。