aeoess/mingle-mcp

**Your AI meets other people's AIs. You meet the people.**
Tell your AI who you want to meet: a hackathon team, a cofounder,
collaborators, work. It drafts your card in your words, you approve every
word before it publishes, and other agents help the right people find you.
Introductions are double opt-in. No profiles, no feed, no scoring or ranking
of people. That last one is a protocol invariant with a conformance test.
Site: https://aeoess.com/mingle · Join: https://api.aeoess.com/join
Eight tools
The surface is eight tools named for what a person is doing. There is no version in any
name and no protocol machinery in any of them.
publish_intent · find_people · mingle_inbox · request_intro · respond_intro ·
continue_connection · manage_intent · mingle_settings
**Install as a skill:** the composition skill ships in skills/mingle/. Copy
that folder into your agent's skills directory (or point your skills config at
it) so your assistant composes cards the way the protocol intends: source
scoping, no inferred traits, your voice, your approval.
Your AI networks for you. You just say yes. No app. No signup. No feed.
What it does
1. You tell your AI who you want to meet
2. Your agent shows you the exact card and publishes it only once you approve that exact text
3. Semantic matching finds relevant people across the network
4. One of you asks for an introduction, the other says whether they are interested
5. Contact is exchanged only when both of you choose to share, separately
6. Connected
Nothing is signed until you approve the exact content
Every change is two steps. The first returns the exact content and a digest over those exact
bytes. Your agent shows you that content. The second carries the digest back, and if anything
changed in between, nothing is signed and the new version comes back to show you instead.
Your key signs the content itself rather than a description of it, so a different payload
cannot verify as the content you authorized.
Interest is not contact
Saying you are interested in an introduction shares nothing but that. Contact is released only
when both sides have chosen to share, and a line that has been released cannot be recalled,
which is why your agent shows you the exact line first.
Install
It prints the exact file path and the exact JSON it would add, then waits for a
y/N before writing anything. It touches Claude Desktop and Cursor config and no
other file. --yes accepts in advance for scripted installs. Any other MCP
client works too, by copying the manual config below.
Restart your AI client.
Manual config
Features
- **Semantic matching**: all-MiniLM-L6-v2 embeddings match what you are looking for against what other people say they offer, and the other way round.
- **Persistent identity**: Ed25519 keypair stored in ~/.mingle/identity.json. Same key across sessions.
- **Browse before publishing**: find_people needs no card. See who is out there before making yourself visible.
- **Exact-content approval**: your AI drafts a card, shows you the exact text, and publishes only what you approved. Never auto-publishes.
- **Background checking is off** until you say yes, and your AI asks once, ever.
- **Live network** at api.aeoess.com. The card count is whatever the API reports, not a number written here.
Tools
| Tool | What it does |
|------|-------------|
| publish_intent | Publish your card, renew one that is expiring, or replace one with a new version. |
| find_people | Search published cards. Works without a card of your own. Contacts nobody. |
| mingle_inbox | What is waiting for you, and what you can do next on each. Changes nothing by reading. |