MCP.so
登录

Cartograph MCP Server

@benteigland11

基本信息

分类

其他

传输方式

stdio

作者

benteigland11

提交者

Ben Teigland

关于 Cartograph MCP Server

Local First MCP for making your AI generated code reusable and improvable across projects.

#vibecoding#reuse#store#memory

Cartograph MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "cartograph": {
      "command": "cartograph-mcp",
      "args": [],
      "description": "Local-first reusable code registry for AI agents",
      "homepage": "https://github.com/benteigland11/cartograph-mcp"
    }
  }
}

Cartograph MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Cartograph?

Cartograph is an MCP server that exposes a focused set of Cartograph widget workflow tools for AI agents. It provides search, inspect, install, create, validate, check-in, and configuration actions without mirroring the entire CLI, keeping the agent-facing surface compact and task-oriented.

How to use Cartograph?

Install via pip install cartograph-mcp, then configure it as an MCP server in your client (e.g., Claude Desktop, Claude Code, Codex, Gemini CLI, or Cursor) by pointing to the cartograph-mcp command. The server delegates to the underlying cartograph-cli for all operations.

Key features of Cartograph

  • Exposes registry widget actions: search, inspect, install, rate
  • Manages installed widgets: upgrade, uninstall
  • Provides widget status, creation, validation, and check-in tools
  • Reads and writes core Cartograph configuration defaults
  • Groups tool surface around agent intents rather than CLI mirroring
  • Falls back to the full CLI for administrative and recovery operations

Use cases of Cartograph

  • Search and inspect reusable widgets before writing new logic
  • Install, upgrade, or uninstall widgets within a project
  • Create, validate, and check in new widgets with a dry-run pipeline
  • Adjust daily workflow defaults like auto-publish, visibility, and governance

常见问题

1

How does Cartograph differ from the full Cartograph CLI?

The MCP intentionally exposes only the daily widget workflow surface (search, install, create, validate, check-in, config). Administrative, recovery, and cloud operations remain in the `cartograph` CLI.

2

What are the runtime dependencies of Cartograph?

The `cartograph-mcp` package depends on `cartograph-cli` and shells out to it as the source of truth for all command execution.

3

How is data isolation handled during testing or development?

Integration tests isolate `HOME`, `XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_CACHE_HOME`, `WIDGET_LIBRARY_PATH`, and the project working directory so they do not touch real widget libraries or user configuration.

4

What configuration defaults does Cartograph expose?

The `cartograph_config` tool exposes `auto-publish`, `visibility`, `governance`, `cloud`, `show-unavailable`, and `publish-registry` settings, read and written through the CLI's `--json` path.

5

How is Cartograph tested?

It has two test layers: command-contract tests that mock the CLI runner and verify exact commands, and isolated integration tests that run the real Cartograph CLI in a temporary environment.

评论

其他 分类下的更多 MCP 服务器