Add MCP to Your Agent in One Click

Let's be honest: setting up MCP (Model Context Protocol) servers is usually a "copy-paste and hope" experience.

You find a cool tool, like the Kendo Telerik MCP (which I use daily for UI scaffolding), and then the dance begins:

1. Open editor settings.
2. Find the JSON config file (and hope you don't break strict JSON syntax).
3. Paste the snippet.
4. Check the commas.
5. Restart everything.

It’s manual. It’s high-friction. And for someone trying your tool for the first time, it’s often where they give up.

The "A-ha!" Moment

While building my first MCP server, I asked myself: "Why is this so hard for users?"

I realized that both Cursor and VS Code actually support deep links. They have a secret way of saying: "Hey, if you click this link, I'll install the server for you."

Think of this as a "mailto:" link, but for installing developer tools.

But there was a catch. The link formats are... let's just say "developer-unfriendly". To create one manually, you have to:

• Base64 encode JSON for Cursor.
• URL encode specific parameters for VS Code.
• Manage different schemas for different editors.

I spent more time encoding JSON strings than actually coding features. That’s when the idea for www.mcpclick.app was born.

Making Installation Invisible

I wanted a way to share the Kendo Telerik MCP with my friends and team without explaining the technical details. I wanted them to just click a button.

So I built www.mcpclick.app to handle the "boring stuff."

How it works (The 10-second version)

1. You go to www.mcpclick.app/generate.
2. You paste your raw JSON config.
3. You get professional buttons for Cursor, VS Code, and VS Code Insiders.

No more btoa() in the console. No more broken URL parameters. Just professional, standard badges ready for your GitHub README or blog.

The Result: One-Click Joy

Now, when I want to share the Kendo Telerik setup, I don't send a block of JSON. I send this:

Why this matters

What problem does this solve for us as developers?

If you are building an MCP server or leading a team, installation is your first point of Developer Experience (DX).

By using installation links, you:

• Remove friction: One click vs. Five fragile steps.
• Avoid typos: The config is baked into the link, so users can't mess it up.
• Look professional: Official-looking badges build trust.

Conclusion

I built www.mcpclick.app as a gift to the community. It’s free, it’s fast, and it hosts over 500+ curated servers if you're looking for inspiration.

Here is my challenge to you:

Go to your favorite MCP project's README (or your own!). Take that ugly block of JSON configuration and replace it with a one-click install badge. Then watch how much easier it is for others to try your work.

Go make your MCPs one-click ready! 🚀