Connect a client
Connect your MCP server to any client
Every MCPCloud deployment exposes a standard streamable HTTP endpoint. Pick your client below for copy-paste setup that mirrors the in-app Connect panel — the same snippets, ready for the web.
Claude Code
Add your MCP server to Claude Code from the terminal.
Claude Desktop
Connect Claude Desktop to a remote MCP server over a stdio bridge.
Cursor
Point Cursor at a remote MCP server.
EditorVS Code
Add a remote MCP server to VS Code.
Windsurf
Connect Windsurf to a remote MCP server.
Antigravity
Add a remote MCP server to Antigravity.
Codex
Add a remote MCP server to the Codex CLI and IDE extension.
ChatGPT
Add your MCP server to ChatGPT as a custom connector.
Gemini CLI
Add a remote MCP server to the Gemini CLI.
Using a skill
Skills don’t connect — they run inside your agent
A skill is a set of instructions, not an endpoint, so there is no URL to paste. You take its SKILL.md into your agent, and connect the MCP servers it depends on — using the client guides above.
- Install the skill from the marketplace. Any MCP servers it depends on are installed alongside it.
- Download the package — Use this skill on the listing, from Settings → Installations, or
mcp skills pull <artifactId>in the CLI. You getSKILL.mdplus anmcpcloud.jsonlisting the servers it needs and whether you already have each one. - Copy
SKILL.mdinto the skills directory your agent reads, and connect each server inmcpcloud.jsonusing the guide for your client above.
Already connected MCPCloud to your agent? Skip the download — ask it to call get_skill_package and it will fetch the instructions and the server list itself.
Don’t have a server yet?
Paste an OpenAPI spec, let Claude enrich every tool description, and deploy a typed MCP server in minutes. Then come back here to connect it.