MCP server

RLPlugins MCP guide

The RLPlugins MCP server is the assistant-facing entry point for the live runtime docs. It keeps searches, page lookups, and plugin planning pointed at the Kraken docs first.

Use it when you need the exact class or method name, want a quick review of a plugin idea, or need a clean scaffold before writing code.

Kraken Javadocs Architecture MCP endpoint

What it exposes

The MCP server mirrors the current runtime contract instead of the legacy EthansAPI tree, so the assistant can reason over the same docs the platform serves to developers.

search_javadocs and get_javadocs_page for Kraken API lookup
plugin_review and plugin_blueprint for planning and auditing
plugin_scaffold for starter code when you need a clean entry point

When to use it

Use the MCP server any time you need the latest runtime surface, a plugin API answer, or a quick review of how a feature should be structured.

Checking exact class names and method signatures
Tracing plugin flow before making a backend or launcher change
Reviewing whether a new idea fits the current runtime model

How the docs fit together

Kraken Javadocs explain the runtime APIs, the architecture page explains the platform flow, and the MCP server makes both searchable from the workspace.

Kraken docs first
Architecture second
MCP as the assisted lookup layer

Quick links

Use these when you want to move from assistant guidance into the live docs or the platform architecture.

Docs

Kraken Javadocs

Open the canonical kraken javadocs reference.

Kraken-first Source of truth

Docs

Architecture

Open the canonical architecture reference.

Kraken-first Source of truth

Docs

MCP endpoint

Open the canonical mcp endpoint reference.

Kraken-first Source of truth