Integrations
Work with your cards and contacts from your own AI
Build your card page. Find a contact you exchanged with. Add a note. Ask for it from the AI or tool you already use.
- REST API
- MCP
- CLI
- skill
- plugin
Three ways to connect
The same operations are available through each. One API key is enough.
REST API
Work with cards, contacts, exchanges and your card page over HTTP. The definition is published in OpenAPI format.
Open /openapi.jsonMCP
An AI that supports MCP can call the same operations as tools. Write tools do not run unless you pass confirm: true.
See how to connectCLI (meishi)
Work with contacts, exchanges, your card page and the AI avatar from the terminal. It runs on Node.js 20 or later.
See examples
Use it from your own AI
It works from AI that supports MCP, such as Claude Code and Codex.
Make an API key
Make one with "Make a key" in the dashboard (/my). The key is shown only once, when you make it.
Connect MCP
In Claude Code, run this in your terminal. Put your own key in place of the placeholder.
export MEISHI_API_KEY='<your API key>' claude mcp add --transport http meishi https://kizunatap.com/mcp --header "Authorization: Bearer $MEISHI_API_KEY"Talk to it
For example, you can ask:
- Who did I exchange cards with today?
- Find the people from "Acme"
- Add a note to Tanaka
A write runs only when the call includes confirm: true. The official skill teaches the AI to show you the change first and get your OK.
Official skill and plugin
Official skill (kizunatap)
It teaches the AI which tool to use when, and how to ask for your OK before writing. It checks the server version first, then reads the guide.
Plugin (meishi)
For Claude Code and Codex. It bundles the MCP endpoint and the skill.
For the skill, the plugin and the CLI, please contact us. MCP and the REST API need only an API key. Contact us
From the command line (meishi)
Check your contacts and card page from the terminal.
meishi me
meishi contacts list --q acme
meishi exchanges list --state captured
meishi profile get
The key is read from the MEISHI_API_KEY environment variable or a config file. It goes only in the Authorization header and is never printed. Add --json for raw JSON.
What is supported
| Way | What you can do | What you need |
|---|---|---|
| REST API | Operate cards, contacts, exchanges, your card page and the AI avatar over HTTP. Definition at /openapi.json | An API key |
| MCP (/mcp) | Call the same operations as tools from an MCP-capable AI. Writes need confirm: true | An API key and an MCP-capable AI |
| CLI (meishi) | Operate contacts, exchanges, your card page and the AI avatar from the terminal | An API key and Node.js 20 or later |
| Official skill | Teaches the AI which tool to use and how to confirm before writing | An AI connected through MCP |
| Plugin (Claude Code, Codex) | The MCP endpoint and the skill, bundled together | Claude Code or Codex |
Using it safely
- You make API keys in the dashboard (/my). A key is shown only once, when you make it.
- Each key carries scopes, the range of operations it allows. An operation outside its scopes is refused.
- A write through MCP does not run unless you pass confirm: true.
- You can make a new key at any time. Making one disables the previous key.
FAQ
Is it free?
Yes. Free includes one API key. Pro lets you use several keys.
Which AI can I connect?
You can use AI and tools that support MCP or the REST API, such as Claude Code and Codex.
What can it do?
Search contacts, add notes and update their status, check exchanges, build and publish your card page, and answer for your AI avatar. Operations that write run only with confirm: true.
Where do I make an API key?
Use "Make a key" in the dashboard (/my). The key is shown only once. Making a new key disables the previous one.
Is it safe to let an AI see my contacts?
An AI you give a key to can read and write the contacts that key allows. You decide which AI gets a key. If you are worried, make a new key and the old one stops working.
Where do I get the skill, plugin and CLI?
Please contact us (contact@kazuyahibara.com). MCP and the REST API need only an API key.
Make your own card
Sign up with just your email. Once your card page exists, you can make an API key.
