Plane MCP Server

Instructions

Implementation Reference

• src/tools/metadata.ts:37-50 (handler)

  Handler function that fetches the details of a specific issue type by making a GET request to the Plane API endpoint and returns the JSON response as text content.

  async ({ project_id, type_id }) => {
    const response = await makePlaneRequest(
      "GET",
      `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/issue-types/${type_id}/`
    );
    return {
      content: [
        {
          type: "text",
          text: JSON.stringify(response, null, 2),
        },
      ],
    };
  }

• src/tools/metadata.ts:33-36 (schema)

  Zod input schema defining the required parameters: project_id and type_id as strings with descriptions.

  {
    project_id: z.string().describe("The uuid identifier of the project containing the issue type"),
    type_id: z.string().describe("The uuid identifier of the issue type to get"),
  },

• src/tools/metadata.ts:30-51 (registration)

  Direct registration of the get_issue_type tool on the MCP server, including name, description, input schema, and handler function.

  server.tool(
    "get_issue_type",
    "Get details of a specific issue type",
    {
      project_id: z.string().describe("The uuid identifier of the project containing the issue type"),
      type_id: z.string().describe("The uuid identifier of the issue type to get"),
    },
    async ({ project_id, type_id }) => {
      const response = await makePlaneRequest(
        "GET",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/issue-types/${type_id}/`
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  );

• src/tools/index.ts:14-14 (registration)

  Top-level call to registerMetadataTools, which registers the get_issue_type tool among others.

  registerMetadataTools(server);