Skip to main content
Glama
conan-io

Conan MCP Server

Official
by conan-io

create_conan_project

Create a new Conan project with specified dependencies and build system templates. Set up libraries or executables quickly by providing project name, version, and required packages.

Instructions

Create a new Conan project with specified dependencies.

This tool creates a new Conan project using templates and automatically adds
the specified dependencies. Useful for setting up new projects with common
libraries like fmt, openssl, boost, etc.

Note: The generated code contains placeholder examples. You need to review
and update: includes/imports, source code usage, and build system targets
(CMakeLists.txt, meson.build, etc.) to properly use your specified dependencies.

Args:
    template: Template type for the project.
              
              Libraries (produce libraries to be linked):
              - cmake_lib: CMake library (default for libraries)
              - header_lib: Header-only library
              - meson_lib: Meson build system
              - msbuild_lib: Visual Studio / MSBuild (Windows only)
              - bazel_lib: Bazel build system (experimental)
              - autotools_lib: Autotools (configure/make)
              
              Executables (programs that can be run):
              - cmake_exe: CMake executable (default for executables)
              - meson_exe: Meson build system
              - msbuild_exe: Visual Studio / MSBuild (Windows only)
              - bazel_exe: Bazel build system (experimental)
              - autotools_exe: Autotools (configure/make)
              
              Note: If the user doesn't specify build system, use cmake_lib
              for libraries or cmake_exe for executables as defaults.
    name: Name of the project
    version: Version of the project (default: "0.1")
    requires: List of dependencies with versions (e.g., ['fmt/12.0.0', 
              'openssl/3.6.0'])
    tool_requires: List of tool dependencies with versions. Common examples:
                  - ['cmake/4.1.2'] - CMake build tool
                  - ['ninja/1.13.1'] - Ninja build system
                  - ['meson/1.9.1'] - Meson build system
    work_dir: Working directory where the command should be executed. 
             The project will be created directly in this directory.
             Always required.
    force: Overwrite existing files if they exist (default: False)

Returns:
    Dictionary containing:
    - result: Success message with project details, dependency note, and 
              raw output from the conan new command

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateYesTemplate type for the project. If not specified, use cmake_lib for libraries or cmake_exe for executables
nameYesName of the project
versionNoVersion of the project0.1
requiresNoList of dependencies with versions
tool_requiresNoList of tool dependencies with versions. Common examples: ['cmake/4.1.2'], ['ninja/1.13.1'], ['meson/1.9.1']
work_dirYesWorking directory where the command should be executed. The project will be created directly in this directory. Always required.
forceNoOverwrite existing files if they exist
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It reveals that generated code contains placeholder examples requiring user review, and the force parameter controls overwriting. It also specifies where the project is created (work_dir). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with front-loaded purpose, a note section, and clear 'Args' and 'Returns' sections. It is somewhat verbose but includes necessary details for template options and examples, earning its sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description documents the return dictionary. It covers all 7 parameters with detailed explanations, behavioral notes, and usage context. Minor omission: does not mention prerequisites like having Conan installed, but overall complete for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value beyond schema by categorizing template types (libraries vs executables) and providing default choices. It also gives common examples for tool_requires, enhancing understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new Conan project with specified dependencies. It distinguishes itself from siblings by focusing on project creation, while siblings like install_conan_packages or list_conan_packages handle other lifecycle tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains it is useful for setting up new projects with common libraries and includes a note about placeholder examples requiring user updates. However, it does not explicitly state when not to use this tool or mention alternative siblings for specific scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conan-io/conan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server