Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

get_projects

Retrieve all projects assigned to the current user using the Plane MCP Server, enabling efficient project management through a standardized API interface.

Instructions

Get all projects for the current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_projects' tool. It makes a GET request to the Plane API to fetch projects, maps the response to a simplified structure, and returns the projects as a JSON-formatted text content block.
    server.tool("get_projects", "Get all projects for the current user", {}, async () => {
      const projectsResponse: ProjectsResponse = await makePlaneRequest<ProjectsResponse>(
        "GET",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/`
      );
    
      const projects = projectsResponse.results.map((project) => ({
        name: project.name,
        id: project.id,
        identifier: project.identifier,
        description: project.description,
        project_lead: project.project_lead,
      }));
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(projects, null, 2),
          },
        ],
      };
    });
  • TypeScript type definition for the API response structure used in the get_projects handler.
    type ProjectsResponse = {
      grouped_by: null;
      sub_grouped_by: null;
      total_count: number;
      next_cursor: string;
      prev_cursor: string;
      next_page_results: boolean;
      prev_page_results: boolean;
      count: number;
      total_pages: number;
      total_results: number;
      extra_stats: null;
      results: Project[];
    };
  • Zod schema and TypeScript type for Project, imported and used in ProjectsResponse.results within the get_projects handler.
    export const Project = z.object({
      archive_in: z.number().int().gte(0).lte(12).optional(),
      archived_at: z.string().datetime({ offset: true }).optional(),
      close_in: z.number().int().gte(0).lte(12).optional(),
      cover_image: z.string().optional(),
      cover_image_asset: z.string().uuid().optional(),
      cover_image_url: z.string().readonly(),
      created_at: z.string().datetime({ offset: true }).readonly(),
      created_by: z.string().uuid().readonly(),
      cycle_view: z.boolean().optional(),
      default_assignee: z.string().uuid().optional(),
      default_state: z.string().uuid().optional(),
      deleted_at: z.string().datetime({ offset: true }).readonly(),
      description: z.string().optional(),
      description_html: z.any().optional(),
      description_text: z.any().optional(),
      emoji: z.string().readonly(),
      estimate: z.string().uuid().optional(),
      guest_view_all_features: z.boolean().optional(),
      icon_prop: z.any().optional(),
      id: z.string().uuid().readonly(),
      identifier: z.string().max(12),
      inbox_view: z.boolean().optional(),
      is_deployed: z.boolean().readonly(),
      is_issue_type_enabled: z.boolean().optional(),
      is_member: z.boolean().readonly(),
      is_time_tracking_enabled: z.boolean().optional(),
      issue_views_view: z.boolean().optional(),
      logo_props: z.any().optional(),
      member_role: z.number().int().readonly(),
      module_view: z.boolean().optional(),
      name: z.string().max(255),
      network: z.any().optional(),
      page_view: z.boolean().optional(),
      project_lead: z.string().uuid().optional(),
      sort_order: z.number().readonly(),
      timezone: z.any().optional(),
      total_cycles: z.number().int().readonly(),
      total_members: z.number().int().readonly(),
      total_modules: z.number().int().readonly(),
      updated_at: z.string().datetime({ offset: true }).readonly(),
      updated_by: z.string().uuid().readonly(),
      workspace: z.string().uuid().readonly(),
    });
    export type Project = z.infer<typeof Project>;
  • Top-level registration function that calls registerProjectTools(server), which in turn registers the get_projects tool.
    export const registerTools = (server: McpServer) => {
      registerMetadataTools(server);
      registerUserTools(server);
    
      registerProjectTools(server);
      registerModuleTools(server);
      registerModuleIssueTools(server);
      registerIssueTools(server);
      registerCycleTools(server);
      registerCycleIssueTools(server);
    
      registerWorkLogTools(server);
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'gets' projects, implying a read operation, but lacks details on permissions, rate limits, pagination, or return format. This is inadequate for a tool with zero annotation coverage, leaving key behavioral traits undisclosed.

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 waste—it directly states the tool's purpose without redundancy. It's front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't address behavioral aspects like authentication needs or result format, which are important even for simple tools, leaving gaps in contextual understanding.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds context by specifying 'for the current user', which clarifies the implicit scope beyond the schema, earning a baseline score above 3 for compensating with meaningful semantics.

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 ('Get') and resource ('projects'), specifying it retrieves all projects for the current user. However, it doesn't distinguish itself from potential sibling tools like 'list_projects' (which doesn't exist in the provided list), though it differentiates from other 'get_' tools that fetch specific resources like cycles or issues.

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 minimal guidance, implying usage when needing all projects for the current user, but offers no explicit when-to-use rules, alternatives, or exclusions. For example, it doesn't clarify if this should be used over other project-related tools (like 'create_project') or when filtering might be needed.

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