list_projects

What it does

Projects are where the reusable context lives — company, offer, ICP, voice. An agent that is about to write anything should find the project first, because writing from an empty context is how a personalized message ends up generic.

Arguments

None. Send an empty arguments object.

This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:

{
  "type": "object",
  "properties": {}
}

Request

Paste this, swap the key, and you have called the tool.

curl -s https://topclozer.com/api/mcp \
  -H "Authorization: Bearer tcz_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list_projects",
      "arguments": { }
    }
  }'

Returns

{ count, projects[] }. Each project is the stored row plus context_filled (how many of the twelve fields have content), context_usable, and installs (how many installations are bound to it).

The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.

{
  "count": 1,
  "projects": [
    {
      "id": "prj_4c81",
      "org_id": "org_01",
      "name": "Northbeam · Series-B CTOs",
      "created_at": 1789084800000,
      "updated_at": 1789171200000,
      "context_filled": 7,
      "context_fields": 12,
      "context_usable": true,
      "installs": 2
    }
  ]
}

Worth knowing

An empty list means this workspace has genuinely created no project. There is no default project and none is invented — a project is created in the app, not from here, because naming someone's company for them is not a decision an agent should make.

Limits

No request limit. This tool reads the workspace database and costs nothing to serve. The limits that bite in this product are the sending controls — per-sender weekly invite caps, the warm-up ramp, the working-hours window and a randomised gap between actions — and no tool can raise them.

Related tools

All 21 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.