Skip to main content
Glama

project_create

Create a new Railway project to start applications, set up development environments, or establish project spaces for deployment.

Instructions

[API] Create a new Railway project

⚡️ Best for: ✓ Starting new applications ✓ Setting up development environments ✓ Creating project spaces

⚠️ Not for: × Duplicating existing projects

→ Next steps: service_create_from_repo, service_create_from_image, database_deploy

→ Related: project_delete, project_update

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new project
teamIdNoOptional team ID to create the project under

Implementation Reference

  • The core handler for the 'project_create' MCP tool. This createTool invocation defines the tool's metadata, Zod input schema (name and optional teamId), and the executor function that invokes projectService.createProject to perform the actual project creation.
      "project_create",
      formatToolDescription({
        type: 'API',
        description: "Create a new Railway project",
        bestFor: [
          "Starting new applications",
          "Setting up development environments",
          "Creating project spaces"
        ],
        notFor: [
          "Duplicating existing projects",
        ],
        relations: {
          nextSteps: [
            "service_create_from_repo",
            "service_create_from_image",
            "database_deploy"
          ],
          related: ["project_delete", "project_update"]
        }
      }),
      {
        name: z.string().describe("Name for the new project"),
        teamId: z.string().optional().describe("Optional team ID to create the project under")
      },
      async ({ name, teamId }) => {
        return projectService.createProject(name, teamId);
      }
    ),
  • Zod schema defining the input parameters for the project_create tool: required 'name' string and optional 'teamId' string.
    {
      name: z.string().describe("Name for the new project"),
      teamId: z.string().optional().describe("Optional team ID to create the project under")
    },
  • Registers the projectTools array (containing project_create) along with other tools to the MCP server via server.tool() calls.
    export function registerAllTools(server: McpServer) {
      // Collect all tools
      const allTools = [
        ...databaseTools,
        ...deploymentTools,
        ...domainTools,
        ...projectTools,
        ...serviceTools,
        ...tcpProxyTools,
        ...variableTools,
        ...configTools,
        ...volumeTools,
        ...templateTools,
      ] as Tool[];
    
      // Register each tool with the server
      allTools.forEach((tool) => {
        server.tool(
          ...tool
        );
      });
    } 
  • Helper method in ProjectService called by the tool handler. Performs the API call to create the project via this.client.projects.createProject and formats the response.
    async createProject(name: string, teamId?: string): Promise<CallToolResult> {
      try {
        const project = await this.client.projects.createProject(name, teamId);
    
        return createSuccessResponse({
          text: `Created new project "${project.name}" (ID: ${project.id})`,
          data: project
        });
      } catch (error) {
        return createErrorResponse(`Error creating project: ${formatError(error)}`);
      }
    }
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 of behavioral disclosure. It effectively communicates that this is a creation operation (implies mutation/write), mentions what it's best for and what it's not for, and provides next steps. However, it doesn't explicitly mention permissions, rate limits, or error conditions that might be relevant 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 well-structured with clear sections (purpose, best for, not for, next steps, related tools). Every sentence earns its place by providing specific guidance without unnecessary verbiage. The use of symbols (⚡️, ⚠️, →) enhances readability while maintaining conciseness.

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?

For a creation tool with no annotations and no output schema, the description provides strong contextual guidance about when to use it, what it's not for, and next steps. However, it doesn't describe what the tool returns or potential error conditions, which would be helpful given the absence of an output schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents both parameters (name and teamId). The description doesn't add any additional parameter information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without adding extra value.

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 explicitly states 'Create a new Railway project' which is a specific verb+resource action. It clearly distinguishes this from sibling tools like project_delete, project_update, and project_list by focusing on creation rather than modification or deletion operations.

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

Usage Guidelines5/5

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

The description provides explicit guidance with 'Best for' and 'Not for' sections, clearly indicating when to use this tool (starting new applications, setting up development environments) and when not to use it (duplicating existing projects). It also lists next steps and related tools, providing clear alternatives and context.

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/epitaphe360/railway-mcp'

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