semantic-runtime
Enables MCP clients to serve and query semantic models, providing tools for entity descriptions, metric lookups, context resolution, and operation validation for AI agents.
README
Semantic Runtime
Semantic infrastructure layer for AI Agents: semantic understanding, context resolution, evidence, and safe execution between models and tools.
Models provide intelligence. Tools provide capability. Semantic Runtime provides understanding.
Status
- Shipped: core data models (Entity / Relation / Metric / Evidence / Policy), YAML model loader, registry, graph engine, deterministic context resolver, metric dependency resolution, schema connectors (SQLite, PostgreSQL, MySQL, Snowflake), SQL guardrails, model integrity validation, policy-based operation validation, SafetyProvider extension point, MCP server (stdio + streamable HTTP), five built-in domain packs, the v0.2 benchmark framework (six question types, SRB score), docker compose quick start, and the killer demo.
- Planned: JoinLint adapter integration, plugin system, third-party community packs, Snowflake-verified integration, Mode B agent evaluation, and scripts tooling.
Design Documents
Specifications live in docs/; the Obsidian index is
Semantic Runtime.md.
- PRD — positioning, problem, vision, scope
- Protocol Specification — MCP tools, core objects, protocol principles
- Reference Architecture — core modules and integrations
- Data Model Specification — Entity / Relation / Metric / Evidence / Policy
- API & MCP Specification — Python SDK, MCP tools, error model
- Implementation Blueprint — repository layout, milestones
- MVP Demo Design — e-commerce revenue demo
- Open Source Strategy — adoption and ecosystem
- Future Roadmap — Phase 1-5 roadmap
- Post v0.1 Roadmap — Phase 6-10 execution plan, v0.2-v1.0 evolution
- Benchmark Plan v0.2 — six question types, SRB scoring, Mode A/B split
- Validation and Adoption Plan — real-world validation framework, adoption stages
Superseded v0.1 drafts are archived in docs/archive/.
Repository Layout
docs/ design specifications (source of truth)
src/semantic_runtime/ core runtime packages
core/ models/ loaders/ context/ safety/ evidence/ mcp/ connectors/
tests/unit/ unit tests
tests/integration/ integration tests (MCP server, connectors, benchmarks)
benchmarks/ v0.2 framework: runner, scorer, per-domain datasets
examples/ demo semantic models and scripts
scripts/ development tooling (planned)
Development
python -m pip install -e '.[dev]'
python -m pytest -q
python -m ruff check src tests
The repository is uv-managed for reproducible environments:
uv sync --extra dev
uv run pytest -q
MCP Server
Serve any semantic model to MCP clients over stdio:
python -m semantic_runtime.mcp # e-commerce pack
python -m semantic_runtime.mcp path/to/semantic_model.yaml # your model
Exposes five tools: list_entities, describe_entity, get_metric,
resolve_context, and validate_operation. Try it with any MCP client
(e.g. Claude Desktop) pointed at the command above, or connect with the SDK:
from semantic_runtime.core import SemanticRuntime
from semantic_runtime.packs import load_pack
runtime = SemanticRuntime(load_pack("ecommerce"))
context = runtime.resolve_context("Why did revenue drop?")
print(context.matched_terms) # ["revenue"]
Benchmarks
The v0.2 framework (see the Benchmark Plan) evaluates runtime capability with six question types — semantic understanding, entity discovery, relationship reasoning, metric dependency, evidence grounding, and safety validation — and reports a weighted SRB score with a hard safety gate:
python benchmarks/runner.py --domain ecommerce # full run
python benchmarks/runner.py --domain ecommerce --type metric_dependency
python benchmarks/runner.py --domain ecommerce --safety
python benchmarks/runner.py --domain ecommerce --output report.json
Legacy entry points remain available: benchmarks/run_benchmark.py and
benchmarks/run_safety_eval.py.
Docker
docker compose up # serves the e-commerce pack over streamable HTTP on :8000
docker build -t semantic-runtime .
docker run --rm -i semantic-runtime # MCP over stdio, e-commerce pack
For an HTTP endpoint instead of stdio:
python -m semantic_runtime.mcp --http --port 8000
Quick Start (five minutes)
- Install:
pip install 'semantic-runtime[dev]'(oruv sync --extra dev) - Run the MCP server:
python -m semantic_runtime.mcp(stdio, e-commerce pack) - Wire it into Claude Desktop with
examples/claude_desktop_config.example.json
(copy the
mcpServersblock into yourclaude_desktop_config.json); Cursor users add the same block to.cursor/mcp.json - Ask: "Why did revenue decrease last month?"
- Generate the demo database for connector experiments:
python examples/ecommerce/seed_db.py # creates examples/ecommerce/shop.db
Safety
Deterministic safety checks run before any operation; nothing executes
side-effectful SQL. validate defaults to deny: policies must explicitly
allow an action, and SQL guardrails reject multi-statements and
UPDATE/DELETE without WHERE:
runtime.validate("execute.query") # allow=True (policy)
runtime.validate("execute.query", sql="DELETE FROM orders") # allow=False, UNSAFE_DELETE_NO_WHERE
runtime.validate_model() # integrity: relations/metrics resolve
Operation safety runs through a SafetyProvider — inject your own to plug
in external engines (JoinLint adapters implement check_operation):
from semantic_runtime.core import SemanticRuntime
from semantic_runtime.safety import SafetyReport
class MyProvider:
def check_operation(self, action, sql):
return SafetyReport() # safe
runtime = SemanticRuntime.load("model.yaml", safety_provider=MyProvider())
Semantic Packs
Built-in domain semantic models ship with the package:
from semantic_runtime.core import SemanticRuntime
from semantic_runtime.packs import load_pack
runtime = SemanticRuntime(load_pack("ecommerce")) # ecommerce, saas, finance, game, healthcare
Each pack provides entities, relations, metrics, evidence, and policies.
Load a local community pack directory with load_pack("name", base_dir=path).
Demo
python examples/ecommerce/demo.py # e-commerce
python examples/ecommerce/demo.py --pack saas # any built-in pack
python examples/ecommerce/demo.py --pack finance --question "What is the portfolio value?"
python examples/ecommerce/demo.py --mcp # serve over MCP instead
Schema Connectors
Map database schemas into semantic models (tables become entities, foreign keys become relations). SQLite works out of the box; PostgreSQL and MySQL require their extras:
from semantic_runtime.connectors import SQLiteConnector, map_schema
from semantic_runtime.core import SemanticRuntime
schema = SQLiteConnector("shop.db").load_schema()
runtime = SemanticRuntime(map_schema(schema))
pip install 'semantic-runtime[postgres]' # or [mysql]
from semantic_runtime.connectors import PostgresConnector, map_schema
schema = PostgresConnector("postgres://user:pass@localhost/shop").load_schema()
Contributing
See CONTRIBUTING.md for ground rules, setup, and how to propose changes. All participants agree to the Code of Conduct. Report security issues privately per SECURITY.md.
License
MIT — see LICENSE.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。