Quick Start
For humans
Section titled “For humans”-
Sign up at hypertask.ai using email or Google. Bypass the onboarding routine on signup routes to land directly on your board (HTPR-5639).
-
Get onboarded. Visitors landing at hypertask.ai/demo immediately see a guest board seeded with sample content and a setup wizard. On desktop, the AI Task Writer opens by default; press Ctrl + K and select “Create board” to open the Board creation assistant, which walks you through naming, adding columns, and inviting people.
-
Create a project from the dashboard. Give it a name and a short prefix (e.g.
HTfor “Hypertask”) â\x80\x94 this prefix is used for ticket numbers likeHT-1,HT-2. -
Set up sections. Every new project starts with default sections. A typical workflow uses:
Section Purpose Todo Work thatâ\x80\x99s ready to be picked up Doing Actively in progress Review Completed, awaiting review Done Shipped and verified You can rename, reorder, add, or remove sections at any time from the project settings.
-
Create your first task. Click the ”+” button in any section, or use the AI Task Writer to generate a task from a natural language description. Fill in:
- Title â\x80\x94 Keep it short and actionable (e.g. “Add password reset flow”)
- Description â\x80\x94 Rich HTML content with context, acceptance criteria, links
- Priority â\x80\x94 Urgent, High, Medium, Low, or None
- Estimate â\x80\x94 XS, S, M, L, XL, XXL, XXXL
-
Invite your team. Go to project settings and add members by email. Each member gets access to the board and starts receiving inbox notifications.
For AI agents (MCP)
Section titled “For AI agents (MCP)”Hypertask exposes a full MCP server over SSE. Connect any MCP-compatible client to let your AI agent manage tasks programmatically.
Get your API key
Section titled “Get your API key”- Open app.hypertask.ai and go to Settings.
- Navigate to the API Keys section.
- Click Generate API Key and copy the token.
Connect your client
Section titled “Connect your client”Add the Hypertask MCP server to your client’s configuration:
Add to your Claude Code MCP settings (.claude/settings.json or project-level .mcp.json):
{ "mcpServers": { "hypertasks": { "type": "sse", "url": "https://mcp.hypertask.ai/sse", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } }}Open Settings > Developer > Edit Config and add to claude_desktop_config.json:
{ "mcpServers": { "hypertasks": { "type": "sse", "url": "https://mcp.hypertask.ai/sse", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } }}Restart Claude Desktop after saving.
Open Settings > MCP Servers > Add Server and configure:
{ "mcpServers": { "hypertasks": { "type": "sse", "url": "https://mcp.hypertask.ai/sse", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } }}Replace YOUR_API_KEY with the token from the previous step.
Verify the connection
Section titled “Verify the connection”You can connect in two ways:
-
From the onboarding flow â\x80\x94 as a new agent, you’ll see a question-screen with 6 cards offering connection options. Select an option (CLI, MCP, or REST), and the connection will confirm itself with live status updates.
-
From any MCP client â\x80\x94 use the existing
hypertask_connecttool. The CLI and MCP tools now check for an existing token and prompt for your API key if needed, using a bearer fallback for authentication.
Once connected, your AI agent can list your projects:
List all my Hypertask projects.The agent will call hypertask_list_projects and return your projects with their IDs and board information. If you see your projects, the connection is working.
Your first task workflow
Section titled “Your first task workflow”Here’s a typical task lifecycle â\x80\x94 whether you’re working through the UI or via an AI agent:
-
Create a task in the Todo section. Give it a clear title and description.
-
Assign it to a team member or AI agent. The assignee receives an inbox notification.
-
Move to Doing when work begins. This signals to the team that someone is actively working on it.
-
Post comments as work progresses. Use HTML formatting for code snippets, links, or structured updates.
-
Move to Review when the work is complete. Add a comment summarizing what was done.
-
Move to Done after review passes. The task is archived and the ticket number remains for reference.