Model Context Protocol (MCP) now generally available

MCP Support is live now in GA.

Model Context Protocol (MCP) is now generally available in Superinterface. MCP allows AI assistants to connect with external servers that define both functions and their implementations, simplifying advanced integrations.

How to Get Started

Set up MCP server.

Set up MCP in Superinterface by navigating to Assistant → MCP servers. Add your server URL, and your assistant will be ready to use the tools provided by the server.

For example, you can try the Unichat MCP Server, which connects assistants to OpenAI, MistralAI, Anthropic, xAI, and Google AI using the MCP protocol. Here’s how:

Start the Unichat MCP Server

UNICHAT_MODEL=gpt-4o-mini UNICHAT_API_KEY=your-api-key npx -y unichat-ts-mcp-server --sse

This starts the server on port 3001, with --sse enabling SSE transport.

Expose the Server Locally Use ngrok to make the server accessible online:

ngrok http 3001

Copy the public URL provided by ngrok, e.g., https://c70e-78-58-52-214.ngrok-free.app.

Configure the MCP Server in Superinterface Go to Assistant Settings → MCP Servers and add the server URL, appending /sse:

https://c70e-78-58-52-214.ngrok-free.app/sse

Once configured, your assistant can use tools from the Unichat server. For instance, you can ask it to send a request to OpenAI or other supported providers.

Using Supergateway for Stdio-based MCP Servers

Supergateway

Many community MCP servers only implement stdio transport, which is typically inaccessible to remote assistants. To fix this, we’ve released Supergateway, an open-source utility that converts stdio MCP servers to SSE. This lets you connect them to Superinterface (or any remote SSE-based client).

How it works:

Run your stdio MCP server via supergateway:

npx -y supergateway --port 8000 \ --stdio "npx -y @modelcontextprotocol/server-filesystem /Users/MyName/Desktop"

Expose port 8000 with ngrok (so Superinterface can reach it):

ngrok http 8000

Copy the ngrok HTTPS URL (e.g., https://randomsub.ngrok.io) and append /sse, then add that in Assistant → MCP Servers.

Now your stdio-based MCP server appears as an SSE server to Superinterface, enabling remote usage and debugging with no extra code changes in the server itself.

Background: “We built Supergateway because most MCP servers only support stdio, and we wanted to run them in remote assistants. SSE is part of the MCP spec, but not always implemented. Supergateway bridges that gap so your local or community MCP servers can be used in Superinterface or any SSE-based MCP client.”

Current Capabilities

Superinterface currently supports MCP tools via SSE transport. MCP prompts are not yet supported but are in development. We’re also experimenting with Stdio support over the tunnel, pending further progress from Anthropic.

For more details, book a demo or explore the Unichat MCP Server documentation.