MuiRouter

MCP Server Guide

What is an MCP server?

The Model Context Protocol (MCP) is an open standard that lets AI applications connect to external data and tools through one uniform interface. An MCP server is the component that exposes those tools over the protocol — this guide explains what it is, when you need one, and where MCP servers, routers and AI gateways overlap.

An MCP server in one sentence

An MCP server is a program that speaks the Model Context Protocol: it receives requests from MCP clients such as Claude Desktop, Claude Code, Cursor or Cline, and answers with tools, resources or prompts the AI assistant can call. It is the standard interface between your AI application and everything you want it to reach.

When do you need an MCP server?

You need an MCP server whenever you want your AI client to reach tools that are not built into it. Instead of writing a custom integration for each AI application, you expose one MCP server and every MCP-capable client connects the same way. A hosted MCP server is the right choice when you do not want to run or maintain infrastructure yourself.

MCP server vs. MCP router vs. AI gateway
MCP server

The protocol server that exposes tools to MCP clients. It defines how tools are listed and called, but not which LLM provider backs the calls.

MCP router

An MCP server that also routes model requests. Instead of hard-coding one provider, it dispatches each call to OpenAI, Claude, Gemini, Grok and more behind one key.

AI gateway / LLM gateway

A broader category: a single entry point that handles routing, billing, usage tracking and access control for AI APIs. An MCP router is one kind of AI gateway, exposed through the MCP protocol.

Where MuiRouter fits

MuiRouter runs a hosted MCP server over streamable-HTTP at api.muirouter.com/mcp. It is an MCP router: the same server that lists account tools also routes model calls to OpenAI, Claude, Gemini, Grok and MiMo behind your own sk-gw- key, billed per token from one wallet.

What MuiRouter's MCP server supports

Protocol: MCP 2026-07-28 over streamable-HTTP, with legacy negotiation for 2025-11-25 / 2025-06-18 clients.

Clients: Claude Desktop, Claude Code, Cursor and Cline, plus any MCP client that speaks streamable-HTTP.

Tools: balance, usage and recharge queries, model and pricing listing, image generation and top-up sessions.

Authentication: Bearer token with your own sk-gw- API key; every call is billed to your account.

Limitations to know

MuiRouter's MCP server only routes models MuiRouter supports — check the pricing page for the current catalog.

image_generation and create_topup_session spend money or move funds. Configure your AI client to require confirmation for these tools.

This guide is updated when the protocol or feature set changes; the last reviewed date is below.

Last updated: 2026-08-08

MCP server FAQ

What is the difference between an MCP server and an MCP router?
Every MCP router is an MCP server, but not every MCP server routes. A plain MCP server exposes tools over the protocol; an MCP router additionally sends model requests to multiple LLM providers behind one interface. MuiRouter's MCP server is an MCP router.
Do I need to host my own MCP server?
No. MuiRouter hosts it for you: connect Claude Desktop, Claude Code, Cursor or Cline to api.muirouter.com/mcp with your own API key and the tools work without you running any infrastructure.
Is an MCP server the same as an AI gateway?
They overlap but are not the same. An AI gateway is a category that covers routing, billing and access control for AI APIs. An MCP server is a protocol server that exposes tools to AI clients. MuiRouter is both: a hosted MCP server and an AI/LLM gateway behind one key.
How do I connect an MCP client to MuiRouter?
Add the streamable-HTTP endpoint with your sk-gw- key to your client. The setup guide walks through Claude Code, Cursor and Claude Desktop step by step.

Explore the cluster