About contactapi
contactapi is an open-source API for collecting and managing email-keyed contacts, with simple CRUD operations and optional JSON fields. It also offers an MCP endpoint where authenticated AI clients can manage contacts within the signed-in account.
Key features
- 01Create or upsert contacts by email
- 02List contacts with pagination
- 03Fetch, update, and delete contacts
- 04Publishable browser keys restricted to domains
- 05OAuth 2.1 MCP access with dynamic registration
Use cases
- 01Collect signups from a website form
- 02Update or remove an existing contact
- 03Let an AI client manage account contacts
- 04Integrate contact management through the REST API
MCP support
The MCP server exposes tools to list, retrieve, create, update, and delete contacts. Clients authenticate through OAuth 2.1 with dynamic registration, and access is scoped to the approved account.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEcontactapi
An open-source API to save contacts. Send a POST with an email and any other
JSON fields you want, and they get saved as-is. Manage them with simple CRUD.
Built with Hono and deployed on Vercel.
API overview
The base URL is https://contactapi.dev and every request carries your API key
as a Bearer token:
Authorization: Bearer YOUR_KEY
| Method | Path | Key | Description |
|---|---|---|---|
POST | /v1/contacts | secret or publishable | Create (or upsert) a contact by email |
GET | /v1/contacts | secret | List contacts, paginated |
GET | /v1/contacts/:id | secret | Fetch a single contact |
PATCH | /v1/contacts/:id | secret | Update a contact |
DELETE | /v1/contacts/:id | secret | Delete a contact |
Contacts are keyed by email — creating one whose email already exists updates it
in place rather than duplicating it. Full reference lives on the landing page and
in /llms.txt.
There are two kinds of key:
ck_secret_…— secret key, for your backend. Full access to every endpoint.ck_pub_…— publishable key, for the browser. Can only create contacts and is locked to your domains.
MCP server
AI clients (Claude Desktop, claude.ai custom connectors, Cursor, the MCP Inspector) can manage your contacts through an MCP server at:
https://contactapi.dev/mcp
Auth is OAuth 2.1 with dynamic client registration — point a client at the
URL and it discovers the authorization server, registers itself, and sends you to
log in and approve access; no API key to copy. The server exposes five tools that
mirror the REST API: list_contacts, get_contact, create_contact
(upsert-by-email), update_contact, and delete_contact. Everything is scoped to
the account you log in as.
The OAuth provider is Better Auth's mcp plugin
(src/auth.ts); the tools and endpoint wiring live in
src/mcp/server.ts and src/index.ts.
Development
Prerequisites: Vercel CLI installed globally.
npm install
vc dev
open http://localhost:3000
Build
npm install
vc build
Deploy
npm install
vc deploy
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.