Serve multiple MCP clients from one FrontMCP server
Maintained guide. Example version: FrontMCP 1.10.10. Technical checks recorded: 2026-10-22. How checks work.
A client can start a local MCP subprocess or connect to a server you operate. A shared HTTP server is useful when several clients need the same services. It also gives you access control, availability and state-management decisions to make. Hosted multi-client servers are supported by MCP itself; FrontMCP adds app composition and framework services.
Several clients can call one FrontMCP server. Apps group tools; endpoints decide what is exposed together. A separate route does not by itself decide which tenant's records a caller may read.
Apps and client-visible names
Unique names stay unchanged. When two apps use the same tool name, discovery lists <app id>:<name>. This example checks the actual list and calls both entries.
import { App, FrontMcp, Tool, ToolContext } from "@frontmcp/sdk";
@Tool({ name: "status", description: "Billing service status", inputSchema: {} })
class BillingStatus extends ToolContext {
async execute() { return { service: "billing" }; }
}
@Tool({ name: "status", description: "Operations service status", inputSchema: {} })
class OpsStatus extends ToolContext {
async execute() { return { service: "ops" }; }
}
@App({ id: "billing", name: "Billing", tools: [BillingStatus] })
class BillingApp {}
@App({ id: "ops", name: "Operations", tools: [OpsStatus] })
class OpsApp {}
@FrontMcp({
info: { name: "platform", version: "1.0.0" },
apps: [BillingApp, OpsApp],
})
export default class Server {}Starting FrontMCP in your browser…
FrontMCP starts when this example comes into view.
This fixture is public and read-only. It does not demonstrate tenant authorization. Plain status can still reach the first app; use distinct names when maintaining an existing client contract. The apps reference covers collisions and resource URIs.
The runnable fixture uses the default entry path /. For a local HTTP server, set http.entryPath: "/mcp" to use the routes in the table below.
Choose endpoints and auth together
| Configuration | Routes for entry path /mcp | Access responsibility |
|---|---|---|
| Default | /mcp combines apps | Server auth applies to that endpoint |
| An app with standalone: true | /mcp plus /mcp/app-id | Configure app endpoint auth explicitly |
| splitByApp: true | /mcp/app-id per app; /mcp itself is 404 | Each endpoint uses its app's auth or the server default |
Without configured auth, the default is public. Use auth.mode, not the old auth.type object. Choose transparent auth when your provider issues acceptable JWTs, or remote auth when FrontMCP brokers sign-in and issues its own tokens. Remote configuration needs a provider URL, registered client and issuer settings; changing one property in an old snippet is insufficient.
On a shared endpoint, app grants require the supported local/remote incremental-auth setup. App-level auth on its own endpoint and backing API record authorization remain separate checks. Follow Auth for one app, including its refusal cases.
State depends on the protocol and the application
MCP 2026-07-28 has no protocol sessions. Earlier supported revisions use a handshake and may need shared session storage across instances. A stateless protocol does not remove database, OAuth or job-state requirements. See protocol versions.
Add an existing API
Use OpenapiAdapter from @frontmcp/adapters, registered in an app's adapters. The OpenAPI lesson supplies a complete spec, credential configuration and runnable calls.
Migration playbook
First record names, schemas, resource URIs, errors, authentication and endpoint behavior that existing clients rely on. Move one area at a time, compare the contract, and keep a rollback route. The SDK migration guide gives a concrete sequence. Test both permitted and refused requests before switching clients.