Tambor

Connect & usage

Tambor's whole surface for members is an MCP server. Connect your agent once over OAuth — that connection is your account. There is no dashboard to manage.

Prerequisites

  • An MCP-capable client (e.g. Claude, or MCP Inspector).
  • A card only if you request an intro that carries a contribution — most paths are free.

Connect

  1. Add the Tambor MCP server URL to your client: http://localhost:3001/mcp
  2. Your client discovers the authorization server and registers itself automatically (PRM → AS metadata → Dynamic Client Registration).
  3. You authorize with a one-time email sign-in link and a consent screen (“Allow your agent to request introductions on your behalf”).
  4. Optionally add a card right away, or skip it — your first paid request sends a one-time link and completes once the card is added. Nothing is charged before delivery.

Tools

  • find_path (read-only) — anonymized paths to a target by name, company, or LinkedIn URL. Returns seniority band, relationship strength, tenure, recency, and an explicit contribution (0 = free, which most are). Never returns names or emails.
  • request_intro — request an intro along a path. Places an authorization hold for the quoted amount (you confirm the price). Your connector sends the intro personally, with you and the target on it. Captured only on delivery — any decline or expiry releases the hold.
  • confirm_intro — tell Tambor the connector's intro landed. Captures the hold and pays the connector.
  • get_intro_status (read-only) — check a request. The connector is revealed on accept, the target's name on send, contact details on delivery.
  • list_intro_requests (read-only) — your requests, newest first. Handy when a fresh conversation has lost the request id.
  • place_bounty — attach a public pledge to an unmatched ask (intent only, nothing charged). Matching connectors are alerted.

Troubleshooting

  • Repeated 401s — remove the connector from your client and add it again to force a fresh OAuth flow.
  • Sign-in link expired — links last 15 minutes. Reconnect from your client for a fresh one.
  • Signed out after weeks away — refresh tokens last 30 days; the client just re-runs the connect flow.
  • No email arrived — check spam. The subject names the agent asking to connect.

What Tambor reads and writes

Tambor reads the community's anonymized graph (no identities) and writes intro requests and payment authorizations tied to your account. It never reads your other data, and never shares your identity with a connector before you request an intro.

For connectors

Connectors join by invitation, import their network, choose free or a contribution per contact, and accept or decline requests.