atoms_status

Check the health and authentication status of the ATOMS MCP server. This is the first tool you should call if other tools return errors or authentication failures.

This tool works without authentication. You can always call it to diagnose connection issues.

Parameters

This tool takes no parameters. It uses the environment configuration (ATOMS_ACCESS_TOKEN) automatically.

Parameter	Type	Required	Description
(none)	--	--	Uses environment configuration

Annotations

Annotation	Value
`readOnlyHint`	`true`
`destructiveHint`	`false`
`openWorldHint`	`false`

Example Response

Authenticated

{
  "status": "authenticated",
  "email": "engineer@example.com",
  "message": "Connected to ATOMS. Ready to use all tools."
}

Not Authenticated

{
  "status": "not_authenticated",
  "email": null,
  "message": "No valid access token found. Run the auth flow to get a token."
}

Expired Token

{
  "status": "expired",
  "email": "engineer@example.com",
  "message": "Access token has expired. Re-authenticate to continue."
}

When to Use

Diagnostics first. If any other ATOMS tool returns an auth error, call atoms_status before anything else.
Session startup. Verify the server is reachable and credentials are valid at the start of a session.
After credential changes. Confirm the new token is working after re-authentication.

Typical Workflow

atoms_status → atoms_list_projects → (other tools)

If the status returns "expired" or "not_authenticated", no other tools will work until you re-authenticate. See the Authentication guide for setup instructions.

atoms_status

On this page