Support

Last updated 2026-10-19

Help with the hosted Atoma service at atoma.run, its MCP server and the Atoma plugins for Claude and Codex.

What to include

• the email address you sign in with, and your organisation's name;
• the project and, for a run, its link or identifier, as shown in the app or returned by the MCP tools;
• what you expected, what happened instead, and when (with your time zone);
• for a connection problem, the client you use (Claude, Claude Code, Codex or another MCP client) and the exact error message.

Never send passwords, API keys or tokens. We will never ask for them.

Connecting Atoma to Claude or Codex

• Claude Code: run claude plugin marketplace add atoma-run/atoma, then claude plugin install atoma@atoma. Run /mcp in a session and sign in to Atoma in your browser.
• Any MCP client: add the server https://atoma.run/mcp (HTTP transport). Your client opens Atoma's sign-in page and asks you to approve access for your active organisation. You can also create an API token in the app's settings.
• The tools you see depend on your role. Viewers can read, members can start and cancel runs, and admins also choose the organisation's models.
• To revoke a client's access, remove it from the MCP access panel in the app's settings.

Common questions

A run is waiting for me

A run can pause to ask you a question it cannot settle alone. Answer it in the app or through your MCP client, and the run resumes.

A run stopped incomplete or failed

Open the run to see the step where it stopped and why. You can continue the project with a clarified goal. If you believe Atoma itself is at fault, send us the run's link.

My result was not published to GitHub

Publication needs an accepted result and an organisation connected to a GitHub App installation that can write to the target repository. The app shows each run's publication status.

Deleting my data

Write to mgf@atoma.run from the address linked to your account, and say what to delete: your account, an organisation you own, or a project. The privacy policy describes your rights.

Reporting a vulnerability

Report security issues privately through GitHub's private vulnerability reporting on github.com/atoma-run/atoma (Security tab, then "Report a vulnerability"), or by email to mgf@atoma.run. Do not disclose them publicly before they are fixed, and do not include a live credential or anyone else's data.

More

• Privacy policy and terms of service
• Source code and documentation: github.com/atoma-run/atoma