Solon MCP Server

If you already use Solon, the solon mcp server is the piece that lets your assistant work with it directly. solon ai(&mcp) embedded examples。支持 MCP_2025_06_18（mcp streamable）。示例项目包括各种框架嵌入：（Solon、SpringBoot、jFinal、Vert.X、Quarkus、Micronaut）.

What the server does

solon ai(&mcp) embedded examples。支持 MCP_2025_06_18（mcp streamable）。示例项目包括各种框架嵌入：（Solon、SpringBoot、jFinal、Vert.X、Quarkus、Micronaut）

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• solon-ai-in-jfinal — The solon-ai-in-jfinal tool exposed by this server
• solon-ai-in-jfinal-newstyle — The solon-ai-in-jfinal-newstyle tool exposed by this server
• solon-ai-in-quarkus — The solon-ai-in-quarkus tool exposed by this server
• solon-ai-in-solon — The solon-ai-in-solon tool exposed by this server
• solon-ai-in-springboot2 — The solon-ai-in-springboot2 tool exposed by this server
• solon-ai-in-springboot3 — The solon-ai-in-springboot3 tool exposed by this server
• solon-ai-in-springboot4 — The solon-ai-in-springboot4 tool exposed by this server
• solon-ai-in-springmvc — The solon-ai-in-springmvc tool exposed by this server
• solon-ai-in-vertx — The solon-ai-in-vertx tool exposed by this server
• solon-ai-in-webflux2-llm — 只有 llm 示例（没有 mcp）
• solon-ai-in-webflux3-llm — 只有 llm 示例（没有 mcp）
• solon-ai-in-webflux4-llm — 只有 llm 示例（没有 mcp）

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Solon's toolset — solon-ai-in-jfinal, solon-ai-in-jfinal-newstyle, solon-ai-in-quarkus and 9 more — is a fair guide to whether it matches your workflow. It is maintained by opensolon; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Solon.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.