BetaFinds

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:

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.