BetaFinds vs Chatpack MCP

A side-by-side look at the BetaFinds and Chatpack MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

BetaFinds logoBetaFindsDeveloper Tools · Remote HTTP/SSEPublish and update your startup on BetaFinds from an AI agent — listings, changelog, releases.53GoodAuth: not declaredChatpack MCP logoChatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.87ExcellentAuth: no auth required

Verdict: choose BetaFinds for developer tools work over a hosted endpoint; choose Chatpack MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

BetaFinds logoChoose BetaFinds when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like create_startup, update_startup, list_categories.
Explore BetaFinds

Chatpack MCP logoChoose Chatpack MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_docs, get_document, get_integration_guide.
Explore Chatpack MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBetaFinds logoBetaFindsChatpack MCP logoChatpack MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal53/100 · Good87/100 · Excellent
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars0224
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools145

Tools & capabilities

BetaFinds tools 14

  • create_startupCreate 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_startupUpdate 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_categoriesList of available categories (slug and name) for create_startup.
  • upload_imageUpload 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_startupsList of your startups on BetaFinds (slug, name, status). Updates can only be published for startups with APPROVED status.
  • publish_updatePublish 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_releaseCreate 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_uploadGet 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_uploadConfirm 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_stageChange 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_launchAnnounce 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).
  • +2 more on the listing page

Chatpack MCP tools 5

  • search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.
  • get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.
  • get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
  • list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.
  • get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

BetaFinds

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "betafinds": {
      "url": "https://betafinds.com/api/mcp"
    }
  }
}

Chatpack MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chatpack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chatpack/mcp"
      ]
    }
  }
}

Frequently asked questions

BetaFinds is categorized under Developer Tools and uses a remote HTTP/SSE transport. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick BetaFinds for developer tools work and Chatpack MCP for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

BetaFinds has no declared pricing — check the project's own site. Chatpack MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add betafinds and chatpack-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, BetaFinds has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Chatpack MCP has 87/100 (Excellent) with 4 views, 0 installs and 224 GitHub stars.