← ClaudeAtlas

setup-octomaillisted

Use when setting up or troubleshooting Octomail, this multi-account Gmail MCP server — configuring OAuth credentials, authorizing Gmail accounts, verifying they work, or registering the server with an MCP client.
zerostorypoints/octomail-mcp · ★ 0 · AI & Automation · score 70
Install: claude install-skill zerostorypoints/octomail-mcp
# Setting up Octomail This server exposes several Gmail accounts to an MCP client, each addressed by an alias. Setting it up means: OAuth credentials once, then one authorization per account, then registering the server with the client. ## Important: you have no TTY `npm run setup` with no arguments prompts interactively and will refuse to run without a terminal. Always drive it with flags instead. ## Steps 1. **Check the current state first.** ```bash npm run doctor ``` Read the output before doing anything. It reports Node version, whether the build is current, whether OAuth credentials resolve, and for each configured account either `✓ alias → address` or a `✗` line containing the exact command that fixes it. A `!` line may also appear alongside either one, warning that a token file's permissions are wrong. If everything is `✓`, there is nothing to do. 2. **If OAuth credentials are missing**, do not try to create them yourself. Tell the user to follow `docs/google-cloud-setup.md`, and stress the publishing-status point: a Testing-status app expires refresh tokens after 7 days. Do not ask the user to paste the client secret into the chat, and do not write it yourself. Direct them to put it in `.env` themselves: ```bash npm run setup ``` Run from their own terminal, that prompts for the client ID and secret and writes `.env` at mode `0600` without the value ever passing through you. Alternatively they can cr