@dedot-ai/mcp

Dedot MCP plugin — lets your AI find people worth meeting.

Fastest way to get started

npx -y @dedot-ai/cli@latest init

This writes the MCP config for your IDE (Claude Code, Cursor, or Claude Desktop), then tells you to restart and say "Log me into Dedot." — done in under a minute.

Or configure manually below.

Note: npx -y @dedot-ai/mcp uses the mcp executable name (npm’s rule for scoped packages). The package ships both mcp and dedot-mcp pointing at the same entry. Use @dedot-ai/[email protected] or later if you saw dedot-mcp: command not found with older builds.

Quick start (manual)

Step 1 — Add to your MCP config

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "dedot": {
      "command": "node",
      "args": ["/absolute/path/to/debot-be/packages/mcp-plugin/dist/index.js"],
      "env": {
        "DEDOT_API_BASE_URL": "http://localhost:8080"
      }
    }
  }
}

Replace DEDOT_API_BASE_URL with your deployed API URL when running in production.

Step 2 — Restart Claude Desktop

After saving the config, quit and reopen Claude Desktop. You should see dedot listed under Settings → Developer → MCP servers with a green running badge.

Step 3 — Log in (first time only)

Open a new chat and say:

"Log me into Dedot."

Claude will call the dedot_login tool, which:

1. Opens a browser window to the Dedot login page.
2. You enter your email and receive an OTP code.
3. Token is automatically sent back from the browser to the plugin.
4. Token is saved to ~/.dedot/auth.json — future sessions reconnect silently.

Step 4 — Register your profile

After logging in, say:

"Register my Dedot profile."

Claude will ask you for the profile fields (name, company, industry, what you do, can help with, looking for, etc.) and call dedot_register_profile.
Once registered, the backend generates your embedding and starts matching you with other profiles.

Step 5 — Check your candidates

Wait a few minutes for matching to complete, then say:

"Show me my Dedot candidates."

Claude calls dedot_get_candidates and presents your shortlist with anonymised profiles.

Step 6 — Evaluate and confirm

After reviewing the candidates:

"Evaluate my Dedot candidates — I'm interested in candidate X."

When both parties express interest, a mutual match is created. You then confirm with:

"Confirm my Dedot match."

Once both sides confirm, contact details are revealed.

Referrals (invite links, leaderboard, custom code)

Pre-pricing: referrals are for attribution and leaderboard / landing — not billing. Stored scores in the API are growth metrics until a pricing launch.

After you have a profile, use dedot_referral_stats, dedot_leaderboard, and dedot_update_referral_code.
On first registration, pass referred_by_code via dedot_register_profile if the user arrived via dedot.ai/join/{code}.

There is no separate Dedot push notification for referral “rewards”; the user sees activity when they run the tools above.

Manual test matrix and Claude Desktop walkthrough: docs/referral-testing.md.

All available tools

| Tool | Description | |------|-------------| | dedot_login | Authenticate via email OTP (browser opens automatically) | | dedot_logout | Remove stored auth token | | dedot_status | Check auth + profile summary + flush pending events | | dedot_register_profile | Register your profile on the network (optional referred_by_code) | | dedot_get_profile | View your current profile | | dedot_update_profile | Update profile fields (triggers re-embedding + re-matching) | | dedot_deregister | Remove yourself from the network | | dedot_get_candidates | Get your current candidate shortlist | | dedot_evaluate | Submit AI evaluation votes for candidates | | dedot_get_matches | List mutual matches | | dedot_confirm_match | Confirm a match — contact revealed when both confirm | | dedot_decline_match | Decline a match | | dedot_check_events | Pull and flush any queued events from the backend | | dedot_referral_stats | Invite link, successful invites, leaderboard score (pre-pricing; not billing) | | dedot_leaderboard | Top referrers (public; no extra login) | | dedot_update_referral_code | Set a custom invite code once |

Auth flow (how browser login works)

Your AI calls dedot_login
        │
        ▼
Plugin starts local HTTP server on port 47832
        │
        ▼
Browser opens → https://api.dedot.ai/login?callbackPort=47832
        │
        ▼
You enter email → receive OTP → enter OTP
        │
        ▼
Login page POSTs token to http://127.0.0.1:47832/callback?token=...
        │
        ▼
Plugin receives token → saves to ~/.dedot/auth.json → returns "Logged in"

All subsequent sessions load the saved token automatically — no repeated logins.

Notifications — how they work

Dedot uses a live-first, email-fallback model:

| Scenario | What you see | |----------|-------------| | Plugin is online (callback URL reachable) | Event delivered directly to your AI — no email sent | | Plugin is offline / no callback URL | Event queued on backend; fallback email sent to your registered address |

This means if your plugin is running, you will not receive notification emails — your AI handles everything in-session. Email is only the fallback for when you are away.

Events you can receive

| Event | When | |-------|------| | NEW_CANDIDATES | Backend found profiles worth reviewing | | MATCH_FOUND | Both you and another member's AI said yes; awaiting human confirmation | | MATCH_CONFIRMED | Both humans confirmed — contact details are now available (no email for this one) |

Offline reconnect

If the plugin was offline when events were dispatched, they are queued in the backend.

On startup, if you are authenticated, the plugin automatically fetches and flushes any queued events. You can also trigger a manual flush at any time:

"Check my Dedot events."

Troubleshooting

| Symptom | Fix | |---------|-----| | dedot shows as stopped in MCP settings | Check the path to dist/index.js is correct and absolute | | Not logged in message on startup | Normal — just say "Log me into Dedot" to trigger login | | Login browser window doesn't open | Make sure a display/browser is available; not supported in headless environments | | ECONNREFUSED when calling tools | Backend is not running at DEDOT_API_BASE_URL | | Token expired / 401 errors | Say "Log me into Dedot" again to refresh the token |