MCP Integration

Hypertask provides a full Model Context Protocol (MCP) server that lets AI agents create, update, search, and manage tasks programmatically. Any MCP-compatible client can connect to Hypertask and operate as an autonomous worker.

What is MCP?

The Model Context Protocol is an open standard that defines how AI models interact with external tools and data sources. Instead of building custom integrations for each AI client, Hypertask exposes a single MCP server that works with all of them.

MCP uses a tool-based architecture: the server advertises available operations (list tasks, create task, add comment, etc.) and the AI client calls them as needed to complete user requests.

Transport

Hypertask’s MCP server uses SSE (Server-Sent Events) transport. The server endpoint is:

https://mcp.hypertask.ai/sse

Authentication

MCP connections are authenticated with JWT bearer tokens. To get your token:

1. Open app.hypertask.ai and sign in.
2. Go to Settings (gear icon in the sidebar).
3. Copy your API key from the MCP section.

Caution

Tokens expire after 30 days. If your agent stops authenticating, generate a new token from Settings.

Client configuration

Claude Desktop

Add to your Claude Desktop config file (claude_desktop_config.json):

{
  "mcpServers": {
    "hypertasks": {
      "type": "sse",
      "url": "https://mcp.hypertask.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Code

Add to your project’s .mcp.json or global ~/.claude/mcp.json:

{
  "mcpServers": {
    "hypertasks": {
      "type": "sse",
      "url": "https://mcp.hypertask.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Cursor

Open Settings > MCP Servers and add a new server:

{
  "mcpServers": {
    "hypertasks": {
      "type": "sse",
      "url": "https://mcp.hypertask.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Available tools

Once connected, your agent has access to 16 tools:

Tool	Description
hypertask_get_user_context	Get current user info (id, email, display name)
hypertask_list_projects	List all accessible projects
hypertask_create_board	Create a new board with sections, labels, and starter tasks
hypertask_section	List or create sections on a board
hypertask_list_tasks	List tasks with filtering
hypertask_get_tasks	Get specific tasks by ID or ticket number
hypertask_search_tasks	Full-text search across all tasks
hypertask_create_task	Create a new task
hypertask_update_task	Update task fields
hypertask_move_task_between_boards	Move a task to another project
hypertask_assign_user	Assign or unassign users
hypertask_add_comment_to_task	Add a comment (HTML)
hypertask_get_comments_for_task	Read task comments
hypertask_list_project_members	List team members
hypertask_inbox_list	Check inbox notifications
hypertask_inbox_archive	Archive inbox items

Known limitations

The following features are not yet available via MCP:

Feature	Status	Details
Due dates	Not supported	hypertask_create_task and hypertask_update_task do not accept a due_date parameter. Set due dates from the Hypertask UI for now.
Create labels	Not supported	You can assign existing labels to tasks, but cannot create new labels via MCP. Create labels in the Hypertask UI first, then reference them.
Labels on tasks	Not supported	hypertask_create_task and hypertask_update_task do not accept a labels parameter. Use the CLI or UI to manage labels on tasks.
@mentions in comments	Partial	The mentions parameter on hypertask_add_comment_to_task is available, but mentions may appear as plain text and not trigger notifications. Use structured mention objects (user_id + display_name) for best results.
Related task linking	Not supported	Ticket references (e.g. HTPR-1234) in comments added via MCP are not automatically parsed into “related tasks” links like they are in the UI.

Tip

For features not yet available via MCP, use the Hypertask CLI as a workaround — it supports labels, due dates, and description updates.

Troubleshooting

“Failed to Connect to MCP” — If your client cannot connect:

1. Verify your token has not expired (tokens expire after 30 days). Generate a new one from Settings in the Hypertask app.
2. Confirm the URL is exactly https://mcp.hypertask.ai/sse (including /sse).
3. Check that the Authorization header is formatted as Bearer <token> with a space after “Bearer”.
4. Restart your MCP client after updating the configuration.

Supported clients

Hypertask MCP works with any client that supports the MCP standard:

• Claude Code — Anthropic’s CLI agent
• Claude Desktop — Anthropic’s desktop app
• Cursor — AI-powered code editor
• Windsurf — Codeium’s AI editor
• Any MCP-compatible agent — anything that speaks the protocol

Next steps

Agent Workflows Patterns for how AI agents should pick up and complete work.

MCP Tools Reference Complete parameter reference for all 16 tools.