A
Atlas
...

CLI, MCP & AI Agents

You can create projects and form endpoints without opening the dashboard, from the atlas CLI, the Atlas MCP server, or plain HTTP. All three sign in with device login: the tool shows a link and a code, you approve it in your browser while signed in to Atlas, and the tool receives an account token (atl_...).

Plain-text instructions for AI coding agents are at atlasforms.app/llms/agent-setup.txt. Point your agent at that file and it can do the whole setup.

Credentials

CredentialPrefixUse it for
Account tokenatl_The CLI, the MCP server, and AI agents. Issued by device login. Covers all your projects.
Project API keyfep_Server-side integrations such as Zapier. Shown once when a project is created. Older CLI setups also used these.

The CLI and MCP server share credentials through ~/.atlasrc, so signing in to one signs in the other. Environment variables override the file: ATLAS_TOKEN for an account token, ATLAS_API_KEY for a project key.

Never paste a token or API key into an AI chat, and never commit one to your repository. Form endpoints (https://atlasforms.app/f/...) are public URLs and are safe to commit.

You can revoke any connected tool in Settings → API → Connected agents.

CLI

The CLI needs Node 18 or later.

bash
npm install -g https://atlasforms.app/dl/atlasforms-cli-0.1.3.tgz
# or, without installing:
npx -y https://atlasforms.app/dl/atlasforms-cli-0.1.3.tgz <command>

Sign in

bash
atlas login

The CLI prints a URL and a code and opens your browser. Approve the request there, and the CLI saves an account token to ~/.atlasrc.

  • --no-browser: print the URL without opening a browser. Use this over SSH and in AI agents. The command waits up to 10 minutes for approval.
  • --api-key : use an existing key (fep_... or atl_...) instead of a device login, for example a project key from an older setup.
  • bash
    atlas whoami   # show the signed-in account
    atlas logout   # revoke this machine's token and remove stored credentials

    Projects

    bash
    atlas projects list
    atlas projects create "My Website" --origin example.com          # includes a default contact form
    atlas projects create "My Website" --origin example.com --json   # machine-readable output
    atlas projects create "Shop" --webhook https://example.com/hook

    Set --origin to the site's production domain. A form with no allowed domains rejects every submission from the live site. Localhost testing works without it.

    Forms

    bash
    atlas forms list --project PROJECT_ID
    atlas forms create "Newsletter" --project PROJECT_ID
    atlas forms create "Contact" --project PROJECT_ID --origin example.com   # override the project's allowed domains
    atlas forms create "Waitlist" --project PROJECT_ID --slug waitlist --redirect https://example.com/thanks --json
    atlas forms create "Contact" --project PROJECT_ID --spam-filter          # turn on the AI spam filter
    atlas forms update FORM_ID --spam-filter off                              # change an existing form
    atlas forms update FORM_ID --webhook https://example.com/hook --json     # only the options you pass change

    The output includes the form's endpoint, such as https://atlasforms.app/f/abc123xyz.

    --spam-filter turns on the free AI spam filter, which sends submission text to Cloudflare Workers AI. It is off by default; only turn it on if the site owner wants it. atlas forms update takes the form's ID from atlas forms list and accepts --name, --webhook, --redirect, --origin (none removes a URL or returns to the project's domains) and --spam-filter on|off.

    Other commands

  • atlas list: list projects, or forms with --project
  • atlas init: create a form interactively (needs a terminal; agents use atlas forms create)
  • atlas submissions: view recent submissions (--project, --form, --limit, --include-spam, --json)
  • atlas usage: plan, submissions and file storage used, with warnings (--json); atlas upgrade opens the billing page
  • atlas sandbox --form FORM_ID --action status: manage localhost testing for a form (register, add-ip --ip , generate-key, revoke-key --yes). FORM_ID is the form's ID from atlas forms list, not the public id in the endpoint URL.
  • Every command exits with status 1 on an error, including when you are not signed in.

    The full reference is at atlasforms.app/llms/cli.txt.

    MCP Server

    The MCP server lets AI coding assistants such as Claude Code, Cursor, Windsurf, and VS Code / Copilot manage your forms.

    Claude Code:

    bash
    claude mcp add atlas-forms -- npx -y https://atlasforms.app/dl/atlasforms-mcp-0.1.3.tgz

    Other MCP clients (for example .cursor/mcp.json):

    json
    {
      "mcpServers": {
        "atlas-forms": {
          "command": "npx",
          "args": ["-y", "https://atlasforms.app/dl/atlasforms-mcp-0.1.3.tgz"]
        }
      }
    }

    You don't need to configure an API key. If no credentials are found, the server starts signed out and the agent signs in with two tools:

  • atlas_login starts a device login and returns a link and a code. The user opens the link, checks the code, and clicks Approve. Pass force: true to start a new login when already signed in.
  • atlas_login_complete finishes the login and saves the token to ~/.atlasrc. It waits up to about 50 seconds; if the login is still pending, call it again.
  • Running atlas login in a terminal also signs in the MCP server.

    atlas_create_project and atlas_create_form accept allowed_origins. atlas_create_form also accepts ai_spam_filter, atlas_update_form changes an existing form's settings (including ai_spam_filter), and atlas_get_submissions accepts include_spam.

    Other tools: atlas_list_projects, atlas_create_project, atlas_list_forms, atlas_create_form, atlas_update_form, atlas_get_form_endpoint, atlas_get_submissions, atlas_sandbox_status, atlas_sandbox_register_ip, atlas_sandbox_add_ip, atlas_sandbox_generate_key, atlas_usage.

    The full reference is at atlasforms.app/llms/mcp.txt.

    Agent Skill

    For Claude Code and other agents that load Agent Skills, Atlas publishes a skill that teaches the agent to use the MCP tools, the CLI, or the HTTP API:

    bash
    mkdir -p ~/.claude/skills/atlas-forms && curl -fsSL https://atlasforms.app/skills/atlas-forms/SKILL.md -o ~/.claude/skills/atlas-forms/SKILL.md

    Install it under .claude/skills/atlas-forms/ in your repository instead to share it with your team.

    HTTP

    Any tool that can make HTTP requests can use device login directly:

  • POST /api/v1/auth/device starts a login and returns device_code, user_code, and verification_uri_complete.
  • Show the user the link and code, then poll POST /api/v1/auth/device/token with the device_code every interval seconds until it returns access_token.
  • Send the token as Authorization: Bearer atl_....
  • DELETE /api/v1/auth/token revokes the token.
  • Then create a project and forms:

    bash
    # Create a project (includes a default "Contact Form")
    curl -s -X POST https://atlasforms.app/api/v1/projects \
      -H "Authorization: Bearer $ATLAS_TOKEN" \
      -H "Content-Type: application/json" \
      -d &#x27;{"name": "Acme Marketing Site", "allowed_origins": ["acme.com"]}'
    
    # Create another form in it
    curl -s -X POST https://atlasforms.app/api/v1/projects/<project_id>/forms \
      -H "Authorization: Bearer $ATLAS_TOKEN" \
      -H "Content-Type: application/json" \
      -d &#x27;{"name": "Newsletter Signup"}'

    See Authentication for the full device login reference and Projects & Forms for the request and response fields.