Daml/Canton Docs MCP

Daml/Canton Docs MCP

Builds and serves local MCP-searchable documentation indexes for Daml, Canton, and related projects, enabling search and query of documentation through MCP tools.

Category
访问服务器

README

Daml/Canton Docs MCP

This repository builds and serves local MCP-searchable documentation indexes for the Daml, Canton, Canton Network, DPM, CN Quickstart, and Splice documentation sources.

The installed command is docs-mcp. It can:

  • sync configured documentation sources into .docs/
  • build SQLite FTS5 indexes for local search
  • query an index from the command line
  • serve an index over stdio or streamable HTTP as an MCP server

The primary docset is daml, which combines:

  • daml-sdk from digital-asset/daml
  • canton from digital-asset/canton
  • dpm from digital-asset/dpm
  • cn-quickstart from digital-asset/cn-quickstart
  • canton-network from docs.canton.network
  • splice from canton-network/splice

Setup

Requirements: Python 3.10+, uv, and Git.

uv sync
uv run docs-mcp list

Build or refresh indexes

Build the combined Daml/Canton index:

uv run docs-mcp update daml \
  --export-dir .docs/daml \
  --db-path .docs/daml/docs_index.db

Build an individual source index by replacing daml with a configured docset, for example canton, daml-sdk, canton-network, or splice.

Generated sources, caches, and indexes live under .docs/ and .cache/ and are ignored by Git.

Use through mcporter

This is the expected usage path for agents: register the daml docs server with mcporter, then call the generated tools on demand instead of loading the MCP server directly into every session.

Add a server entry to ~/.mcporter/mcporter.json or to a project-local config/mcporter.json. Use absolute paths because mcporter may start the server outside this checkout.

{
  "mcpServers": {
    "daml": {
      "command": "/absolute/path/to/uv",
      "args": [
        "run",
        "--directory",
        "/absolute/path/to/daml-docs-mcp",
        "docs-mcp",
        "--root",
        "/absolute/path/to/daml-docs-mcp",
        "serve",
        "daml",
        "--export-dir",
        "/absolute/path/to/daml-docs-mcp/.docs/daml",
        "--db-path",
        "/absolute/path/to/daml-docs-mcp/.docs/daml/docs_index.db"
      ]
    }
  }
}

Verify the registration and call the search tool:

mcporter list daml --schema
mcporter call daml.search_daml --args '{"query":"contract keys","scope":"chunks","limit":8}'

Refresh the index through the same registered server:

mcporter call daml.refresh_daml_index

Query locally

uv run docs-mcp query daml \
  --db-path .docs/daml/docs_index.db \
  --scope chunks \
  --limit 8 \
  "contract keys"

Combined daml results prefix categories with their member docset, such as canton:sdk, so callers can tell which source matched.

Serve as MCP

Serve over stdio for an MCP client:

uv run docs-mcp serve daml \
  --db-path /absolute/path/to/daml-docs-mcp/.docs/daml/docs_index.db

Serve over streamable HTTP:

uv run docs-mcp serve daml \
  --db-path .docs/daml/docs_index.db \
  --transport streamable-http \
  --port 8765

MCP client configs should use absolute paths for this repository and for --db-path, because clients may start the server from a different working directory.

Configurations

Docsets are configured in configs/*.json. configs/daml.json is the combined index; the other Daml/Canton-related files define the source repositories, website source, public URL mapping, and file suffixes copied into the export.

configs/hermes.json, configs/claude_code.json, and configs/template.json remain from the upstream docs MCP template and are not part of the Daml/Canton package workflow.

Development checks

Run these before changing CLI, export, indexing, or MCP behavior:

uv run ruff format --check .
uv run ruff check .
uv run mypy
uv run python -m unittest discover -s tests -v

Project map

  • docs_mcp/cli.py: docs-mcp command entry point.
  • scripts/sync_docset.py: syncs sources and rebuilds exports/indexes.
  • scripts/export_docs.py: copies docs and writes sitemap/export files.
  • scripts/build_fts_index.py: builds SQLite FTS5 indexes.
  • scripts/query_fts.py: queries indexes from the CLI.
  • scripts/docs_mcp_server.py: serves MCP tools.
  • configs/: docset configuration files.
  • tests/: regression tests.

License

MIT. See LICENSE.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选