Deployment
Everything about running a MCP server and letting a client reach it.
| Page | Content |
|---|---|
|
requirements, dependencies, a complete server, GraalVM native image. |
|
|
every option, generated from the code, plus the inherited Fusion ones. |
|
|
the streamable HTTP protocol: routes, headers, sessions, SSE, negotiation. |
|
|
Claude, IDE agents, the MCP inspector, |
|
|
validate against the official MCP conformance suite, for |
The short version
mvn package -pl demo exec:exec # a server on http://localhost:8080/mcp
claude mcp add --transport http demo http://localhost:8080/mcp
Add fusion-mcp-server-impl to a Fusion application and the three routes come with it:
| Route | Purpose |
|---|---|
|
|
requests, notifications and responses. |
|
|
the server to client event stream. |
|
|
session termination. |
Checklist before exposing it
-
set
fusion.mcp.instructions- it is what tells the model when to use this server, -
set
fusion.mcp.name/title/versionso the client shows something meaningful, -
review the tool descriptions with the MCP inspector: they are the interface with the model,
-
decide the session policy,
fusion.mcp.requireSession, and the session timeout, -
behind a load balancer, enable sticky routing on the
Mcp-Session-Idheader, -
put authentication in front of it if the data is not public - MCP has no opinion there, use the regular Fusion means.