Available Tools

The full list of 20 tools your coding agent can use through the Hamster MCP server.

Overview

When your agent connects to the Hamster MCP Server, it gains access to 20 tools organized across six areas: accounts, Briefs, Tasks, subtasks, documents, and plans. These tools let the agent read your project context, create and update work items, and navigate between accounts — all scoped to your permissions.

Every tool runs as the signed-in user. A Reviewer can list Briefs, threads, and Tasks but cannot mutate them; a Creator can create and update; an Admin and Owner can do everything their role allows in the browser. There is no admin override at the MCP layer — your role is your role.

Accounts

Tool What it does
list_accounts Show all your accounts (personal and team)
switch_account Switch to a different account

Briefs

Tool What it does
list_briefs List Briefs in the current account
get_brief Get a Brief's full content and metadata
create_brief Create a new Brief
update_brief Update a Brief's title, description, or status
delete_brief Delete a Brief

Tasks

Tool What it does
list_tasks List Tasks for a Brief, with optional filters for status, priority, and assignee
get_task Get a Task's full details including subtasks and dependencies
create_task Create a new Task under a Brief
update_task Update a Task's title, description, priority, assignee, or other fields
update_task_status Move a Task to a new status (to do, in progress, done)
get_next_task Get the next Task to work on based on priority and dependencies

Subtasks

Tool What it does
list_subtasks List subtasks for a Task
create_subtask Add a subtask to a Task
update_subtask Update a subtask's content or status
delete_subtask Remove a subtask

Documents

Tool What it does
list_documents List documents attached to a Brief
get_document Get a document's full content

Plans

Tool What it does
get_plan Get the full Plan for a Brief, including all generated Tasks

How Tools Are Discovered

Your AI tool calls tools/list once per session and gets back the full list of 20 tools, each with its input schema and description. The schema is rich enough that the AI can infer when to use a tool without you spelling it out — "what's my next Task?" maps to get_next_task, "what Briefs do I have open?" maps to list_briefs, and so on.

Hamster's MCP Server is stateless — each call carries your auth token and the active account context, and the server resolves the right team-account scope per request. That makes it safe for AI tools that open and close Connections frequently or run multiple sessions in parallel.

Tips

  • The get_next_task tool is particularly useful for agentic workflows. It returns the highest-priority Task that has no unfinished dependencies — so the agent always picks up the right thing next.
  • get_task and update_task_status accept both UUIDs and display IDs (like HAM-123), so your agent can reference Tasks the same way you do.
  • list_tasks supports filters for status, priority, and assignee — useful when you want the agent to focus on a specific slice of work.
  • update_task_status handles reordering automatically. When the AI moves a Task to "done", the Task list stays correctly sorted.
  • Tool Results respect your role. If an action is blocked by your permissions, the response carries a clear error rather than a silent failure.
  • The MCP Server and the CLI complement each other: MCP gives the agent live read/write access; CLI sync keeps the same content on disk as markdown your agent can grep, read, and reference without an API call.

Related