what it’s for
monica works with Monica, the open-source personal relationship manager: contacts, notes, activities, reminders, tasks, journal entries, relationships and more, on the stable 4.x API and on the current main API with UUID identifiers. output is official TOON by default, or JSON, YAML, markdown and tables, and --raw prints just the data rows for jq.
a CRM holds other people’s details, so this one starts careful: setup leaves read-only mode on unless you ask for read-write, and checks what your server version supports before an agent plans anything.
what it covers
- contacts
- notes
- activities
- reminders
- tasks
- tags
- companies
- calls
- gifts
- debts
- journal
- relationships
- documents
- photos
- audit logs
built for agents
walls around the effects
other people’s details deserve a second key. reading is the default; writing is a decision.
read-only from the first run
setup keeps read-only mode on unless you pass
--read-write;--dry-runvalidates a configuration without saving it.monica setup --api-url http://your-monica-instance/api --api-key your-api-key --non-interactive --dry-runknow what this server supports
a read-only capability probe gives an allow-list of supported commands, and a deny-list with the endpoint and status that ruled each one out.
monica --json info unsupported-commandstools in your runtime’s shape
exports tool definitions for OpenAI, Anthropic and MCP with required inputs and mutation safety metadata, limited to what your server supports.
monica --json agent-tools mcp-tools --instance-awarewrites need two keys
API mutations need
--confirmand a write-enabled configuration.monica api mutate <operation> --confirmcontracts you can check
every output type has a registered schema, and JSON, YAML or TOON payloads can be validated against it.
monica schemas validate config-test ./payload.toon
a first run
same rules, four services
each service CLI pairs compact, structured output with discovery an agent can read and writes that have to be asked for.