RuneScape Wiki

RuneScape 3 MCP Server

Ask what it's worth, whether the flip clears tax, and what to train next.

Connect Claude, ChatGPT, Cursor, and other assistants to RuneScape 3 Grand Exchange guide prices, 7–90 day history, flip math after the 2% tax, public RS3 hiscores, and wiki pages. RS3 only. Unofficial, and not affiliated with Jagex or the RuneScape Wiki.

An independent Birdwell Labs project. No Jagex or Weird Gloop approval is claimed. Support and rights concerns · Permissions and source review.

Default prices are Jagex guide prices and Weirdgloop history. They lag the in-game market. Ask for reported instant-buy/sell prices to include the separate RS3 trade feed at prices.runescape.wiki.

Questions to ask

• What's the guide price of a Noxious scythe, and how did it move over 30 days?
• Compare a Noxious scythe, a Dragon rider lance, and an Abyssal whip.
• Estimate the profit from flipping 100 Dragon rider lances after tax.
• Look up my stats and tell me the weakest skill to train. Normal mode.
• Find the RuneScape Wiki source link for the Abyssal whip special attack.

The server answers questions about items you name. It does not rank the whole Grand Exchange.

Price questions use lookup_item, get_item_details current-data views, get_price_series history views, and estimate_flip. Stats questions use get_player_stats on the selected normal, ironman or hardcore board; the assistant turns those levels into a training suggestion. Wiki questions use search_wiki, then get_wiki_page_content.

Wiki pages return source links by default. Article text is available only for reviewed revisions; the server does not supply an article summary when text is withheld.

Access and data handling

This server reads public APIs and performs calculations. It does not connect to the game client, control characters, place trades or ask for your Jagex password, session cookies or bank PIN. A player-name lookup sends the supplied name to Jagex's public hiscores endpoint.

Your assistant receives tool results and may use them to generate an answer. Its own privacy, retention and model-training settings apply separately; this project cannot promise how an AI provider handles those results. Check linked sources before acting on generated advice.

See the privacy policy before using the hosted service. Optional diagnostics may receive request context, and enabling DEBUG can print tool arguments and returned data. Do not submit secrets or information you do not want processed by the service and your AI provider.

Connect

Hosted endpoint: https://runescape-wiki-mcp.fly.dev/mcp

Privacy policy describes the tool-request data, diagnostics and service providers involved.

No server account, API key, game login or local installation is needed. Use Streamable HTTP with no authentication.

Claude setup

1. Open Customize → Connectors, then + Add → Add custom connector.
2. Name it RuneScape Wiki MCP and enter the hosted endpoint above.
3. Choose No sign in when asked about authentication, then finish adding the connector.
4. In a chat, enable it through + → Connectors and ask: “What is the RS3 guide price of an Abyssal whip?”

Team and Enterprise users may need an owner to add the connector first. See Claude's custom connector guide for your account's setup flow.

ChatGPT setup

1. On ChatGPT web, open Plugins, select +, then Add custom MCP server.
2. Name it RuneScape Wiki MCP, enter the hosted endpoint above, and select No authentication.
3. Review the connection warning, then choose Create as a plugin.
4. Install the resulting personal plugin. In a chat, type @, select it, and ask: “Compare Dragon bones and Frost dragon bones.”

Custom MCP access depends on your workspace permissions and security settings. See OpenAI's custom MCP guide if the option is unavailable.

Other MCP clients

For clients that accept remote MCP configuration, use:

{

"mcpServers": { "runescape-wiki": { "url": "https://runescape-wiki-mcp.fly.dev/mcp" } } }

For clients that require local stdio, install through npm:

{

"mcpServers": { "runescape-wiki": { "command": "npx", "args": ["-y", "runescape-wiki-mcp"] } } }

Local stdio, after bun install and bun run build:

{

"mcpServers": { "runescape-wiki": { "command": "node", "args": ["/path/to/runescape-wiki-mcp/dist/index.js"] } } }

Also listed on:

• Glama hosted connector
• MCPRush
• Server card: https://runescape-wiki-mcp.fly.dev/mcp/server-card
• AI Catalog: https://runescape-wiki-mcp.fly.dev/.well-known/ai-catalog.json
• Official MCP Registry: io.github.birdwell/runescape-wiki-mcp
• npm: runescape-wiki-mcp

Speaks MCP 2026-07-28 (stateless) via stdio and Streamable HTTP, with legacy 2025-era clients still supported.

Tools

• lookup_item — Resolve an item name to a Grand Exchange ID and the latest guide or Weirdgloop price. Start here when you only know the name.
• get_item_details — Single/batch Jagex catalogue records and guide prices, with optional recorded-trade and numeric-fact enrichment.
• get_price_series — Explicit observations/statistics views over historical prices; ID-based preferred discovery.
• estimate_flip — Tax-adjusted flip profit, with optional remaining-quota and assumed-duration scenarios. Default prices lag the live market.
• browse_items — Browse one Grand Exchange category by starting letter. This is not a name search.
• get_ge_info — Catalogue metadata: default status, view: "categories" for IDs/names, or view: "category_counts" with category for letter counts.
• get_player_stats — RS3 hiscores for a username. gameMode selects normal, ironman or hardcore. A 404 means the player was not found on that board; no other board is substituted.
• search_wiki — Search RuneScape Wiki titles and source links when the page title is unknown.
• get_wiki_page_content — Source reference following redirects; text only for a reviewed revision and matching content hash.
• get_wiki_entity_facts — Structured monster combat statistics and quest metadata.
• list_wiki_category_members — Direct Wiki category members with category-bound continuation.
• get_wiki_drop_table — Indexed drop references, quantities, rolls and listed rarities; notes are excluded.
• get_player_quests — Complete public RuneMetrics journal with quest statuses and Jagex eligibility; no Jev key needed.
• recommend_next_activity — Opt-in paid goal-based planning using account context and Wiki evidence; requires the server configuration below.

Try the Jev recommendation tool locally

The MCP server owns the loop. The calling assistant supplies a goal and whatever account context it knows, then explains the structured result to the player. No separate agent framework or text-generation model is needed inside the server.

Set these in a local, ignored .env.local file. Do not commit the API key:

RUNESCAPE_RECOMMENDATIONS_ENABLED=true

TYPESAFE_API_KEY=your-typesafe-key

Optional; defaults to jev-latest

TYPESAFE_MODEL=jev-latest

bun run build

node --env-file=.env.local dist/index.js

Or use dist/http.js for a local HTTP MCP endpoint.

The entry point does not automatically load dotenv files. For an MCP client's stdio configuration, pass the same settings through its server env block or include --env-file=/absolute/path/to/.env.local in the Node arguments.

Example recommend_next_activity arguments:

{

"goal": "Train Prayer toward bossing", "context": { "username": "YourName", "gameMode": "normal", "skills": { "Prayer": 50 }, "budgetGp": 2000000, "sessionMinutes": 45, "playStyle": "active", "members": true, "completedQuests": ["The Restless Ghost"], "gear": [], "notes": "Prefer methods that help unlock future combat upgrades." } }

Only goal is required. Public hiscores fill missing skill levels when a username is supplied; caller-supplied levels take precedence and their provenance is returned. Quest completion comes from RuneMetrics for quest goals; membership, gear and bank contents remain unknown unless provided. For other goals, a caller-supplied completed list records known completions only; absence does not mean a quest is unfinished.

For a quest question, supply the username and natural-language goal:

{

"goal": "What is the best mining quest to do?", "context": { "username": "YourName" } }

The server reads the fresh public RuneMetrics journal and the wiki pages for its quests, resolves title aliases and quest disambiguation, and reads the wiki's shared prerequisite table. Completed quests are excluded. Every unfinished quest is sent to Jev with completion rewards, separate conditional post-quest rewards, skill and quest prerequisites, current status, eligibility, and known blockers. Independent comparisons run in bounded batches, then a final comparison picks a quest to do now and useful blocked targets. The planner fetches the finalists' quick-guide checklists and returns their starting location, length, items, enemies, and opening walkthrough steps. Started quests retain their status; the exact stage must be read from the player's in-game journal.

Quest goals use at most 24 Jev requests, including routing, with two comparison requests in flight at once. Individual request bodies stay below 40,000 serialized characters. questCoverage reports journal totals, metadata coverage and the exact number of unfinished quests evaluated. Missing/private journals and missing wiki facts are reported explicitly. Skill/prerequisite checks and Jagex eligibility constrain the choices; current membership, inventory, combat readiness, boost alternatives and miscellaneous requirements may still need checking. A stale caller-supplied completion list does not override the fresh official journal. Public wiki quest metadata is cached for six hours; player journals are never cached.

For a skill training plan, use a goal such as "Train Mining to 70", or supply goalType: "skill_training", targetSkill: "Mining" and targetLevel: 70. The server reads wiki training tables and the fresh public quest completion set when a username is available, preserves separate rate assumptions such