Skip to main content
Glama

create_project

Create a new REAPER project with specified tempo and time signature, setting the foundation for your audio production.

Instructions

Create a new REAPER project with the given tempo and time signature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tempoNo
time_signatureNo4/4
nameNo

Implementation Reference

  • The create_project tool handler: creates a new REAPER project using RPR.Main_OnCommand(41929), sets tempo and time signature via reapy, then returns success/failure.
    def create_project(tempo: float = 120.0, time_signature: str = "4/4", name: str = "") -> dict:
        """Create a new REAPER project with the given tempo and time signature."""
        try:
            RPR.Main_OnCommand(41929, 0)  # File: New project
            project = get_project()
            project.bpm = tempo
            if time_signature:
                num, denom = map(int, time_signature.split("/"))
                project.time_signature = (num, denom)
            return {
                "success": True,
                "name": name or f"New Project {time.strftime('%Y-%m-%d %H-%M-%S')}",
                "tempo": project.bpm,
                "time_signature": time_signature,
            }
        except Exception as e:
            logger.error(f"create_project failed: {e}")
            return {"success": False, "error": str(e)}
  • The register_tools function that wraps create_project with the @mcp.tool() decorator, registering it as an MCP tool.
    def register_tools(mcp):
    
        @mcp.tool()
        def create_project(tempo: float = 120.0, time_signature: str = "4/4", name: str = "") -> dict:
            """Create a new REAPER project with the given tempo and time signature."""
            try:
                RPR.Main_OnCommand(41929, 0)  # File: New project
                project = get_project()
                project.bpm = tempo
                if time_signature:
                    num, denom = map(int, time_signature.split("/"))
                    project.time_signature = (num, denom)
                return {
                    "success": True,
                    "name": name or f"New Project {time.strftime('%Y-%m-%d %H-%M-%S')}",
                    "tempo": project.bpm,
                    "time_signature": time_signature,
                }
            except Exception as e:
                logger.error(f"create_project failed: {e}")
                return {"success": False, "error": str(e)}
  • The server.py imports and calls register_tools from project_tools to register create_project on the FastMCP instance.
    from reaper_mcp.project_tools import register_tools as _reg_project
    from reaper_mcp.track_tools import register_tools as _reg_track
    from reaper_mcp.midi_tools import register_tools as _reg_midi
    from reaper_mcp.fx_tools import register_tools as _reg_fx
    from reaper_mcp.audio_tools import register_tools as _reg_audio
    from reaper_mcp.mixing_tools import register_tools as _reg_mixing
    from reaper_mcp.render_tools import register_tools as _reg_render
    from reaper_mcp.mastering_tools import register_tools as _reg_mastering
    from reaper_mcp.analysis_tools import register_tools as _reg_analysis
    
    _reg_project(mcp)
    _reg_track(mcp)
    _reg_midi(mcp)
    _reg_fx(mcp)
    _reg_audio(mcp)
    _reg_mixing(mcp)
    _reg_render(mcp)
    _reg_mastering(mcp)
    _reg_analysis(mcp)
  • The get_project helper used by create_project to obtain the current REAPER project object via reapy.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
  • The function signature defines the schema: tempo (float, default 120.0), time_signature (str, default "4/4"), name (str, default "") as inputs, and returns a dict.
    def create_project(tempo: float = 120.0, time_signature: str = "4/4", name: str = "") -> dict:
Behavior1/5

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

No annotations provided. The description does not disclose side effects (e.g., closing current project, unsaved changes lost), prerequisites, or whether the operation is destructive. This is a significant gap for a creation tool.

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

Conciseness5/5

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

The description is a single, clear sentence with zero unnecessary words. It efficiently communicates the core action and key parameters.

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

Completeness2/5

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

Despite the tool's apparent simplicity, the description fails to address critical context: what happens to the current project, whether the user is prompted to save, the return value (e.g., new project ID), and any dependencies. With no output schema or annotations, this leaves significant ambiguity.

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

Parameters2/5

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

Schema coverage is 0% (no parameter descriptions). The description only mentions tempo and time signature but omits the 'name' parameter. It also does not specify allowed formats for time_signature (e.g., '4/4' string). Thus, it insufficiently compensates for the missing schema descriptions.

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 it creates a new REAPER project, specifying tempo and time signature. This distinguishes it from siblings like load_project (loading) and set_tempo/set_time_signature (modifying existing projects).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. It does not mention that creating a new project may close the current unsaved project, nor does it differentiate from set_tempo for existing projects.

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/bonfire-audio/reaper-mcp'

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