Cosmos Semantic

Name: Cosmos Semantic
Author: WiliamRosa

作者：WiliamRosa版本 0.3.0i★ –i在你的电脑上运行

注册名称io.github.WiliamRosa/cosmos-semantic

安装

概览

作者提供的说明（英文原文）

Governed metrics, business rules and a glossary for AI agents, with evidence on every answer.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 278/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：COSMOS_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： COSMOS_API_KEY, COSMOS_DEV_API_KEYS

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "cosmos-semantic": {
      "command": "uvx",
      "args": [
        "cosmos-semantic",
        "mcp",
        "--model",
        "--connections"
      ],
      "env": {
        "COSMOS_API_KEY": "your-value",
        "COSMOS_DEV_API_KEYS": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add cosmos-semantic --env COSMOS_API_KEY=your-value --env COSMOS_DEV_API_KEYS=your-value -- uvx cosmos-semantic mcp --model --connections

运行前请先填写空着的值。

这个服务器需要在启动命令中填入值，请复制设置后自行填写。

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "cosmos-semantic": {
      "command": "uvx",
      "args": [
        "cosmos-semantic",
        "mcp",
        "--model",
        "--connections"
      ],
      "env": {
        "COSMOS_API_KEY": "your-value",
        "COSMOS_DEV_API_KEYS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器需要在启动命令中填入值，请复制设置后自行填写。

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "cosmos-semantic": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "cosmos-semantic",
        "mcp",
        "--model",
        "--connections"
      ],
      "env": {
        "COSMOS_API_KEY": "your-value",
        "COSMOS_DEV_API_KEYS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

COSMOS_API_KEY 机密必填 env
The caller's key; its user context feeds the model's row filters
COSMOS_DEV_API_KEYS env
YAML file with development keys (local use); production uses an OIDC provider

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 WiliamRosa 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18590 个服务器的 0%
发布到注册中心的时间比此分类中其他 18590 个服务器的 92% 更新
基础检查结果等于或优于此分类中其他 18590 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Cosmos Semantic 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：COSMOS_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.3.0）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, render.ai Presentations

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

render.ai Presentations

Create, edit, preview and export designed, editable presentations from a brief or outline.

作者：render.ai今天更新

在云端运行✓ render.ai

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Cosmos Semantic

An open-source semantic layer with an ontology at its core, so AI agents and apps get the same number on every database, with the proof in every answer.

[Live demo of the console](https://wiliamrosa.github.io/cosmos-semantic-platform/) · Quickstart · Docs · Article (em português)

AI agents that write SQL over raw tables return numbers that look right and that nobody can explain: "revenue" has three definitions, "active customer" means 60 days to one team and 90 to another. Cosmos Semantic defines metrics, business rules and concepts once, serves them to agents over MCP instead of letting them guess SQL, and attaches evidence to every answer.


Multi-database	One model, the same number on Databricks, Snowflake, Oracle, SQL Server, Postgres, MySQL, MariaDB and DuckDB, checked by the test suite on every change
Ontology	A bilingual business glossary (SKOS), versioned business rules with owners and tests, and a knowledge graph of teams, systems and processes
Built for AI agents	A native MCP server: agents find the concept, ask for a governed metric and get deterministic SQL; personal data never reaches them
Verifiable numbers	Every answer carries the expanded formula, rules, row filters, reference date and hashes; `cosmos replay` tells whether a number changed and why
Reconciliation	Compares a governed metric with the legacy SQL a team already uses and names the likely cause of each divergence
Open, no lock-in	Apache 2.0, its own engine, and import from dbt, Power BI, Cube and Apache Ossie

The YAML format uses the dbt Semantic Layer vocabulary and ships a JSON Schema; Cube and dbt are import sources and export targets, not dependencies. The core is Apache 2.0 within an open-core model (ADR 0005).

Status: phases 0 to 3 are implemented: the engine, the ontology (glossary and business rules), the REST API, the MCP server, OIDC identity, verifiable numbers (evidence, replay, reconciliation, impact, bootstrap), business context (rule versions, usage and cost, knowledge graph, Power BI import, AI-assisted discovery, the retail pack, SKOS export) and the read-only console. See the roadmap.

Quickstart

pip install "cosmos-semantic[duckdb,testdata]"

cosmos init demo && cd demo cosmos demo-data cosmos query revenue average_order_value --by orders.status --evidence cosmos explain rule:active_customer

That is a governed metric with its evidence (formula, rules, policies, as_of and hashes) in about a minute, on a local DuckDB file. The quickstart continues with business rules, row filters, personal data and connecting an AI agent over MCP. Extras: duckdb, postgres, sqlserver, mysql (MySQL and MariaDB), oracle, databricks, snowflake, server (REST and MCP), ai (cosmos suggest), testdata.

Console

cosmos serve also serves a read-only console at /console, in English or Portuguese, for people who decide rather than build:

metric health and ownership;
business processes as graphs colored by health;
the catalog in business words;
every audited answer, with a button to reproduce it;
usage and cost per agent.

cosmos check records rule tests and reconciliations against legacy reports, so the console shows health over time.

Development

Requires Python 3.11+ and uv. From a clone of this repository:

uv sync --all-extras

Generate synthetic e-commerce data into a local DuckDB (data/ecommerce.duckdb)

uv run cosmos demo-data -c examples/ecommerce/connections.yml # --locale pt_BR for Brazilian data with CPF

Validate the example model

uv run cosmos validate -m examples/ecommerce/semantic

Revenue and average order value by status

uv run cosmos query revenue average_order_value --by orders.status \ -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

Same query as CSV (raw values, header + one row per result row) for spreadsheets and scripts

uv run cosmos query revenue average_order_value --by orders.status --csv \ -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

Metrics from different models, with the user's row filter; --show-sql prints the generated SQL

uv run cosmos query revenue paid_value customer_count --by customers.region -u region=Midwest --show-sql \ -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

Business rules as a filter and as a grouping; --as-of pins "today"

uv run cosmos query customer_count --where "{rule.active_customer}" --by customers.segment \ -u region=Northeast --as-of 2026-10-22 -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

Evidence envelope: formulas, rules, policies, as_of and hashes; then replay the audited query

export COSMOS_AUDIT_LOG=data/audit.jsonl uv run cosmos query average_order_value --by customers.segment --where "{rule.active_customer}" -u region=Northeast --evidence -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml uv run cosmos replay -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

Reconcile a governed metric with legacy SQL or another model, and explain the divergence

uv run cosmos reconcile revenue --by orders.status --sql legacy_revenue.sql -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml uv run cosmos reconcile --cases examples/ecommerce/divergence_zoo.yml -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

What a change affects, and who queried it (also: --changes-from )

uv run cosmos impact rule:active_customer -m examples/ecommerce/semantic --audit data/audit.jsonl

Past numbers under the rule in effect then, or under today's rule

uv run cosmos query customer_count -w "{rule.active_customer}" --as-of 2026-06-30 --rules-as-of 2026-10-23 -u region=Midwest -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

Usage and estimated cost per metric, user, agent and data source (rates: `cost` in connections.yml)

uv run cosmos usage --audit data/audit.jsonl -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml

The business knowledge graph: owners, source systems and processes (Mermaid, DOT or JSON)

uv run cosmos graph --focus process:order_to_cash -m examples/ecommerce/semantic uv run cosmos impact system:payment_gateway -m examples/ecommerce/semantic

AI-assisted discovery: concepts, rules, metrics and descriptions, validated by the engine, for review

(repeat --source to require that each suggestion runs on every database the model serves)

uv run cosmos suggest --source local -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml -o suggestions.yml

Industry pack mapped onto your tables by name (draft + report for review)

uv run cosmos pack list uv run cosmos pack apply retail --source local --schema public -c examples/ecommerce/connections.yml -o semantic/retail.yml

The business glossary as SKOS/RDF for data catalogs (turtle, jsonld or ntriples)

uv run cosmos export skos -m examples/ecommerce/semantic -o glossary.ttl --base https://data.example.com/glossary/

Draft a model from the database catalog (keys, joins, measures, LGPD suggestions), then review it

uv run cosmos bootstrap -c examples/ecommerce/connections.yml -o semantic/draft.yml

Business rule examples (on DuckDB, without touching the data sources) and reference queries

uv run cosmos test -m examples/ecommerce/semantic uv run cosmos reference

Import models from other tools

uv run cosmos import cube path/to/model -o semantic/imported.yml uv run cosmos import dbt path/to/dbt/models --schema analytics -o semantic/dbt.yml uv run cosmos import ossie model.yaml -o semantic/ossie.yml uv run cosmos import powerbi model.bim -o semantic/powerbi.yml # or a TMDL folder

REST API and MCP

cosmos serve starts the REST API at /v1 and the MCP server at /mcp in the same process; interactive docs are at /docs.

# Production: tokens from the OIDC provider (Cosmos only validates, never issues)

export COSMOS_OIDC_ISSUER=https://login.microsoftonline.com/ /v2.0 export COSMOS_OIDC_AUDIENCE=api://cosmos-semantic

Development: API keys bound to a fixed context (a file with `keys: { : {subject, user}}`)

export COSMOS_DEV_API_KEYS=dev-keys.yml

uv run cosmos serve -m examples/ecommerce/semantic -c examples/ecommerce/connections.yml curl -X POST localhost:8080/v1/query -H "X-API-Key: " -H "content-type: application/json" \ -d '{"metrics": ["revenue"], "dimensions": ["customers.segment"]}'

Remote MCP clients use /mcp as an OAuth protected resource: requests without a valid token get HTTP 401 with a WWW-Authenticate header pointing to /.well-known/oauth-protected-resource, which names the identity provider (set COSMOS_PUBLIC_URL behind a proxy).

For local MCP clients (Claude Desktop, Claude Code), use the stdio transport: cosmos mcp -m ... -c ... with COSMOS_API_KEY set. The tools are search_concepts, explain, list_members, query and show_sql. Every call runs as the user who owns the token; personal data never reaches agents.

Data sources

Local Postgres: docker compose -p cosmos-semantic -f deploy/docker-compose.yml up -d, then cosmos demo-data --target postgres and cosmos reference --source postgres. To also run the tests on Postgres, set COSMOS_PG_URI=postgresql://cosmos:cosmos@localhost:15432/cosmos.

Local SQL Server: docker compose -p cosmos-semantic -f deploy/docker-compose.yml --profile sqlserver up -d and COSMOS_MSSQL_URI='mssql+pymssql://sa:Cosmos!Passw0rd@localhost:14330/master'. Every data source accepts a schema_map in connections.yml (for example public: dbo) to use the same model with different schemas.

Local MySQL, MariaDB and Oracle Database Free: docker compose -p cosmos-semantic -f deploy/docker-compose.yml --profile mysql --profile mariadb --profile oracle up -d,

只显示了开头部分；其余内容请在仓库中阅读

Cosmos Semantic

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

render.ai Presentations

作者的 README

Cosmos Semantic

Quickstart

Console

Development

Generate synthetic e-commerce data into a local DuckDB (data/ecommerce.duckdb)

Validate the example model

Revenue and average order value by status

Same query as CSV (raw values, header + one row per result row) for spreadsheets and scripts

Metrics from different models, with the user's row filter; --show-sql prints the generated SQL

Business rules as a filter and as a grouping; --as-of pins "today"

Evidence envelope: formulas, rules, policies, as_of and hashes; then replay the audited query

Reconcile a governed metric with legacy SQL or another model, and explain the divergence

What a change affects, and who queried it (also: --changes-from )

Past numbers under the rule in effect then, or under today's rule

Usage and estimated cost per metric, user, agent and data source (rates: cost in connections.yml)

The business knowledge graph: owners, source systems and processes (Mermaid, DOT or JSON)

AI-assisted discovery: concepts, rules, metrics and descriptions, validated by the engine, for review

(repeat --source to require that each suggestion runs on every database the model serves)

Industry pack mapped onto your tables by name (draft + report for review)

The business glossary as SKOS/RDF for data catalogs (turtle, jsonld or ntriples)

Draft a model from the database catalog (keys, joins, measures, LGPD suggestions), then review it

Business rule examples (on DuckDB, without touching the data sources) and reference queries

Import models from other tools

REST API and MCP

Development: API keys bound to a fixed context (a file with keys: { : {subject, user}})

Data sources

Usage and estimated cost per metric, user, agent and data source (rates: `cost` in connections.yml)

Development: API keys bound to a fixed context (a file with `keys: { : {subject, user}}`)