Skip to main content
Glama

add_project

Add a new project to OmniFocus with details like name, notes, due date, tags, and folder. Define sequential tasks, estimated time, and flag status for enhanced task management.

Instructions

Add a new project to OmniFocus

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deferDateNoThe defer date of the project in ISO format (YYYY-MM-DD or full ISO date)
dueDateNoThe due date of the project in ISO format (YYYY-MM-DD or full ISO date)
estimatedMinutesNoEstimated time to complete the project, in minutes
flaggedNoWhether the project is flagged or not
folderNameNoThe name of the folder to add the project to (will add to root if not specified)
nameYesThe name of the project
noteNoAdditional notes for the project
sequentialNoWhether tasks in the project should be sequential (default: false)
tagsNoTags to assign to the project

Implementation Reference

  • src/server.ts:48-53 (registration)
    Registers the 'add_project' tool with the MCP server, specifying its name, description, input schema, and handler function imported from './tools/definitions/addProject.js'.
    server.tool(
      "add_project",
      "Add a new project to OmniFocus",
      addProjectTool.schema.shape,
      addProjectTool.handler
    );
  • Zod schema defining the input parameters for the 'add_project' tool, including project name, notes, dates, flags, estimates, tags, folder, and sequential setting.
    export const schema = z.object({
      name: z.string().describe("The name of the project"),
      note: z.string().optional().describe("Additional notes for the project"),
      dueDate: z.string().optional().describe("The due date of the project in ISO format (YYYY-MM-DD or full ISO date)"),
      deferDate: z.string().optional().describe("The defer date of the project in ISO format (YYYY-MM-DD or full ISO date)"),
      flagged: z.boolean().optional().describe("Whether the project is flagged or not"),
      estimatedMinutes: z.number().optional().describe("Estimated time to complete the project, in minutes"),
      tags: z.array(z.string()).optional().describe("Tags to assign to the project"),
      folderName: z.string().optional().describe("The name of the folder to add the project to (will add to root if not specified)"),
      sequential: z.boolean().optional().describe("Whether tasks in the project should be sequential (default: false)")
    });
  • MCP tool handler for 'add_project' that validates input, calls the primitive addProject function, and returns formatted success or error response.
    export async function handler(args: z.infer<typeof schema>, extra: RequestHandlerExtra) {
      try {
        // Call the addProject function 
        const result = await addProject(args as AddProjectParams);
        
        if (result.success) {
          // Project was added successfully
          let locationText = args.folderName 
            ? `in folder "${args.folderName}"` 
            : "at the root level";
            
          let tagText = args.tags && args.tags.length > 0
            ? ` with tags: ${args.tags.join(', ')}`
            : "";
            
          let dueDateText = args.dueDate
            ? ` due on ${new Date(args.dueDate).toLocaleDateString()}`
            : "";
            
          let sequentialText = args.sequential
            ? " (sequential)"
            : " (parallel)";
            
          return {
            content: [{
              type: "text" as const,
              text: `✅ Project "${args.name}" created successfully ${locationText}${dueDateText}${tagText}${sequentialText}.`
            }]
          };
        } else {
          // Project creation failed
          return {
            content: [{
              type: "text" as const,
              text: `Failed to create project: ${result.error}`
            }],
            isError: true
          };
        }
      } catch (err: unknown) {
        const error = err as Error;
        console.error(`Tool execution error: ${error.message}`);
        return {
          content: [{
            type: "text" as const,
            text: `Error creating project: ${error.message}`
          }],
          isError: true
        };
      }
    } 
  • Core helper function that generates AppleScript for creating an OmniFocus project and executes it via osascript, returning success status, project ID, or error.
    export async function addProject(params: AddProjectParams): Promise<{success: boolean, projectId?: string, error?: string}> {
      try {
        // Generate AppleScript
        const script = generateAppleScript(params);
        
        console.error("Executing AppleScript directly...");
        
        // Execute AppleScript directly
        const { stdout, stderr } = await execAsync(`osascript -e '${script}'`);
        
        if (stderr) {
          console.error("AppleScript stderr:", stderr);
        }
        
        console.error("AppleScript stdout:", stdout);
        
        // Parse the result
        try {
          const result = JSON.parse(stdout);
          
          // Return the result
          return {
            success: result.success,
            projectId: result.projectId,
            error: result.error
          };
        } catch (parseError) {
          console.error("Error parsing AppleScript result:", parseError);
          return {
            success: false,
            error: `Failed to parse result: ${stdout}`
          };
        }
      } catch (error: any) {
        console.error("Error in addProject:", error);
        return {
          success: false,
          error: error?.message || "Unknown error in addProject"
        };
      }
    } 
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool adds a project but doesn't explain what happens upon success (e.g., returns a project ID), error conditions, permissions needed, or side effects. 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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an AI agent to parse quickly.

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 ('add') with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like return values, error handling, or system impacts, leaving significant gaps for an AI agent to understand how to use it effectively.

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 all 9 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to the rules, with high schema coverage, the baseline is 3 even with no param info in the description.

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 ('Add a new project') and target resource ('to OmniFocus'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'add_omnifocus_task' or 'batch_add_items' that might also create items in OmniFocus, so it doesn't reach the highest score.

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. It doesn't mention when to choose 'add_project' over 'add_omnifocus_task' (for tasks vs. projects) or 'batch_add_items' (for bulk operations), nor does it specify prerequisites or exclusions for project creation.

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/jqlts1/omnifocus-mcp-enhanced'

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