skore-mcp
Community MCP server for Skore that exposes tools for projects, evaluate, compare, train_test_split, configuration, and a dispatcher for report methods like metrics, inspection, and data analysis.
README
Skore MCP server
Community MCP server for Skore — not affiliated with Probabl. It exposes MCP tools for projects, evaluate / compare / train_test_split, global configuration, and a skore_report_call dispatcher that covers the report surface documented in the Skore API (e.g. ComparisonReport.get_predictions, metrics, inspection, data.analyze). Call skore_api_catalog for the exact allowlisted method names per accessor.
Repository: github.com/fanfcorp/skore-mcp
Requirements
- Python 3.10+ (same as Skore 0.15)
- Dependencies:
skore,mcp[cli],pandas(seepyproject.toml)
Install
From PyPI (after the package is published):
python3.12 -m venv .venv
source .venv/bin/activate
pip install skore-mcp
From GitHub (any time, no PyPI needed):
pip install "skore-mcp @ git+https://github.com/fanfcorp/skore-mcp.git"
From a local clone (editable for development):
cd "/path/to/skore-mcp"
python3.12 -m venv .venv
source .venv/bin/activate
pip install -e .
After install, run the server as skore-mcp or python -m skore_mcp (stdio MCP).
Cursor / Claude Desktop
Add a stdio server (use your real paths):
{
"mcpServers": {
"skore": {
"command": "/path/to/MCP Skore/.venv/bin/python",
"args": ["-m", "skore_mcp"],
"env": {
"SKORE_WORKSPACE": "/path/to/your/skore/workspace"
}
}
}
}
Alternatively, after pip install into an environment:
{
"mcpServers": {
"skore": {
"command": "skore-mcp"
}
}
}
Tools
| Tool | Purpose |
|---|---|
skore_info |
Skore version and mode hints |
skore_api_catalog |
JSON allowlists for skore_report_call (accessors + method names) |
skore_hub_login |
Hub auth for the current process (optional api_key) |
skore_project_summarize |
CSV of Project.summarize() |
skore_report_metrics |
Shortcut: metrics summary CSV for one report id |
skore_evaluate_csv |
skore.evaluate on a CSV; returns session_report_key; optional put into a project |
skore_project_delete |
Delete a local/hub project |
skore_show_versions |
skore.show_versions() output |
skore_configuration_get / skore_configuration_set |
Read/write skore.configuration |
skore_train_test_split_csv |
skore.train_test_split on a CSV → train/test CSV blobs |
skore_estimator_report_from_split_csv |
Build EstimatorReport from CSV; returns session_report_key |
skore_compare_persisted_reports |
skore.compare on reports from a Project |
skore_compare_session_reports |
skore.compare on in-memory session reports |
skore_report_call |
Call get_predictions, cache_predictions, metrics.*, inspection.*, data.*, etc. |
skore_session_release |
Drop a session_report_key from memory |
Session keys
skore_evaluate_csv always registers the report in-memory and returns session_report_key. Use that with skore_report_call (and skore_compare_session_reports) without persisting to a project. Persisted reports use project_name + report_id (id from summarize) instead.
API coverage
Skore’s Python API is large (many classes and plot objects). This server maps one tool (skore_report_call) to the methods Skore exposes on reports and accessors, with an explicit allowlist so behavior stays predictable. Plots are returned as base64 PNG and tables as CSV in JSON when serialization supports it. It is not a line-for-line duplicate of every overload in the docs, but it covers the public patterns for reports, metrics, inspection, and data analysis.
Hub projects use project_name like workspace_slug/project_slug per Skore docs. Call skore_hub_login (or your hub plugin’s env vars) before hub operations.
Notes
- On SQLite 3.41+, the server applies a small compatibility patch for
diskcache(used by local Skore storage) so local projects work on current macOS/Python builds. - Logs go to stderr; do not print to stdout when using stdio MCP.
License
This project is licensed under the MIT License — see LICENSE. Skore and other dependencies remain under their own licenses.
Publish or clone from GitHub
PyPI via Trusted Publishing (recommended)
The repo includes .github/workflows/publish.yml. On PyPI → skore-mcp → Publishing (or when creating the project), add a pending publisher:
| Field | Value |
|---|---|
| Owner | fanfcorp (or your GitHub org/user) |
| Repository | skore-mcp |
| Workflow name | publish.yml |
| Environment | (leave empty unless you add environment: pypi to the job) |
Then merge the workflow on main, bump the version in pyproject.toml / skore_mcp/__init__.py, and create a GitHub Release (or run the workflow manually with Actions → Publish to PyPI → Run workflow). The release event triggers the upload; no long-lived PYPI_API_TOKEN is required.
Clone
After cloning:
git clone https://github.com/fanfcorp/skore-mcp.git
cd skore-mcp
python3.12 -m venv .venv && source .venv/bin/activate
pip install -e .
To push updates (replace the remote URL if your fork or username differs):
git remote add origin https://github.com/fanfcorp/skore-mcp.git
git branch -M main
git push -u origin main
Or create the repo and push in one step (with GitHub CLI authenticated):
gh repo create fanfcorp/skore-mcp --public --source=. --remote=origin --push
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。