Add curated catalog entries for popular MCP servers

[btsouth]

The catalog is a hand-verified list of popular MCP servers that become one-click "Add" buttons in src-tauri/src/catalog.rs. Growing it is one of the easiest, highest-value ways to contribute.

If there's a real, working MCP server you use that isn't in the catalog, add it. The guide is in CONTRIBUTING.md: one http() or cmd() line plus a category, and the tests check it automatically.

Comment with the specific server you're adding to avoid overlap. Before starting, check the current curated() entries in src-tauri/src/catalog.rs; that file is the source of truth for what has already shipped. Older catalog lists in the comments are historical and may be incomplete.

Acceptance

• New entry in catalog.rs with a category (and a credential hint if it needs a key).
• cargo test --manifest-path src-tauri/Cargo.toml catalog passes; the server connects and exposes tools when added.

[BharadwajKanneveti]

Hi @tsouth89 can I work on this issue?

[btsouth]

Yes, and your BoltAI PR is in and clean, so this is a perfect next one.

One rule matters most here, the one the issue flags: only add a server you've actually run and seen connect and list tools. An entry that looks right but doesn't work is worse than none, it breaks someone's first launch. So pick from things you've genuinely used.

What's already in, so you don't dupe (24): Stripe, GitHub, Vercel, Sentry, Cloudflare Docs, AWS, Supabase, Neon, PostgreSQL, Notion, Linear, Atlassian, Asana, Slack, Resend, Context7, DeepWiki, Hugging Face, Brave Search, Figma, Filesystem, Fetch, Git, Playwright.

Still-open gaps if you've used any: MongoDB or Redis, GitLab, Grafana or Datadog, Firecrawl or Exa, Shopify or PayPal, HubSpot, Google Drive or Maps. Pick whatever you've actually run.

Format is two helper closures at the top of curated():

Hosted: http("Name", "short description", "https://endpoint", "https://homepage")

Local stdio: cmd("Name", "short description", "npx", &["-y", "the-package"], &["REQUIRED_ENV"], "https://homepage")

Drop your line into the matching category in the vec![]. Env vars are names only, never values, and keep the description short like the existing ones. You've got the full list above, so dedupe against it, make sure it actually connects, and open the PR, no need to clear the pick with me first.

[btsouth]

@BharadwajKanneveti checking in on this one. I said yes back in June but the assignee field never got set, so it's been sitting in an odd in-between state where it reads as unclaimed to anyone browsing.

You've since picked up #372, #374, #379 and #381, so no pressure at all. Do you still want this one? If yes I'll set the assignee properly. If you'd rather let it go, say so and I'll open it back up, since it's a good entry point for someone new and I don't want it parked if it isn't moving.

The one rule from earlier still stands either way: only add a server you've actually run and watched connect and list tools. An entry that looks right but doesn't work breaks someone's first launch, which is worse than not having it.

[BharadwajKanneveti]

@tsouth89 i will work on those 4 issues i picked up. You can assign it to someone else.

[btsouth]

Understood, thanks for saying so plainly rather than leaving it parked. Reopening this one to anyone who wants it. Your four are the priority and there's no rush on them.

[Vermitrude]

@tsouth89 i like a challenge, want me on?

[btsouth]

Thanks for volunteering. #3 is the umbrella catalog, so I don't want to assign the whole issue. After #579 is finished, pick one specific server from the checklist that you have personally run and can validate end-to-end, then comment with the server name. We'll scope and assign that one.