CI/CD & Headless Usage

For automation, pipelines, and non-interactive environments, use token-based authentication.

Setup

Set the ATOMS_ACCESS_TOKEN environment variable with a valid Supabase JWT:

export ATOMS_ACCESS_TOKEN="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

Obtaining a token

1. Run npx @atoms-tech/atoms-mcp login on your local machine
2. Extract the token from ~/.atoms/credentials.json:

cat ~/.atoms/credentials.json | jq -r '.access_token'

3. Store this as a secret in your CI/CD platform

GitHub Actions example

name: Requirements Check
on: [pull_request]

jobs:
  coverage:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '18'
      - run: npx @atoms-tech/atoms-mcp whoami
        env:
          ATOMS_ACCESS_TOKEN: ${{ secrets.ATOMS_ACCESS_TOKEN }}

Environment variables

Rate limits

The default rate limit is 60 requests per minute per user. For batch operations, use atoms_bulk_import to create up to 100 items in a single call instead of individual atoms_create_item calls.