A real API, and an MCP server agents act through

Capabilities

What the API covers

The API spans the core work objects, so automation and agents operate on the same structured surface your team does.

• 01

  Sheets, folders & workspaces

  Create and organise the structured surfaces work lives in, and read their contents programmatically.

• 02

  Tasks & hierarchy

  Create, update, move, indent, and bulk-edit tasks - the unit agents and automations act on.

• 03

  Columns & schema

  Define the data model: columns, types, and dropdown options that give work its structure.

• 04

  Saved views & reports

  Create and read the views that shape how work is seen - so agents can target the right slice.

• 05

  Comments & activity

  Read and write discussion and activity, keeping a human-readable trail alongside automated changes.

• 06

  Webhooks & imports

  Subscribe to changes and bring data in - the integration points that connect Homany to the rest of your stack.

Agent-readiness

MCP: the same surface, exposed to agents

The Model Context Protocol (MCP) server lets agents discover and call Homany's capabilities directly - within the scope and permissions you set.

• API parity

  Agents act through the same operations as integrations - no weaker, separate agent path.

• Scoped access

  Agents operate within the permissions and objects you grant, the same way a teammate would.

• Traceable actions

  Agent actions land on the audit trail, so what changed, when, and on whose authority is recoverable.

Examples

What teams build on it

• Automated intake

  Route incoming requests into the right sheet and owner, with an agent triaging the structure.

• Live roll-ups

  Keep a programme view current from the underlying tasks, without manual status chasing.

• System sync

  Use webhooks to keep Homany and your other systems of record in step.