Campfront CLI

The Campfront CLI puts Campfront AI in your terminal. Ask a question about your camp in plain English and it answers from your live data, in the window you're already working in. It's the same assistant as the Ask AI panel, with the same permissions and the same approval step before anything changes.

Installing

You'll need Node 22 or later. One command installs the CLI and signs you in:

npx campfront-install

To do it yourself instead:

npm install -g @campfront/cli
campfront login

You'll need an admin account for the camp you're connecting. Parent and staff accounts can't connect the CLI.

Connecting your camp

campfront login opens your browser, you sign in to your camp the way you always do, and the browser hands the CLI back a credential. Nothing is typed into the terminal, so your password never goes near it.

You can connect more than one camp. The first one you connect becomes the default, and --camp picks a different one for a single command:

campfront login --camp summerwood
campfront ask "how many campers are enrolled for 2026?" --camp summerwood

campfront whoami lists the camps you're connected to and the account each one uses.

Asking a question

Run campfront on its own to open a chat, or ask a single question and get the answer straight back:

campfront ask "how many campers are enrolled for 2026?"
campfront ask "which sessions still have space?"
campfront ask "what did the Patel family pay last season?"

Add --json to print the answer, the conversation id and the token usage as JSON, which makes the CLI easy to pipe into a script.

Anything that changes data needs your approval first. A one-shot ask won't approve on your behalf. It stops and tells you to run campfront and answer the prompt yourself.

Commands

  • campfront - Chat with the assistant

  • campfront chat - The same, said out loud

  • campfront ask "<question>" - Ask one question and print the answer

  • campfront login - Connect a camp and store its credential

  • campfront logout - Disconnect a camp and forget its credential

  • campfront whoami - View the camps you're connected to

Add --camp to any of them to pick the camp for that run, and campfront --help prints the same list in your terminal.

In the chat

Typing / lists what you can run and narrows the list as you keep typing. Tab completes the highlighted one and Enter runs it.

  • /new - Start a new conversation, dropping what's been said

  • /threads - View recent conversations and switch to one

  • /clear - Clear the screen, keeping what's been said

  • /whoami - View the camp and account you're connected as

  • /help - View these commands

  • /quit - Leave the chat

The up arrow walks back through the last 20 lines you sent, and the down arrow comes forward again.

Every run starts a fresh conversation, so the assistant isn't carrying yesterday's context into this morning's question. Earlier conversations are kept, and /threads picks one up when you want it.

/clear and /new do different jobs. /clear empties the screen and leaves the conversation running, so the assistant still knows what you've been talking about. /new starts over, and the assistant forgets.

Settings

Three environment variables change how the CLI behaves:

  • CAMPFRONT_CAMP - The camp subdomain to use when --camp is left out

  • CAMPFRONT_HOST - A different Campfront server to talk to

  • NO_COLOR - Turns color off when it's set to anything

Security and your data

The CLI acts as you, with your Campfront permissions. It can't read or change anything you couldn't read or change in the app, and every write still waits for your approval.

Credentials live in ~/.config/campfront/credentials.json. The CLI writes the folder and the file so that only your account can read them. The one secret stored there is a refresh token, one per camp, and it's revocable. Everything else the CLI uses is short lived and stays in memory for the length of the command.

Your chat history in the terminal is part of the session and nothing more. A question can name a camper, so the CLI never writes it to disk. /clear forgets it, and so does closing the terminal.

A copied credentials file is worth exactly as much as the refresh token in it. If a laptop goes missing, revoke that connection and the CLI on it stops working.

Disconnecting

campfront logout revokes the credential for a camp and deletes it from your machine.

To revoke from somewhere else, sign in to Campfront and open Camp settings > Integrations > MCP. Every connection you've made is listed there with a Revoke action. Revoking there stops the CLI on that machine whether or not you can still get to it.

Was this helpful?