Search is the obvious half; the resources are the half people miss. Rather than retrieving snippets, you can pull a Micronaut module's documentation into the conversation's context and work against it directly — which is the difference between an assistant guessing at an annotation and reading the page that defines it. It is a remote endpoint maintained alongside micronaut.fun, so there is nothing to keep updated locally.
The MCP server exposed by micronaut.fun, the Micronaut project's own search engine over the Micronaut documentation and guides. The application is built with Micronaut and OpenSearch; the MCP endpoint is a face on the same index.
- Tools that search the Micronaut documentation and the Micronaut guides
- Micronaut documentation resources you can add to a conversation's context, chosen by module
- Prompts aimed at day-to-day Micronaut tasks
Nothing to install and no account. The endpoint is https://micronaut.fun/mcp over HTTP — for Claude Code, `claude mcp add --transport http micronautfun https://micronaut.fun/mcp`, which writes an `mcpServers` entry with type http. Setup pages are included for Claude Desktop, Cline, VS Code and IntelliJ IDEA GitHub Copilot.
One command — claude mcp add --transport http micronautfun https://micronaut.fun/mcp
