Skip to main content
Glama
elizagarate

Things MCP Server

by elizagarate

add_project

Create a project in Things 3 with title, notes, schedule, deadline, tags, area, and initial to-dos.

Instructions

Create a new project in Things

Args: title: Title of the project notes: Notes for the project when: When to schedule the project (today, tomorrow, evening, anytime, someday, or YYYY-MM-DD). Use YYYY-MM-DD@HH:MM format to add a reminder (e.g., 2024-01-15@14:30) deadline: Deadline for the project (YYYY-MM-DD) tags: Tags to apply to the project area_id: ID of area to add to area_title: Title of area to add to todos: Initial todos to create in the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
notesNo
whenNo
deadlineNo
tagsNo
area_idNo
area_titleNo
todosNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler that creates a new project in Things by constructing and executing a Things URL. Decorated with @mcp.tool.
    @mcp.tool
    async def add_project(
        title: str,
        notes: str = None,
        when: str = None,
        deadline: str = None,
        tags: List[str] = None,
        area_id: str = None,
        area_title: str = None,
        todos: List[str] = None
    ) -> str:
        """Create a new project in Things
    
        Args:
            title: Title of the project
            notes: Notes for the project
            when: When to schedule the project (today, tomorrow, evening, anytime, someday, or YYYY-MM-DD).
                Use YYYY-MM-DD@HH:MM format to add a reminder (e.g., 2024-01-15@14:30)
            deadline: Deadline for the project (YYYY-MM-DD)
            tags: Tags to apply to the project
            area_id: ID of area to add to
            area_title: Title of area to add to
            todos: Initial todos to create in the project
        """
        url = url_scheme.add_project(
            title=title,
            notes=notes,
            when=when,
            deadline=deadline,
            tags=tags,
            area_id=area_id,
            area_title=area_title,
            todos=todos
        )
        url_scheme.execute_url(url)
        return f"Created new project: {title}"
  • URL construction helper that builds a things:///add-project URL from project parameters, mapping arguments to URL query parameters.
    def add_project(title: str, notes: Optional[str] = None, when: Optional[str] = None,
                    deadline: Optional[str] = None, tags: Optional[list[str]] = None,
                    area_id: Optional[str] = None, area_title: Optional[str] = None,
                    todos: Optional[list[str]] = None) -> str:
        """Construct URL to add a new project.
    
        Args:
            title: Title of the project
            notes: Notes for the project
            when: Schedule the project. Accepts:
                - Keywords: "today", "tomorrow", "evening", "anytime", "someday"
                - Date: "yyyy-mm-dd" or natural language ("in 3 days", "next tuesday")
                - DateTime (adds reminder): "yyyy-mm-dd@HH:MM" (e.g., "2024-01-15@14:30")
            deadline: Deadline date (yyyy-mm-dd)
            tags: List of tag names
            area_id: UUID of area to add to
            area_title: Title of area to add to
            todos: List of todo titles to create in the project
        """
        params = {
            'title': title,
            'notes': notes,
            'when': when,
            'deadline': deadline,
            'area-id': area_id,
            'area': area_title,
            # Change todos to be newline separated
            'to-dos': '\n'.join(todos) if todos else None
        }
    
        # Handle tags separately since they need to be comma-separated
        if tags:
            params['tags'] = ','.join(tags)
    
        return construct_url('add-project', {k: v for k, v in params.items() if v is not None})
  • The @mcp.tool decorator registers add_project as an MCP tool on the FastMCP server instance.
    @mcp.tool
  • Helper that executes a Things URL via subprocess, used by the add_project handler to open the constructed URL.
    def execute_url(url: str) -> None:
        """Execute a Things URL without bringing Things to the foreground.
        
        Security: validates the URL starts with 'things:///' before execution
        to prevent opening arbitrary URLs or executing unintended commands.
        Uses subprocess with argument list (no shell interpolation) to avoid
        command injection vectors.
        """
        if not url.startswith("things:///"):
            raise ValueError(f"Invalid Things URL scheme: {url[:50]}")
        subprocess.run(['open', '-g', url], check=True, capture_output=True)
  • URL construction helper used by add_project to build the full things:///add-project URL with encoded parameters.
    def construct_url(command: str, params: Dict[str, Any]) -> str:
        """Construct a Things URL from command and parameters."""
        # Start with base URL
        url = f"things:///{command}"
    
        # Get authentication token if needed
        if command in ['update', 'update-project']:
            token = things.token()
            if token:
                params['auth-token'] = token
    
        # URL encode parameters
        if params:
            encoded_params = []
            for key, value in params.items():
                if value is None:
                    continue
                # Handle boolean values
                if isinstance(value, bool):
                    value = str(value).lower()
                # Handle lists (for tags, checklist items etc)
                elif isinstance(value, list):
                    value = ','.join(str(v) for v in value)
                encoded_params.append(f"{key}={urllib.parse.quote(str(value))}")
    
            url += "?" + "&".join(encoded_params)
    
        return url
Behavior4/5

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

No annotations exist, so the description carries full burden. It explains parameter formats (e.g., 'when', 'deadline') and the purpose of 'todos' as initial items. However, it does not mention side effects, idempotency, or return behavior, which are typical for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and uses a clear Args list. It is appropriately sized for 8 parameters, though some entries (e.g., 'tags') could be more specific. No superfluous content.

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

Completeness4/5

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

Given no annotations and a moderate number of parameters, the description covers all inputs well. It lacks notes on precedence between 'area_id' and 'area_title', and does not mention error handling or prerequisites, but overall provides sufficient context for typical usage.

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

Parameters5/5

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

Schema description coverage is 0%, but the description explains all 8 parameters with concrete examples and allowed formats (e.g., 'when' values, date formats). This adds significant value beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new project in Things', using a specific verb and resource. This distinguishes it from sibling tools like 'add_todo' which creates todos, and 'update_project' which modifies existing projects.

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 is provided on when to use this tool versus alternatives like 'add_todo' or 'update_project'. The description only lists parameters without context on when this tool is appropriate.

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/elizagarate/things-mcp'

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