Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

create_cycle

Use this to initiate a new project cycle within Plane's project management system, specifying key details like start and end dates, issue tracking, and metadata through a structured API.

Instructions

Create a new cycle in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycle_dataYesThe data for creating the cycle
project_idYesThe uuid identifier of the project to create the cycle in

Implementation Reference

  • The main handler function that executes the create_cycle tool logic by posting cycle data to the Plane API endpoint and returning the JSON response.
    async ({ project_id, cycle_data }) => {
      const response = await makePlaneRequest(
        "POST",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/cycles/`,
        cycle_data
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Zod schema for Cycle type, imported as CycleSchema and used in create_cycle input validation with partial().required({name: true, project_id: true}).
    export const Cycle = z.object({
      archived_at: z.string().datetime({ offset: true }).optional(),
      backlog_issues: z.number().int().readonly(),
      cancelled_issues: z.number().int().readonly(),
      completed_estimates: z.number().readonly(),
      completed_issues: z.number().int().readonly(),
      created_at: z.string().datetime({ offset: true }).readonly(),
      created_by: z.string().uuid().readonly(),
      deleted_at: z.string().datetime({ offset: true }).readonly(),
      description: z.string().optional(),
      end_date: z.string().date().optional().describe("The end date of the cycle of format YYYY-MM-DD"),
      external_id: z.string().max(255).optional(),
      external_source: z.string().max(255).optional(),
      id: z.string().uuid().readonly(),
      logo_props: z.any().optional(),
      name: z.string().max(255),
      owned_by: z.string().uuid().readonly(),
      progress_snapshot: z.any().optional(),
      project_id: z.string().uuid().readonly(),
      sort_order: z.number().optional(),
      start_date: z.string().date().optional().describe("The start date of the cycle of format YYYY-MM-DD"),
      started_estimates: z.number().readonly(),
      started_issues: z.number().int().readonly(),
      timezone: z.any().optional(),
      total_estimates: z.number().readonly(),
      total_issues: z.number().int().readonly(),
      unstarted_issues: z.number().int().readonly(),
      updated_at: z.string().datetime({ offset: true }).readonly(),
      updated_by: z.string().uuid().readonly(),
      version: z.number().int().gte(-2147483648).lte(2147483647).optional(),
      view_props: z.any().optional(),
      workspace: z.string().uuid().readonly(),
    });
  • Direct registration of the create_cycle tool via server.tool() call within registerCycleTools, specifying name, description, input schema, and handler.
    server.tool(
      "create_cycle",
      "Create a new cycle in a project",
      {
        project_id: z.string().describe("The uuid identifier of the project to create the cycle in"),
        cycle_data: CycleSchema.partial()
          .required({
            name: true,
            project_id: true,
          })
          .describe("The data for creating the cycle"),
      },
      async ({ project_id, cycle_data }) => {
        const response = await makePlaneRequest(
          "POST",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/cycles/`,
          cycle_data
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      }
    );
  • Utility function makePlaneRequest used by the create_cycle handler to perform 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;
      }
    }
  • Invocation of registerCycleTools within registerTools, which includes the create_cycle tool registration.
    registerCycleTools(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. It states this is a creation operation but doesn't mention permissions required, whether it's idempotent, what happens on conflicts, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'cycle' represents in this context, what happens after creation, error conditions, or relationship to sibling tools. The 100% schema coverage helps with parameters but doesn't compensate for missing behavioral and contextual information.

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 documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline expectation but not providing extra value.

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 action ('Create') and resource ('new cycle in a project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_cycle' or 'list_cycles' beyond the basic verb, missing explicit sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_cycle' or 'list_cycles', nor does it mention prerequisites or context for creation. It simply states what the tool does without usage 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

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