NestDaddy

VibeCodePicks

com.vibecodepicks/vibecodepicks · v2.6.1

The best vibe coding tools, ranked by what you want to build

Connect Remote server

Terminal
claude mcp add --transport http vibecodepicks https://vibecodepicks.com/api/mcp/
~/.cursor/mcp.json
{
  "mcpServers": {
    "vibecodepicks": {
      "url": "https://vibecodepicks.com/api/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "vibecodepicks": {
      "type": "http",
      "url": "https://vibecodepicks.com/api/mcp/"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://vibecodepicks.com/api/mcp/

Tools 30 found in our last check

  • search

    Find vibe coding / AI tools. Rows: id|name|category|$from/mo|free(1/0). Use fetch(id) for details.

  • fetch

    Tool profile by id. Default: summary, best_for, price, free, 2 strengths, 2 weaknesses, url. fields: summary description best_for not_for skill coding pricing platforms strengths weaknesses alternatives video compare official all.

  • recommend_tools

    Ranked best-fit tools for a goal, matched on verified capabilities (not categories), with why + caveat. Saved tags can reorder equally-matched tools by up to 2 points when the new matcher is on (platforms/preferences tags only); they never override a verified-capability filter,…

  • compare_tools

    Side-by-side of two tools + comparison page url.

  • list_alternatives

    Alternatives to a tool. Rows: id|name|$from/mo|free.

  • list_scenarios

    Use-case scenarios (e.g. ai-game-development, code-review) with top tools by community sentiment.

  • scenario

    Tools competing in one scenario, ranked by community sentiment, with compact strengths/weak spots here.

  • list_categories

    Category and use-case keys with tool ids.

  • whats_new

    Daily feed. With key: honors the saved feed mode — by_interests: new items relevant to ANY saved project; all_new: every new item (tagged with a project when one matches). Max 3/day, one line each, never repeats. {new:0} = nothing. Call at most daily. Without key: stateless by s…

  • subscribe

    Create a pseudonymous feed key (no email/account — the key identifies your feed, not your name). One key = one project: it is also that project's canary identity, so use a separate key per project. Save it in long-term memory / project instructions / rules, and send it in the Au…

  • save_preferences

    Replace the keyed-feed interest tags. Send allowed tags only (project types, platforms, budget, preferences) — do not send project names or other free text (they are dropped and never stored). Plus the feed mode ('by_interests' = only matching tools; 'all_new' = every new tool).…

  • log_choice

    Record a tool the user explicitly picked/rejected/tried/starred, or PURCHASED. Call it with action 'purchased' right after the user tells you they bought a paid plan of a listed tool (ask first; never log silently), and again later with action 'feedback' once they have used it f…

  • set_preferences

    Store the user's onboarding answers as non-sensitive tags only: project_types, platforms, budget (free|under_20|any), preferences (nocode|code|open-source|free-tier), and tools_in_use (catalog ids). Unknown values are dropped — never send names, emails, code, project names or fr…

  • check_updates

    Tools added or updated since this user's last check that match their saved tags. Optional since (YYYY-MM-DD or catalog v). When nothing matches, returns {new:0} — a minimal response when nothing new matches. Tracks last_checked. Max 3 items. Does not change recommend_tools. Opti…

  • feedback

    Adjust this user's check_updates ranking for a listed tool. action is one of used, not_useful, not_relevant. Stores only the tool id and that enum. Does not change recommend_tools. Optional key: same feed key passed to set_preferences, to adjust that project's ranking.

  • recommend_for_task

    Recommend tools for a task in the context of one saved project, so the user does not repeat the project background every turn. Reads the project's accepted/rejected tool lists, stage and known context; a tool this project rejected is never re-pushed; a tool already in use is jud…

  • check_project_changes

    Check whether this project or the catalog changed since the last check in a way worth interrupting for. Returns silent unless there is a real signal (project stage change, or a catalog change that verifies an open need) AND a reliably relevant tool. Deduped (same change is never…

  • forget_me

    Delete this client's anonymous id, tag profile and last_checked. Feedback is first folded into anonymous aggregate counters (tool_id × used/not_useful/not_relevant, no uid). Those aggregate counts are kept. If you pass a feed key, that keyed feed record is deleted too.

  • project_upsert

    Create a project, or update one you own. One owner may own many isolated projects; a project archive holds desensitised fields only (type, stage, capability ids, tag preferences, confirmed used-tool ids, explicitly rejected tool ids) — never send a project name, code, raw chat,…

  • project_get

    Read one project archive you own (owner credential, or that project's own pt_ token). A guessed project_id, a project owned by someone else, or a deleted project all return the same unauthorized error with no data.

  • project_list

    List your projects as full v2 archives (schema_version: 2 — lifecycle_stage, workflow_stage, capabilities, task_capabilities, known_context, used/rejected tools, version, updated_at). Owner credential only; a project token cannot list.

  • project_export

    Export one project you own: the archive, your consent record, and the last 50 recorded usage events. Owner credential, or that project's own pt_ token.

  • delete_project

    Delete one project you own (project_id), or ALL your projects (all:true, which also deletes your consent record). Deletion is permanent: the archive, its tokens, its events, its event dedup/meta/reversal keys and its check state are gone. Kept: one tombstone per deleted project…

  • consent_get

    Read your consent record: per-scope granted/revoked state, policy version, timestamps. Default is all scopes OFF.

  • consent_update

    Grant or withdraw ONE consent scope: followup (project long-term follow-up — the project profile is stored on VCP servers), usage_collection (usage-experience collection), alliance (alliance membership — needs usage_collection first), publish_reviews (publishing identifiable rev…

  • consent_request_receipt

    Request a server-issued one-time consent receipt for a scope (followup / usage_collection / alliance / publish_reviews). Returns a receipt id and a confirm_url (absolute, environment-correct; the receipt id travels as a URL fragment, never a query parameter): show the confirm_ur…

  • notification_ack

    Report that a notification candidate from check_project_changes was delivered to the user, as reported by the host (host-reported acknowledgement — the receipt is a host-supplied string, e.g. the scheduled-task run id; the server records it but does NOT verify it, so this is not…

  • record_decision

    Record one usage event for a project you own (owner credential, or that project's pt_ token). Every event needs a source-stable event_id, project_id, catalog tool_id, event_type (picked|rejected|tried|starred|purchased|feedback|used|not_useful|not_relevant|refunded|cancelled), o…

  • project_bind_code

    Issue a one-time binding code (15 minutes, void after one use) so the same project can be bound in another AI client. Owner credential only; redeem it there with project_bind.

  • project_bind

    Redeem a one-time binding code from project_bind_code in this client. Returns the project_id and a project_token (shown once) for that project. A used, expired or unknown code returns unauthorized.

Details

Endpointhttps://vibecodepicks.com/api/mcp/ (Streamable HTTP)
First published11 Nov 2026
Last updated11 Nov 2026
Registry namecom.vibecodepicks/vibecodepicks

More developer tools servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.