Contactapi

io.github.kozmos-techPublished by GitHub account kozmos-techv0.1.1Updated Oct 24, 2026

An open-source API for collecting and managing contacts and signups.

VerifiedSTDIODesktop onlyDatabasesBusiness & Commerce

Overview

AI-generated overview

An MCP server for Contactapi, an open-source contact and signup API, letting an assistant list, read, create, update and delete contacts in your account.

What you can do
List and fetch contacts, paginated, from your Contactapi account, and read a single contact by ID. Create or upsert a contact by email, with any extra JSON fields saved as-is. Update an existing contact's fields. Delete a contact. All operations are scoped to the account you log in as.
When to use it
Use it when you keep contacts or signups in Contactapi and want an assistant to look them up, add new ones, correct details or remove entries without calling the REST API by hand.
Requirements
A Contactapi account and a client that supports OAuth 2.1 with dynamic client registration; you log in and approve access in the browser, so no API key needs to be copied. The README also documents a hosted endpoint and a REST API using a Bearer key.
Before you install
The tools can create, update and delete contacts, and deletes are permanent. Creating a contact whose email already exists overwrites that contact in place rather than adding a new one. Access is granted to your whole account, so review what the assistant changes.

Installation

In SourceWeft

  1. Open Contactapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

contactapi

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
MethodPathKeyDescription
POST/v1/contactssecret or publishableCreate (or upsert) a contact by email
GET/v1/contactssecretList contacts, paginated
GET/v1/contacts/:idsecretFetch a single contact
PATCH/v1/contacts/:idsecretUpdate a contact
DELETE/v1/contacts/:idsecretDelete 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.

bash
npm installvc devopen http://localhost:3000

Build

bash
npm installvc build

Deploy

bash
npm installvc deploy

License

MIT

Source: README.md at commit 7006be5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts