Conan MCP

What conan-io/conan-mcp MCP server does

The conan-io/conan-mcp MCP server exposes common Conan package-management tasks through MCP tools. It is intended for C and C++ development workflows where an agent needs to create project files, resolve dependencies, inspect package availability, or review dependency metadata.

Project generation supports library and executable templates for CMake, Meson, MSBuild, Bazel, and Autotools. A generated project can include regular requirements and tool requirements, such as build-system packages. The creation operation accepts a project name, optional version, working directory, and an overwrite flag.

How it works

The server runs as a local MCP process and uses an installed Conan executable to perform package-manager operations. Paths supplied to dependency operations are resolved relative to the requested working directory. This applies to project folders as well as conanfile.txt and conanfile.py files.

Package searches can query the local cache, configured remotes, or both. Search parameters include package name, version or version range, user, channel, recipe revision, package ID, settings, options, and remote. Dependency installation can select a remote, restrict resolution to the cache, override host settings and options, and optionally build missing binaries from source.

The conan-io/conan-mcp MCP server uses Conan graph information for license collection. License analysis covers packages in the host context and excludes build-context tools. Vulnerability scanning can inspect a project dependency graph or audit one specific Conan reference; a path and a package reference cannot be used together.

Setup and configuration

Python 3.10 or newer and Conan are required. The documented MCP configuration runs the package with uvx:

{
  "mcpServers": {
    "conan": {
      "command": "uvx",
      "args": ["conan-mcp"]
    }
  }
}

By default, Conan is located through the system PATH or the environment in which the MCP process runs. Set CONAN_MCP_CONAN_PATH when a particular Conan executable or virtual-environment installation must be used. For local development, the repository instructions use uv sync followed by uv run conan-mcp.

Tools and capabilities

Available operations cover:

• Reading the default or a named Conan profile and listing available profiles.
• Creating projects from supported library and executable templates.
• Searching recipes and binary packages with Conan cache, remote, revision, settings, and option filters.
• Installing dependencies and producing a dependency graph.
• Collecting dependency license information for host packages.
• Scanning a project or individual package reference for known security vulnerabilities.

The conan-io/conan-mcp MCP server also exposes the underlying input fields used by these operations, including template, name, version, requirements, tool requirements, working directory, force, profile, remote, path, and package-selection filters.