The Model Context Protocol (MCP) lets AI clients call tools on your behalf. ContactAPI ships an MCP server, so an assistant can list, create, update, and delete your contacts with your permission, scoped to your account.
The endpoint
https://contactapi.dev/mcpAuth is OAuth, not a pasted key
You don't hand the model an API key. The server uses OAuth 2.1 with dynamic client registration: point a client at the URL, it discovers the auth server, registers itself, and sends you to log in and approve. Every tool call is scoped to the account you approved.
What the assistant can do
list_contactsreturns your contacts newest first, paginated.get_contactfetches one by id.create_contactcreates or upserts by email.update_contactmerges fields into an existing contact.delete_contactremoves one.
Add the URL as a custom connector in claude.ai, Claude Desktop, or Cursor and ask, in plain language, to "add ada@example.com to my contacts as a pro user." The model does the rest, safely and only for your data.
Where ContactAPI fits
ContactAPI is an open-source REST API for saving and managing contacts. You POST an email plus any JSON fields, get simple CRUD back, and can reach the same data from an AI client over its MCP server. No CRM, no pipeline stages, no lock-in.