Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

create_project

Generate and initialize a new project by specifying its name and identifier through the Plane MCP Server. Simplifies project setup for efficient management in AI-driven workflows.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesThe identifier of the project. This is typically a word of around 5 characters derived from the name of the project in uppercase.
nameYesThe name of the project

Implementation Reference

  • Direct registration of the 'create_project' tool on the MCP server, including schema and handler function.
    server.tool(
      "create_project",
      "Create a new project",
      {
        name: z.string().describe("The name of the project"),
        identifier: z
          .string()
          .max(7)
          .describe(
            "The identifier of the project. This is typically a word of around 5 characters derived from the name of the project in uppercase."
          ),
      },
      async ({ name, identifier }) => {
        const project = await makePlaneRequest("POST", `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/`, {
          name,
          identifier: identifier.toUpperCase().replaceAll(" ", ""),
        });
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(project, null, 2),
            },
          ],
        };
      }
    );
  • The handler logic for creating a project by making a POST request to the Plane API endpoint using the makePlaneRequest helper.
    async ({ name, identifier }) => {
      const project = await makePlaneRequest("POST", `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/`, {
        name,
        identifier: identifier.toUpperCase().replaceAll(" ", ""),
      });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(project, null, 2),
          },
        ],
      };
    }
  • Zod-based input schema defining 'name' and 'identifier' parameters for the tool.
    {
      name: z.string().describe("The name of the project"),
      identifier: z
        .string()
        .max(7)
        .describe(
          "The identifier of the project. This is typically a word of around 5 characters derived from the name of the project in uppercase."
        ),
    },
  • Utility function makePlaneRequest used by the handler to perform authenticated HTTP requests to the Plane API.
    export async function makePlaneRequest<T>(method: string, path: string, body: any = null): Promise<T> {
      const hostUrl = process.env.PLANE_API_HOST_URL || "https://api.plane.so/";
      const host = hostUrl.endsWith("/") ? hostUrl : `${hostUrl}/`;
      const url = `${host}api/v1/${path}`;
      const headers: Record<string, string> = {
        "X-API-Key": process.env.PLANE_API_KEY || "",
      };
    
      // Only add Content-Type for non-GET requests
      if (method.toUpperCase() !== "GET") {
        headers["Content-Type"] = "application/json";
      }
    
      try {
        const config: AxiosRequestConfig = {
          url,
          method,
          headers,
        };
    
        // Only include body for non-GET requests
        if (method.toUpperCase() !== "GET" && body !== null) {
          config.data = body;
        }
    
        const response = await axios(config);
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Request failed: ${error.message}`);
        }
        throw error;
      }
    }
  • Higher-level registration where registerProjectTools is imported and invoked as part of overall tools registration.
    import { registerProjectTools } from "./projects.js";
    import { registerUserTools } from "./user.js";
    import { registerWorkLogTools } from "./work-log.js";
    
    export const registerTools = (server: McpServer) => {
      registerMetadataTools(server);
      registerUserTools(server);
    
      registerProjectTools(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a new project' implies a write/mutation operation but provides no information about permissions needed, whether this is idempotent, what happens on conflicts, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 perfectly concise at three words, front-loading the essential action and resource with zero wasted language. Every word earns its place in communicating the core purpose.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, what permissions are required, or how this tool relates to sibling tools like 'get_projects'. The 100% schema coverage helps with parameters but doesn't compensate for the lack of behavioral context.

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%, with both parameters (identifier and name) well-documented in the schema. The description adds no parameter information beyond what the schema already provides, so it meets the baseline of 3 for high schema coverage.

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

Purpose4/5

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

The description clearly states the verb ('Create') and resource ('a new project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_cycle' or 'create_module', which follow the same pattern for different resources.

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 is provided on when to use this tool versus alternatives. While the name implies it's for project creation, there's no mention of prerequisites, dependencies, or when other creation tools (like create_cycle) would be more appropriate.

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

Related 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/makeplane/plane-mcp-server'

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