BetaFinds MCP Server

Publish and update your startup on BetaFinds straight from an AI agent.

BetaFinds is a directory for early-stage startups — discover, upvote and discuss new projects. This is its official Model Context Protocol server: point an AI agent (Claude, Cursor, …) at it and it can create your listing, post changelog updates, and upload release files for you.

Endpoint: https://betafinds.com/api/mcp — Streamable HTTP, hosted (nothing to install)
Auth: Bearer token, created at https://betafinds.com/profile
Full API docs: https://betafinds.com/api.txt
Auto-discovery: https://betafinds.com/.well-known/mcp.json

Why

Filling out submission forms — description, screenshots, links, release files — is the tedious part of launching. If you already build with an AI agent, you can skip the form entirely:

"Upload my project to betafinds.com" — then hand the agent your API token.

Quickstart (Claude Code)

Create an API token at https://betafinds.com/profile (format: blt_…).

Add the server:

claude mcp add betafinds https://betafinds.com/api/mcp \
  --transport http \
  --header "Authorization: Bearer blt_YOUR_TOKEN"

Ask your agent: "List my startups on BetaFinds", or "Publish an update to <startup>: shipped dark mode and fixed the onboarding flow."

Claude Desktop

Add to your claude_desktop_config.json via mcp-remote:

{
  "mcpServers": {
    "betafinds": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://betafinds.com/api/mcp",
        "--header", "Authorization: Bearer blt_YOUR_TOKEN"
      ]
    }
  }
}

Tools

Tool	What it does
`list_my_startups`	List your startups and their slugs (start here)
`list_categories`	List available categories (by slug)
`create_startup`	Create a new startup listing (submitted for moderation)
`update_startup`	Update an existing startup's fields
`upload_image`	Upload a logo or screenshot; returns an image URL
`publish_update`	Post a "what's new" entry to a startup's changelog feed
`create_release`	Create a release (version) for Windows / macOS / Android / Linux
`request_asset_upload`	Get a presigned URL to upload a release file
`complete_asset_upload`	Finalize a release-file upload
`get_releases`	List a startup's public releases

Typical flow

Publishing a new build end to end:

create_release → request_asset_upload (per file) → PUT the file → complete_asset_upload

Subscribers of the startup receive an email digest within ~10 minutes of a published update.

Notes

The server is hosted and stateless (Streamable HTTP) — there is nothing to run locally.
Listing is free; new startups go through moderation before appearing.
A Russian-language sibling runs the same protocol at BetaList.ru (https://betalist.ru/api/mcp).