# Human CRM — MCP

Human exposes a Model Context Protocol server so any MCP client (Claude, etc.)
can manage the CRM with discrete, typed tools.

## Connect

```json
{
  "mcpServers": {
    "human": {
      "url": "https://humancrm.com/api/memories/mcp",
      "headers": { "Authorization": "Bearer hc_..." }
    }
  }
}
```

Get a key with `POST /api/signup` (agents can self-serve) or from your
dashboard. Use an `hcr_` key for read-only access. Transport is JSON-RPC 2.0
over HTTP (protocol `2024-11-05`).

## Tools

- **search** `{ query, entityId? }` — semantic + keyword search across memories.
- **query** `{ query, outputSchema?, slug?, name? }` — extract STRUCTURED data
  from the memories; pass a `slug` to save it as a cached custom API.
- **list_contacts** `{ type?, limit? }`
- **get_contact** `{ entityId }` — contact + its memory documents.
- **create_contact** `{ name, type?, fields? }`
- **log_memory** `{ title, markdown, entityId? }` — append a markdown note.
- **get_summary** `{ entityId }`
- **update_summary** `{ entityId, markdown }`
- **create_view_link** `{ kind, entityId?, slug?, ttlHours? }` — mint a no-login
  browser link (kind: `workspace` | `entity` | `query`).

## Notes

- Everything the REST API can do, these tools can do — they share one action core.
- Writes require a full (`hc_`) key; read-only (`hcr_`) keys can `search`,
  `query`, `list_contacts`, `get_contact`, `get_summary`.
- See the full REST reference at `/docs/api.md`.