LinkMCP

Landing Page
My MCPs
MCP Builder
MCP Marketplace
MCP Templates and Methods

Inspiration

Late-night vibecoding sessions kept breaking because we were juggling 5+ MCP servers at once. The AI would hallucinate parameters, pick the wrong tool, or just give up. We realized: nobody had built the “one link to rule them all” that lets any AI reliably use Supabase + GitHub + Stripe + whatever else without falling apart. So we built LinkMCP.

What it does

LinkMCP lets you drag-and-drop methods from different MCPs (Supabase, GitHub, Stripe, etc.) and fuse them into one clean, rock-solid “super action”. You export a single MCP endpoint, paste it into Cursor, Lovable, Claude Desktop, or any agent — and suddenly your AI can do complex, multi-tool workflows without hallucinating or juggling auth.

How we built it

Next.js 15 + App Router + Tailwind
Supabase for auth, storage, and realtime
Drag-and-drop canvas powered by React Flow
Custom MCP proxy server that merges multiple remote MCP schemas into one unified endpoint (WIP)
Hybrid fallback: real MCPs where possible (Supabase, GitHub), smart API wrappers for everything else (Stripe, etc.) so it always works (WIP)

Challenges we ran into

Most third-party MCPs are either private, half-baked, or locked behind Stripe Connect apps (looking at you, Stripe & ElevenLabs).
Authenticating and proxying real MCP traffic without breaking spec is hard, we spent half the hackathon just getting OAuth + PAT forwarding bulletproof.

Accomplishments that we're proud of

Built a beautiful, fully functional drag-and-drop MCP fusion builder from scratch in <48 hours (Next.js 15 + React Flow + Tailwind)
Implemented real OAuth flows for Supabase and GitHub — you can click “Connect” and actually get real tokens
Designed and shipped a clean endpoint generation flow + personal MCP URLs
Proved the core vision works: we can take two real MCPs (Supabase + GitHub), let users chain methods visually, and export a schema that any MCP-compatible editor understands

What we learned

Pure MCP idealism dies fast, the ecosystem is still too immature. Hybrid (real MCP + instant wrappers) is the only way to ship something people can use today.
Users don’t care about protocol purity; they care about “does my AI actually do the thing without exploding?”
Drag-and-drop + live preview is pure magic for both vibe-coders and non-technical founders.

What's next for LinkMCP

Full marketplace of community-shared super actions
Full migration from MCP x API marketplace → Entirely MCPs
Templates gallery: “e-commerce ops agent”, “personal CRM brain”, “bug tracker sync”, etc.
Agency tier: let teams lock down which tools employees can use (security + governance)
Partnerships with Cursor, Lovable, and Superbase to ship as the default “combine your tools” button

LinkMCP: One link. Zero hallucinations. We’re just getting started.