Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

create_task

Create a task in Super Productivity with title and optional details (notes, project, tags, time estimate, due date) using the local API.

Instructions

Creates a new task in Super Productivity. Extra fields are passed through to the local API if supported by your app version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
notesNoAdditional notes / description
projectIdNoProject ID to assign the task to
projectNameNoProject name to assign the task to
tagIdsNoList of tag IDs
tagNamesNoList of tag names
timeEstimateMinsNoEstimated duration in minutes
dueDateISONoDue date in ISO 8601 format (e.g. 2026-04-23)

Implementation Reference

  • The MCP server.tool registration for 'create_task' — contains the Zod schema (input validation) and the async handler that resolves IDs, calls SpClient.createTask, and returns the result.
    // ── Create task ─────────────────────────────────────────────────────────
    server.tool(
      "create_task",
      "Creates a new task in Super Productivity. Extra fields are passed through to the local API if supported by your app version.",
      {
        title: nonEmptyString.describe("Task title"),
        notes: z.string().optional().describe("Additional notes / description"),
        projectId: nonEmptyString.optional().describe("Project ID to assign the task to"),
        projectName: nonEmptyString.optional().describe("Project name to assign the task to"),
        tagIds: z.array(nonEmptyString).optional().describe("List of tag IDs"),
        tagNames: z.array(nonEmptyString).optional().describe("List of tag names"),
        timeEstimateMins: z.number().optional().describe("Estimated duration in minutes"),
        dueDateISO: nonEmptyString.optional().describe("Due date in ISO 8601 format (e.g. 2026-04-23)"),
      },
      async ({ title, notes, projectId, projectName, tagIds, tagNames, timeEstimateMins, dueDateISO }) => {
        const resolved = await resolveTaskWriteIds({ projectId, projectName, tagIds, tagNames });
        const task = await SpClient.createTask({
          title,
          notes,
          projectId: resolved.projectId,
          tagIds: resolved.tagIds,
          timeEstimate: timeEstimateMins ? timeEstimateMins * 60_000 : undefined,
          dueDate: parseIsoDateToTimestamp(dueDateISO),
        });
        return ok(task);
      }
    );
  • The CreateTaskPayload interface that defines the shape of the payload sent to the Super Productivity API (the backend HTTP call).
    export interface CreateTaskPayload {
      title: string;
      notes?: string;
      projectId?: string;
      tagIds?: string[];
      timeEstimate?: number;
      dueDate?: number;
    }
  • The SpClient.createTask method — the actual HTTP POST request to /tasks that creates the task via the REST API.
    createTask(payload: CreateTaskPayload): Promise<Task> {
      return request("/tasks", TaskSchema, {
        method: "POST",
        body: JSON.stringify(payload),
      });
    },
  • The parseIsoDateToTimestamp helper used by the create_task handler to convert dueDateISO to a millisecond timestamp.
    export function parseIsoDateToTimestamp(dateString?: string): number | undefined {
      if (!dateString) {
        return undefined;
      }
    
      const timestamp = Date.parse(dateString);
      if (Number.isNaN(timestamp)) {
        throw new Error(`Invalid dueDateISO "${dateString}". Use a valid ISO date like 2026-04-23 or 2026-04-23T09:00:00Z.`);
      }
    
      return timestamp;
    }
  • src/index.ts:5-17 (registration)
    The top-level entry point where registerTaskTools is called, which includes the 'create_task' tool registration.
    import { registerTaskTools } from "./tools/tasks.js";
    import { registerProjectTools } from "./tools/projects.js";
    import { registerResources } from "./resources.js";
    import { registerPrompts } from "./prompts.js";
    
    const server = new McpServer({
      name: "super-productivity-mcp",
      version: "1.0.0",
    });
    
    // Register everything
    registerTaskTools(server);
    registerProjectTools(server);
Behavior3/5

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

The description mentions that extra fields are passed through to the local API, which is useful behavioral context. However, it lacks details on error handling, idempotency, permissions, or what happens upon success.

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 concise with two sentences, front-loading the core purpose. No unnecessary text.

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?

With 8 parameters and no output schema or annotations, the description is too brief. It omits return value, error states, and how to determine if extra fields are supported.

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 coverage is 100%, so the input schema already documents all parameters. The description adds the note about extra fields being passed through, but does not clarify individual parameter semantics beyond what the schema provides.

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 'Creates a new task in Super Productivity', specifying the verb and resource. However, it does not differentiate from sibling tools like update_task, which also modify tasks.

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 provided on when to use this tool versus alternatives such as update_task or set_current_task. There is no mention of when not to use it or context-specific scenarios.

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

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/claus-92/super-productivity-mcp'

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