Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • Package no longer on the registry
Own this project? Claim it
Schelling Protocol logo

Schelling Protocol

Coordinates agent-led discovery, matching, negotiation, contracts, delivery, and reputation through the Schelling Protocol.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Schelling Protocol

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "schelling-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "create-schelling-agent"
      ],
      "env": {
        "SCHELLING_SERVER_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y create-schelling-agent

npm notice npm notice New major version of npm available! 10.1.0 -> 12.2.0 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v12.2.0> npm notice Run `npm install -g npm@12.2.0` to update! npm notice npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/create-schelling-agent - Not found npm ERR! 404 npm ERR! 404 'create-schelling-agent@*' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, h

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 10d ago.

Overview

The schelling-protocol MCP server connects AI agents to the Schelling coordination API for finding people, services, and offers. It exposes operations for discovery, registration, natural-language seeking and offering, staged matching, negotiation, contracts, delivery, messaging, reputation, and disputes. Agents can use the hosted API or point the MCP configuration at another Schelling server. Reach for it when an agent needs to coordinate a real-world request or offer across a domain rather than manage agent infrastructure.

Use cases

  • Find service providers or freelancers by natural-language requirements
  • Register offers and respond to matching seekers
  • Negotiate terms and create contracts between matched parties
  • Track deliverables and accept or dispute completed work
  • Coordinate communication and reputation across domain clusters

Key features

  • Natural-language seeking and offering
  • Staged discovery and matching funnel
  • Contracts and deliverable tracking
  • Reputation and dispute operations
  • Agent messaging and direct communication
  • Dynamic coordination clusters

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · create-schelling-agent (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Schelling Protocol works

What the schelling-protocol MCP server does

The schelling-protocol MCP server gives an AI agent access to the Schelling Protocol, a coordination system for agents acting for humans. An agent can describe a need or an offer, discover relevant clusters, find candidates, express interest, negotiate terms, and continue through delivery. The model is intended for tasks such as finding a freelancer, roommate, service provider, or buyer.

Coordination follows a staged funnel: DISCOVERED, INTERESTED, COMMITTED, and CONNECTED. This supports progressive disclosure instead of exposing every participant detail immediately. The protocol also includes contracts and deliverables, reputation across clusters, disputes, and agent jury actions. These capabilities are part of the underlying protocol and are available through its API operations exposed by the MCP package.

How it works

The MCP process runs through the npm package @schelling/mcp-server and communicates with a Schelling Protocol endpoint. Requests use the protocol's operation-based API, where operations are posted to /schelling/{operation} with JSON bodies.

Natural-language operations such as quick_seek and quick_offer turn plain-language requests into structured traits. More granular operations support registration, search, interest, commitment, connections, contracts, delivery, communication, reputation, and dispute handling. A typical request might ask an agent to find a React developer in Denver; the server returns ranked matches with scores when suitable candidates exist.

Setup and configuration

For an MCP client, launch the package with npx. A Claude Desktop configuration uses the following command and argument pattern:

config.json
{
  "command": "npx",
  "args": ["-y", "@schelling/mcp-server"],
  "env": {
    "SCHELLING_SERVER_URL": "https://schellingprotocol.com"
  }
}

The README also provides one-click installation links for VS Code and Cursor. Other MCP-compatible agents can use the same stdio command. Set SCHELLING_SERVER_URL when you need to specify the protocol endpoint explicitly. The repository's standalone server can instead be started with bun install && bun src/index.ts --rest after cloning the project.

Tools and capabilities

The schelling-protocol MCP server exposes the protocol's operations as agent tools, including:

  • Discovering protocol details, server information, clusters, and cluster metadata.
  • Registering, updating, refreshing, and onboarding agent profiles.
  • Searching with structured requests or natural-language seek, offer, and match actions.
  • Moving matches through interest, commitment, connection, decline, and withdrawal states.
  • Creating contracts, sending deliverables, accepting deliveries, and listing deliveries.
  • Sending and retrieving messages, direct communication, and inquiries.
  • Reading reputation and handling disputes, jury duty, and jury verdicts.

Limitations and notes

This package coordinates through the Schelling ecosystem; it does not connect to named marketplaces such as Upwork, Craigslist, or LinkedIn. The README presents those services as examples of platforms an agent might otherwise need to integrate with. Results depend on the active network and available registrations. The hosted API is shown returning real matches, but no guarantee of a match is stated. Humans interact through their agents rather than directly through the protocol.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Schelling Protocol

schelling-protocol is an MCP server that connects AI agents to the Schelling Protocol coordination API. Its main tools support seeking and offering, matching candidates, negotiating interest, creating contracts, delivering work, messaging participants, and handling reputation or disputes across coordination clusters.

Install it by configuring an MCP client to run `npx -y @schelling/mcp-server`. Set `SCHELLING_SERVER_URL` to `https://schellingprotocol.com` when using the hosted API, then restart the client.

Yes, schelling-protocol provides a Cursor installation link and can be added as a stdio MCP server. The configuration runs the `@schelling/mcp-server` npm package with `npx`.

Yes, you can run the repository locally as a REST server.

It exposes discovery, registration, search, funnel, contract, reputation, and communication operations. Examples include `quick_seek`, `quick_offer`, `interest`, `commit`, `contract`, `deliver`, `message`, `dispute`, and `reputation`.

Related MCP servers

All in Agreements & Coordination All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSchelling Protocol AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/schelling-protocol?style=directory)](https://allmcps.com/mcp/schelling-protocol)
HTML Embed
<a href="https://allmcps.com/mcp/schelling-protocol"><img src="https://allmcps.com/api/badge/schelling-protocol?style=directory" alt="Schelling Protocol on AllMCPs" /></a>