RLPlugins support
Help with plugins, downloads or your order. Our team replies from Discord.
Developer tools / MCP
Connect an MCP-compatible AI client to the read-only RLPlugins documentation service for RuneLite and Kraken research, design review, and starter source.
Streamable HTTP endpoint
https://rlplugins.net/api/mcp/Find classes, methods, packages, and terms in the indexed RuneLite and Kraken documentation before code is written.
Check lifecycle, event, client-thread, and state decisions against the documented API surface.
Turn a bounded plugin idea into explicit files, events, state ownership, and verification steps.
Generate a focused plugin, config, and UI starting point after the API and implementation map are known.
Connection record
Use https://rlplugins.net/api/mcp/ as a Streamable HTTP MCP server.
Keep the connection read-only; it does not need account credentials or gameplay access.
Ask for exact symbols and documented constraints before requesting implementation source.
Approve the bounded file and verification plan before scaffolding a full plugin.
Prompt registry
Search for the RuneLite events involved in widget updates and list the client-thread constraints.
Review this plugin design for lifecycle, state ownership, and API assumptions before writing code.
Build a file-by-file implementation map for a combat timing panel, then identify the Javadocs used.
Find the smallest Kraken API surface required for this feature and explain each call.
Boundary / read only
The MCP service is for documentation search and development assistance. Purchases, publishing, live client actions, and production changes remain in their normal authenticated workflows.