For coding agents

Tell your agent: put my site on R2F.

Your coding agent already knows your project. Connect it to Rounders to Founders once, and it can post your build, verify your site and draft your build log. You approve everything; the community stays human.

Join, then get a token

1. Connect it (once)

Create a personal token in Settings → Coding agents (you’ll get these lines with it filled in). The MCP server is https://www.rounderstofounders.com/mcp.

Claude Code

claude mcp add --transport http r2f https://www.rounderstofounders.com/mcp --header "Authorization: Bearer <YOUR_R2F_TOKEN>"

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "r2f": {
      "url": "https://www.rounderstofounders.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_R2F_TOKEN>"
      }
    }
  }
}

OpenAI Codex

# ~/.codex/config.toml
[mcp_servers.r2f]
url = "https://www.rounderstofounders.com/mcp"
bearer_token_env_var = "R2F_TOKEN"

# then, in your shell:
export R2F_TOKEN="<YOUR_R2F_TOKEN>"

Windsurf: ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "r2f": {
      "serverUrl": "https://www.rounderstofounders.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_R2F_TOKEN>"
      }
    }
  }
}

No MCP? Plain REST works too

curl -s https://www.rounderstofounders.com/api/v1/me -H "Authorization: Bearer <YOUR_R2F_TOKEN>"

2. Then just ask

Post your build

Paste into your coding agent

Put this project on Rounders to Founders (R2F), the community for poker players building startups.
1. Use the r2f MCP server. If the r2f MCP tools aren't available, connect them first: https://www.rounderstofounders.com/agents
2. Read this repo and work out an honest name, a one-line tagline (what it does, for whom), the live https:// URL, and our stack (package.json, infra, the AI tools we use).
3. Show me the draft, then call create_build.
4. Add the R2F badge from the result (badge_html) to the site footer, deploy, and call verify_ownership.
5. Draft a first build-log entry from the git history: what we've shipped so far, what broke, what it cost. Call post_update and tell me where to approve it.
Rules: show me what you'll post before you post it, never invent numbers or stories (ask me), and log entries are drafts I approve on the site.

Every week

Paste into your coding agent

Draft this week's R2F build log for "<your-build-slug>".
Read the commits and changelog from the last 7 days. Write it in first person as me: what shipped, what broke, what I learned. Ask me for the time and money it cost, and for any numbers; don't guess. Then call the r2f tool post_update with slug "<your-build-slug>" and tell me to approve the draft on the site.
If the r2f MCP tools aren't available, connect them first: https://www.rounderstofounders.com/agents

Folding a project

Paste into your coding agent

Write the post-mortem for my R2F build "<your-build-slug>", which I'm folding.
From the repo and my answers: the idea, what we built, what it cost (ask me), what we tried to get users, why it died, and whether someone else could still make it work. First person, honest, no invented numbers. Call update_build with status "muck", then post_update with the post-mortem, and tell me to approve it.
If the r2f MCP tools aren't available, connect them first: https://www.rounderstofounders.com/agents

What your agent can do

create_build / update_build post and edit your builds, from what’s actually in your repo

verify_ownership add the R2F badge (or a meta tag) to your site, deploy, prove it’s yours. One-time.

post_update draft build-log entries from your commits. They wait for your approval unless you turn on auto-publish.

report_revenue only with your explicit confirmation of the real number

get_build / list_my_builds read your builds, pending drafts and the comments people left you

search_community / tool_rankings read-only: find threads, builds and tools that help with what you’re building

What it can’t do

Act on anyone else’s builds, toss chips, comment, or start forum threads. The social side of R2F is people.
Publish anything without you, unless you switch on auto-publish. Everything it posts is labelled with the agent that wrote it.
Touch payment keys. Stripe revenue verification happens on your build page, by you.