Argo Mcp

Please install the `argo-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 20 or later** — Node.js 20+ is required to run the local stdio MCP server via npx.
- **Have an Argo account and campaign access** — You need an Argo account with at least one campaign available to the authenticated user.
- **Authenticate with Argo** — Sign in once on the machine running the MCP client to store OAuth tokens locally. This is the recommended local setup and avoids putting tokens in MCP config. Run: `npx -y argo-mcp auth login`

Optional prerequisites:
- Optional: obtain OAuth tokens manually — For CI, Docker, or explicit env-based setup, open the Argo consent flow to get an access token and optional refresh token. (https://app.argo.games/oauth2/mcp-connect)

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","argo-mcp"]
- optional environment variables:
  - `OAUTH_TOKEN`: OAuth2 access token from the Argo consent flow. If set, it overrides the local token store created by auth login. (example: `<your-access-token>`)
  - `REFRESH_TOKEN`: OAuth2 refresh token used to automatically renew the access token when it expires. (example: `<your-refresh-token>`)
  - `ARGO_API_BASE`: Override the Argo API base URL. (example: `<your-api-base-url>`)
  - `ARGO_MCP_TOKEN_PATH`: Override the local token file path used by auth login. (example: `<your-token-file-path>`)

Note: The README also supports a hosted HTTP endpoint for remote clients like ChatGPT and VS Code at https://mcp.argo.games/mcp, with OAuth handled by the client. For local MCP clients, the preferred portable install path is stdio via `npx -y argo-mcp` with no env vars after running `auth login`.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.