MCP Connect
MCP Connect is a transport bridge that connects stdio-based MCP clients to remote Streamable HTTP servers. If your client only speaks stdio — the transport used for local processes — MCP Connect acts as a proxy: it starts as a local stdio process, then forwards all MCP messages to a remote HTTP endpoint like Vinkius Cloud.
Bridging the Transport Gap
The MCP specification defines two transports: stdio (for local processes) and Streamable HTTP (for remote servers). Most cloud MCP servers, including Vinkius Cloud, use Streamable HTTP. But some clients only support stdio — they expect to spawn a local process and communicate over standard input/output.
MCP Connect bridges this gap. You configure your client to start MCP Connect as a local stdio process, and MCP Connect relays every message to the remote HTTP server. From the client's perspective, it looks like a local MCP server. From the server's perspective, it looks like a normal HTTP client.
When you need MCP Connect:
- Client only supports stdio — some older or minimal clients lack HTTP transport
- Firewall restrictions — proxy through a controlled local process
- Protocol debugging — intercept and log all MCP messages
- Multi-hop setup — chain local preprocessing before reaching the cloud server
Setup Guide
1. Create a Token
In Vinkius Cloud, go to your server → Connection Tokens → Create. Copy the URL.
2. Install MCP Connect
npm install -g mcp-connect3. Configure Your Client
In your MCP client's config, register MCP Connect as a stdio server. Example for clients that use command + args:
{
"mcpServers": {
"vinkius": {
"command": "mcp-connect",
"args": ["https://edge.vinkius.com/{TOKEN}/mcp"]
}
}
}The client starts MCP Connect as a local process, and MCP Connect connects to Vinkius Cloud over HTTP transparently.
FAQ
When do I need MCP Connect? Only when your MCP client does not support Streamable HTTP transport. Most modern clients support HTTP natively and can connect to Vinkius Cloud directly.
Does MCP Connect add latency? Minimal. MCP Connect is a thin proxy — it adds a few milliseconds per message for the stdio-to-HTTP translation.
Can I use MCP Connect for debugging? Yes. You can configure verbose logging to see every MCP message passing through the proxy, which is useful for protocol debugging.
Is MCP Connect free? Open-source. No licensing or account required.