Connects AI assistants to your Argo campaigns via the Model Context Protocol. Once configured, your AI assistant can read and write campaign lore, look up character details, and interact with Argo data directly from the chat interface.
Supported clients: Claude Code, Claude Desktop, OpenAI Codex, VS Code (1.103+), and any MCP-compatible host.
MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
1.0.3
API key
OAUTH_TOKEN, REFRESH_TOKEN, ARGO_API_BASE
ตรวจสอบล่าสุด
2026-11-08
ดาว
—
เครื่องมือ
—
อัปไทม์
—
One-click install
Clicking either button hands a vscode:mcp/install URL to your editor with this config:
VS Code stores the entry in your user-level mcp.json, then negotiates OAuth on first connect via Dynamic Client Registration against the Argo authorization server. No tokens are embedded in the URL — VS Code stores the resulting access and refresh tokens in your OS keychain.
Linux / Flatpak / Snap note: If clicking the button doesn't open VS Code, the vscode: URL handler isn't registered. This is common on:
Flatpak / Snap VS Code — the sandbox isolates the install from the host, so the host browser can't find the protocol handler.
Tarball / manual installs — no postinst hook runs update-desktop-database. Either run xdg-mime default code.desktop x-scheme-handler/vscode once, or use the manual fallback below.
The same install button is rendered on the Argo install page at https://app.argo.games/docs/mcp/install.
Prerequisites
Node.js 20 or later
An Argo account with at least one campaign
A Game Master must authorize the AI assistant via the OAuth2 consent flow (see Getting a token)
Quick start
There are three supported ways to use the Argo MCP server. Pick the one that matches your client.
ChatGPT (remote)
Use the hosted endpoint — do not install the npx package. Add this MCP server URL to ChatGPT:
https://mcp.argo.games/mcp
ChatGPT will walk you through OAuth on first connect via dynamic client registration.
Local MCP clients (Claude Code, Claude Desktop, Codex, etc.) — recommended
Sign in once on the machine that runs the MCP client:
npx -y argo-mcp auth login
The command prints the consent URL, opens nothing, and asks you to paste the access token (and optionally the refresh token) from the consent page. Tokens are saved locally:
npx -y argo-mcp auth status # show whether you are signed in
npx -y argo-mcp auth logout # forget locally stored tokens
Local stdio mode does not use OAuth Dynamic Client Registration. DCR is only used by the hosted HTTP server at https://mcp.argo.games.
Advanced — environment variables
For CI, Docker, or anyone who prefers explicit env config, you can skip auth login and pass tokens directly. OAUTH_TOKEN always wins over the local token store.
git clone https://github.com/Argo-RPG-Platform/MCP.git argo-mcp
cd argo-mcp
npm install
npm run build
Getting a token
The MCP server authenticates with Argo using an OAuth2 access token tied to a specific set of campaigns. Tokens are obtained through the Argo consent flow:
VS Code handles OAuth automatically via Dynamic Client Registration on first connect. There is no need to set OAUTH_TOKEN or REFRESH_TOKEN — VS Code stores tokens in the OS keychain.
For the hosted ChatGPT app surface, this repo exposes OAuth discovery, dynamic client registration, and domain verification endpoints on the MCP domain. The submission checklist and required env vars are in CHATGPT_APP_SUBMISSION.md.
npm run dev # hot-reload via tsx
# or
npm start # compiled dist/
Pre-built Agent Skills
Once the MCP is connected, you can install the argo-agent-skills plugin to get ready-made Game Master workflows that orchestrate the tools below — session prep, post-session recap, NPC generation, and a guided MCP setup walkthrough. The same skill source ships parallel packaging for Claude (Code + Claude.ai) and OpenAI-compatible clients (Codex, ChatGPT).
create_campaign (campaign.create) creates a new campaign
update_campaign (campaign.write) updates campaign name or description
list_co_gms (campaign.read) lists assistant GMs
add_co_gm (campaign.write) adds an assistant GM
remove_co_gm (campaign.write) removes an assistant GM
Mnemons
describe_mnemon_types lists supported mnemon types, relationship labels, and content-block rules
list_mnemons (campaign.read) lists mnemon entries for a campaign
get_mnemon (campaign.read) retrieves a mnemon entry in full
list_mnemon_relationships (campaign.read) lists linked entries and relationship edges
create_*_mnemons (campaign.write) creates typed mnemon entries for NPC, Location, Quest, Lore, Archive, Journal, SessionSummary, Player, and Custom entries
update_*_mnemons (campaign.write) updates typed/meta fields for those mnemon entry types; the quest tools also write a quest's objectives, reward chips, background and GM notes
set_quest_objective_state (campaign.write) ticks, fails or reopens one quest objective by its id
send_friend_request (friends.write) sends a friend request
accept_friend_request (friends.write) accepts a request
reject_friend_request (friends.write) rejects a request
cancel_friend_request (friends.write) cancels a sent request
To bring someone into a campaign or guild, use invite_guild_member or send_friend_request — the MCP surface does not send email to addresses outside your existing Argo context.
Forum
forum_list_categories (forum.read) lists forum categories
forum_list_topics (forum.read) lists topics in a category
forum_get_latest_topics (forum.read) lists recent forum activity
forum_read_topic (forum.read) reads a topic thread
forum_search (forum.read) searches forum content
forum_get_user_posts (forum.read) lists the current user's topics
forum_get_notifications (forum.read) lists the current user's notifications
forum_create_topic (forum.write) creates a new topic on community.argo.games
forum_reply (forum.write) replies to an existing topic on community.argo.games
Many campaign-scoped tools accept campaignId. You can find a campaign's ID from the Argo campaign URL or by asking the GM.
Token renewal
The access token expires after approximately one hour. If REFRESH_TOKEN is configured, the server automatically fetches a new access token on the first request that returns a 401 and retries transparently — no action required.
If no refresh token is set and the access token expires, the tool will return:
Re-run the consent flow at that URL to get fresh tokens.
Revoking access
To disconnect the AI assistant from a campaign, revoke the grant from the campaign's integrations page in the Argo WebApp. The access token and refresh token will both become invalid immediately.
Environment variables
Variable
Required
Description
OAUTH_TOKEN
If not signed in via auth login
OAuth2 access token from the consent flow
REFRESH_TOKEN
Recommended
OAuth2 refresh token; enables automatic renewal
ARGO_API_BASE
No
Override the API base URL (default: https://api.argo.games)
ARGO_MCP_TOKEN_PATH
No
Override the local token file path used by auth login
Data collected. OAuth access and refresh tokens issued by the Argo authorization server (oauth.argo.games); the campaign, mnemon, guild, forum, and friends payloads that pass through tool calls; standard HTTP metadata (IP, user agent) for rate limiting and abuse mitigation.
Usage. Tool calls are proxied to the Argo WebAPI (api.argo.games) on behalf of the authenticated user. Tokens are cached in-process for the lifetime of an MCP session so clients that omit Authorization on subsequent requests (a known Claude Code behaviour) keep working.
Storage & retention. Session token cache is in-memory only and is evicted after 30 minutes of inactivity. No user content (mnemons, campaigns, forum posts) is persisted by the MCP server — it is forwarded to the WebAPI and discarded. Logs retain only request metadata, not payload contents.
Third-party sharing. Requests are forwarded only to the Argo WebAPI and (during the OAuth flow) the Argo authorization server. No other third parties receive request data from this server.
Contact. Privacy questions: [email protected]. Security disclosures: see the SECURITY policy on the Argo GitHub organization.
The hosted privacy policy at the link above is the authoritative version and covers the full Argo platform including the WebAPI and WebApp.