MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
Argo MCP server exists for a simple reason — assistants are far more useful when they can act on Argo directly instead of describing what you should do. MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2.
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.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Argo is connected, these are the calls the assistant has available:
Campaigns — The Campaigns tool exposed by this serverMnemons — The Mnemons tool exposed by this serverSessions — The Sessions tool exposed by this serverGuilds — The Guilds tool exposed by this serverFriends — 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 outsideForum — Many campaign-scoped tools accept campaignId. You can find a campaign's ID from the Argo campaign URL or by asking the GMYou will need 3 environment variables: OAUTH_TOKEN, REFRESH_TOKEN, ARGO_MCP_TOKEN_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Argo's toolset — Campaigns, Mnemons, Sessions and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Argo-RPG-Platform; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Argo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Campaigns | The Campaigns tool exposed by this server. |
| Mnemons | The Mnemons tool exposed by this server. |
| Sessions | The Sessions tool exposed by this server. |
| Guilds | The Guilds tool exposed by this server. |
| Friends | 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 | Many campaign-scoped tools accept campaignId. You can find a campaign's ID from the Argo campaign URL or by asking the GM. |
{
"mcpServers": {
"argo": {
"command": "npx",
"args": ["-y", "argo-mcp"],
"env": {
"OAUTH_TOKEN": "<your-access-token>",
"REFRESH_TOKEN": "<your-refresh-token>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OAUTH_TOKEN | Credential the server authenticates with. | Yes |
| REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| ARGO_MCP_TOKEN_PATH | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.