Bay Run
Enables agents to discover, evaluate, and serve task-specialist models (embeddings, reranking, classification, extraction) with OpenAI-compatible endpoints and MCP tools for routing, embedding, reranking, and extraction.
README
Bay Run — find, prove, and serve the right task-specialist model
Agents don't need one giant model for everything — they need the right small specialist for each narrow job (embeddings, reranking, classification, extraction, transcription), proven on their data, served instantly. Bay Run is that loop — OpenAI-compatible and MCP-native:
discover → eval → serve (over a catalog of 147K models, mirrored-first)
- Live:
https://bay-run-mvp-zfmlsu2yla-uc.a.run.app - Remote MCP:
https://bay-run-mvp-zfmlsu2yla-uc.a.run.app/mcp/(streamable-HTTP; add to any MCP client) - Public demo token (rate-limited, try instantly):
bayrun-demo-AS4XgfRmTHgNXRlpuP19zKeMxbcShyvP
⭐ Flagship showcase — the Semantic Intent-Router
flagship/ is the headline proof of the thesis. Every agent framework routes each
user message to the right handler — usually with a $$ frontier-LLM call. The flagship does the same
routing with a 33M-param open embedder Bay Run picks + serves (thenlper/gte-small, proven on
labeled intents by a live bake-off): 95.8% routing accuracy on unseen messages, ~140 ms warm,
~14× cheaper than a GPT-4o-mini intent call — every number captured from the live service.
git clone https://github.com/barneywohl/bay-run && cd bay-run/flagship
pip install -r requirements.txt && python router_demo.py
See flagship/README.md for the scorecard + cost table, and
flagship/more-specialists.md for four more agent sub-tasks (RAG
rerank, multilingual routing, dedup, semantic cache), each with a verified-servable tiny specialist.
Runnable demo — the whole loop in one command
demo/ is a self-contained killer demo: it routes support tickets with a 22M-param open
embedder picked by a bake-off on labeled data — ~26× cheaper than a GPT-4o-mini classification baseline,
at equal-or-lower latency, open weights, no lock-in. Every number is captured from the live service.
git clone https://github.com/barneywohl/bay-run && cd bay-run/demo
pip install -r requirements.txt
python demo.py # ships with the public demo token; runs discover → eval → serve → cost live
demo/README.md— the captured scorecard, latencies, and cost table.demo/mcp-quickstart.md— give your agent the tools in one command.demo/firecrawl-to-bay-run.md— scrape with Firecrawl, run the specialist here.demo/wrappers/— drop-in LangChain / LlamaIndex / OpenAI-Agents adapters.
30-second try
curl -s https://bay-run-mvp-zfmlsu2yla-uc.a.run.app/v1/discover -H "authorization: Bearer bayrun-demo-AS4XgfRmTHgNXRlpuP19zKeMxbcShyvP" -H "content-type: application/json" \
-d '{"query":"multilingual sentence embeddings","kind":"embedding","limit":5}'
Point any OpenAI client at it
from openai import OpenAI
client = OpenAI(base_url="https://bay-run-mvp-zfmlsu2yla-uc.a.run.app/v1", api_key="bayrun-demo-AS4XgfRmTHgNXRlpuP19zKeMxbcShyvP")
client.embeddings.create(model="BAAI/bge-small-en-v1.5", input=["hello"])
MCP (agent-callable)
Add the remote server https://bay-run-mvp-zfmlsu2yla-uc.a.run.app/mcp/ to your MCP client (Bearer auth). 9 tools:
find_specialist_for_task (discover→eval→serve on your labeled data), request_specialist (serve-or-capture — returns a serve pointer if a specialist exists, else records your demand), route (runtime auto-router — no examples, picks a specialist per-request), discover_models, eval_models, embed, rerank, classify (guardrail/moderation/sentiment/intent, or zero-shot via candidate_labels + an NLI model), extract (HTML/text → schema-guided JSON).
Served from a content-addressed, quarantine-gated mirror. Neutral — it helps you pick the model that wins on your data, not sell you one. Backend is closed; this repo is the public manifest + connector.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。