# BetaFinds [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pendurov/betafinds-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/betafinds

## Description
Publish and update your startup on BetaFinds from an AI agent — listings, changelog, releases.

## Tools
Capabilities this server exposes over MCP:

- **create_startup** — Create a new startup on BetaFinds (submitted for review). Upload the logo and screenshots first via upload_image (or POST https://betafinds.com/api/v1/images) and pass the returned URLs here. Set the category by slug — get the list via list_categories (a category name also works, case-insensitive).
- **update_startup** — Update an existing startup: app-store links, website, short/full description, tags, category, logo and screenshots. Upload the logo and screenshots first via upload_image and pass the returned URLs (screenshots fully replace the current set; to clear the logo, pass an empty string). Pass only the fields you want to change. See current values via list_my_startups. Note: editing an approved startup sends it back to moderation.
- **list_categories** — List of available categories (slug and name) for create_startup.
- **upload_image** — Upload an image (logo or screenshot) for create_startup. Pass the file content as base64 (data is base64 only, no data: prefix). Returns a url to pass into create_startup. Max 2 MB; formats: JPEG, PNG, WebP, GIF.
- **list_my_startups** — List of your startups on BetaFinds (slug, name, status). Updates can only be published for startups with APPROVED status.
- **publish_update** — Publish an update (an entry in the «What's new» feed) for your startup. Subscribers receive an email summary within ~10 minutes. body supports Markdown.
- **create_release** — Create a release (version) of your startup. By default also publishes a RELEASE-type update with the notes text. After creation, upload files via request_asset_upload.
- **request_asset_upload** — Get a one-time link to upload a release file (Windows/Mac/Android/Linux, up to 1 GB). Then upload the file: curl -T <file> '<upload_url>'. After uploading, call complete_asset_upload.
- **complete_asset_upload** — Confirm that the release file has been uploaded. Verifies the file's presence and size in storage and makes it available for download.
- **get_releases** — Список опубликованных релизов стартапа с файлами. Для LAUNCHED-проектов downloadUrl — постоянная прямая ссылка. На закрытых стадиях ссылка возвращается только для своих стартапов или где у вас открыт доступ (иначе locked=true, downloadUrl=null).
- **change_startup_stage** — Change your startup's product stage: PRELAUNCH — preparing to launch, BETA — recruiting beta testers, PAUSED — development paused (requires public_note). To move to LAUNCHED use announce_launch. Allowed transitions: PRELAUNCH→BETA/PAUSED, BETA→PAUSED, PAUSED→PRELAUNCH/BETA.
- **announce_launch** — Announce your startup's official launch: the stage becomes LAUNCHED, a LAUNCH update is published, and waitlist members are notified (once). A working product link is required (url or an already saved store link).
- **get_waitlist** — Waitlist summary for your startup: aggregated counters (active, per week/month, ready to test, invited/accepted), answer distribution for the question, recent anonymized answers and campaigns with aggregated statistics. Participants' contact details are not returned.
- **get_store_reviews** — Public Google Play and App Store reviews of your startup: monitoring state per store and the latest reviews (rating, text, developer response). Reviews are collected automatically via the app links.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "betafinds": {
    "url": "https://betafinds.com/api/mcp"
  }
}
```

## Documentation

## What the BetaFinds MCP server does

The BetaFinds MCP server lets an authenticated AI agent manage startup content on BetaFinds, a directory for early-stage startups. It covers the main publishing tasks: finding the startups associated with an account, creating or editing a listing, adding images, posting changelog updates, and managing public software releases.

New startup listings are submitted for moderation before they appear publicly. Existing listings can be updated through their startup slug. The server also exposes category lookup, which helps an agent select an available category by slug rather than guessing a value.

## How it works

The BetaFinds MCP server is hosted at `https://betafinds.com/api/mcp` and uses Streamable HTTP. It is stateless, so there is no local service or repository process to run. Requests are authenticated with a Bearer token created from the BetaFinds profile page.

Release files follow a multi-step process:

1. Create a release for a supported platform and version.
2. Request a presigned upload URL for each file.
3. Upload the file to that URL with a direct `PUT` request.
4. Complete the asset upload so the release file is finalized.

Published changelog updates are sent to subscribers in an email digest within approximately 10 minutes, according to the project documentation.

## Setup and configuration

Create an API token at `https://betafinds.com/profile`, then add the hosted endpoint to an MCP client with the token in an `Authorization: Bearer ...` header. The documented Claude Code setup uses the HTTP transport directly:

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

Claude Desktop can connect through `mcp-remote`, with the endpoint and authorization header specified in `claude_desktop_config.json`. The server also publishes MCP auto-discovery metadata at `https://betafinds.com/.well-known/mcp.json`. Keep the token private and provide it only through the client configuration used for the connection.

## Tools and capabilities

Available operations include:

- `list_my_startups` to find the account's startups and slugs.
- `list_categories` to retrieve available category slugs.
- `create_startup` and `update_startup` to create or edit listing fields.
- `upload_image` to add a logo or screenshot and receive an image URL.
- `publish_update` to add an entry to a startup's changelog feed.
- `create_release` and `get_releases` to create releases and list public releases.
- `request_asset_upload` and `complete_asset_upload` to prepare and finalize release-file uploads.

Listing startups first is useful because later operations need the relevant startup identifier or slug.

## Limitations and notes

The hosted endpoint means the BetaFinds MCP server does not require a local installation, but it does require a BetaFinds API token. Creating a startup does not make it immediately public because submissions go through moderation. The release-file workflow is not a single MCP call: the agent or client must perform the file transfer between requesting and completing the upload.

The documented server targets BetaFinds at `betafinds.com`.

_Full upstream README: https://allmcps.com/mcp/betafinds/readme_