← Registry

Productivity

focuh.com

Manages tasks and subtasks with scheduling, priorities, and completion tracking.

1 endpoint14 known toolsFirst detected August 17, 2026Last detected August 27, 2026

ENDPOINT 1

https://www.focuh.com/api/mcp

No auth detected

MCP server metadata

Name
Focuh
Version
2.2.0
Capabilities
toolsresourcesprompts
Server instructions

Focuh — focus timer and task manager. 14 tools. TOOLS: - Tasks: get_tasks, create_tasks, update_tasks, delete_tasks - Subtasks: get_subtasks, reorder_subtasks, create_tasks (parent or subtasks) - Loops: get_loops, pull_loops - Calendar: get_calendar - Goals: get_goals, create_goal, update_goal, delete_goal - Stats: get_focus_stats WORKFLOW: Call get_tasks first — it prints the id and date of every task. Mutations return per-task confirmations — do NOT call get_tasks after one. EVERY WRITE TOOL IS BULK. Pass every task in one call, never loop. - To move days or change priority: update_tasks {date, priority}. To change anything, never delete and recreate — deleting a task loses its subtasks, focus time, goal link and position. - Create a task with its subtasks in one create_tasks call. LOOPS: undated recurring intentions in three buckets (pressing/important/ backlog). pull_loops copies one onto a day as a linked task — the loop stays. Loops carry no priority and no date; buckets are the triage. REFERENCES: 'ref' takes the id shown in the list, #N, or an exact title. ROUTING: Use get_calendar (not get_tasks) for scheduling — it has events. POLICY: Only create tasks for actionable work, not events (lunch, gym). Current date: 2026-08-27 (Thursday)

Known tools 14

get_tasks

Today/tomorrow tasks with id, date and priority.

Inferred read-only
create_tasks

Create tasks, each with optional nested subtasks.

Potential side effects
update_tasks

Change tasks: date (moves the day), priority, title, estimate, done, time slot.

Inferred read-only
delete_tasks

Delete tasks by ref, every task on a date, or all completed.

Potential side effects
get_subtasks

List subtasks of a parent.

Inferred read-only
reorder_subtasks

Reorder a parent's subtasks.

Inferred read-only
get_loops

Loops — undated recurring intentions in three buckets (pressing/important/backlog).

Inferred read-only
pull_loops

Copy loops onto a date as linked tasks — each loop stays in Loops.

Inferred read-only
get_calendar

Events + scheduled/unscheduled tasks for a date.

Inferred read-only
get_goals

Goals by horizon (week/month/year/decade) — exactly what the app's Goals view shows.

Inferred read-only
create_goal

Create a goal in a horizon, with optional bottleneck note and lever.

Potential side effects
update_goal

Update goal fields: title, horizon (moves section), status, bottleneckNote, lever.

Potential side effects
delete_goal

Delete a goal by id.

Potential side effects
get_focus_stats

Today/week focus minutes, streak, task completion rates.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.focuh]
url = "https://www.focuh.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "focuh": {
      "type": "http",
      "url": "https://www.focuh.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: focuh
Remote MCP URL: https://www.focuh.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "focuh": {
      "url": "https://www.focuh.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "focuh": {
      "type": "http",
      "url": "https://www.focuh.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "focuh",
  "transport": "streamable-http",
  "url": "https://www.focuh.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.