MCP 207 tools

Browse the tools

Model Context Protocol (MCP)

Connect your AI assistant to Monica to find contacts, add people, and manage favourites through conversation.

Monica’s MCP server gives compatible assistants access to tools that work with your account.

Server address
https://my.monicahq.com/mcp

Set up Monica MCP

  1. An assistant connects in one of two ways. If it supports OAuth, give it the server address and it sends you to Monica to sign in. Monica shows the name the assistant gives itself and the address it sends you back to, and connects it only when you choose Allow. No key is needed.

  2. Otherwise, create an API key in Settings → Security and access → API keys. Under What will use this key, choose AI Assistant and give the key a recognisable name. Copy the key when it appears. Use a separate key for each assistant so you can revoke its access independently.

  3. Every example on this page uses this address.

Set the MONICA_API_KEY environment variable to your Monica API key before starting Claude Code.

Add this configuration to your project’s .mcp.json. If the file already contains servers, add monica to the existing mcpServers object.

.mcp.json

{
"mcpServers": {
"monica": {
"type": "http",
"url": "https://my.monicahq.com/mcp",
"headers": {
"Authorization": "Bearer ${MONICA_API_KEY}"
}
}
}
}

Start Claude Code from that environment, approve the project’s MCP configuration when prompted, and use /mcp to check the connection.

Check your connection

Ask your assistant:

  • “List my Monica vaults.” Confirm that the returned vaults belong to your account.
  • “Find Alice in my Personal vault.” An empty result is fine. What matters is that the call succeeds against the right account.

Manage access

  1. Your assistant acts as you, through its API key or its OAuth connection. Changes made through MCP are recorded in Settings → Logs, under the assistant’s name.

  2. To disconnect an assistant connected through OAuth, choose Disconnect beside it in Settings → Security and access → Connected assistants. To disconnect one using a key, revoke its key in Settings → Security and access → API keys. Either takes effect at once.

Your assistant can access all your vaults

Your assistant can use every tool in every vault in your account, whether it connects with a key or through OAuth. Choosing “AI Assistant” when creating an API key only labels the key—it does not limit what your assistant can access or change.

Edit a template

A template changes through a draft. Its sections and fields can only change on a draft version, and nothing reaches the records it describes until the draft is published. Deleting a draft throws its changes away.

A field can come back with a new id when its section had to be drafted first. Use the id the tool returns.

Asked to add a Hobbies section with a text field and a date field, an assistant calls:

  1. list-templates, to find the template.
  2. create-template-draft, to open a draft and learn its version number.
  3. add-template-section with the name Hobbies, which returns the id of the new section.
  4. create-template-field twice: a text field named Hobby, then a date field named Started.
  5. get-template-version, to check the draft.
  6. publish-template-version, with a note saying what changed.

Troubleshooting

The assistant is refused
With a key, the key is wrong or revoked: create a new one in Settings → Security and access → API keys and update your configuration. With OAuth, the assistant was disconnected or its access expired: remove the connector, add it again, and choose Allow.
The server cannot be reached
Check that the address ends in /mcp and that your instance is reachable from the machine running the assistant.
The key is empty
The assistant cannot see MONICA_API_KEY. Set it in the environment the assistant starts from, then restart it. Desktop apps often do not read your terminal’s variables.
Too many requests
The assistant reached the limit of 60 requests a minute for its key or its connection. Wait a minute and ask again.

See also