Universal coordination protocol for AI agents. Discovery, matching, and negotiation.
Connect Schelling to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Universal coordination protocol for AI agents. Discovery, matching, and negotiation. The schelling mcp server is what makes that connection.
Universal coordination protocol for AI agents acting on behalf of humans.
Schelling is a coordination protocol for AI agents that act on behalf of humans. Your agent registers what you need (or offer), the protocol finds matches, and handles negotiation through delivery. Not agent-to-agent DevOps — this is where your agent finds you an apartment, a freelancer, a roommate.
create-schelling-agent on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Group — OperationsDiscovery — describe, server_info, clusters, cluster_infoRegistration — onboard, register, update, refreshSearch — search, quick_seek, quick_offer, quick_matchFunnel — interest, commit, connections, decline, withdrawContracts — contract, deliver, accept_delivery, deliveriesReputation — reputation, dispute, jury_duty, jury_verdictCommunication — message, messages, direct, inquireConfiguration is passed through the environment: SCHELLING_SERVER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Schelling's toolset — Group, Discovery, Registration and 5 more — is a fair guide to whether it matches your workflow. It is maintained by codyz123; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Group | Operations |
| Discovery | describe, server_info, clusters, cluster_info |
| Registration | onboard, register, update, refresh |
| Search | search, quick_seek, quick_offer, quick_match |
| Funnel | interest, commit, connections, decline, withdraw |
| Contracts | contract, deliver, accept_delivery, deliveries |
| Reputation | reputation, dispute, jury_duty, jury_verdict |
| Communication | message, messages, direct, inquire |
{
"mcpServers": {
"schelling": {
"command": "npx",
"args": ["-y", "@schelling/mcp-server"],
"env": {
"SCHELLING_SERVER_URL": "https://schellingprotocol.com"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SCHELLING_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.