crea8.one

crea8one-agent

Agents that run shell commands use the crea8one-agent CLI. It reads CREA8_API_KEY from the environment. Agents that speak MCP should use the MCP server at https://mcp.crea8.one/mcp instead. ChatGPT setup is on the ChatGPT page.

Install

  1. Open https://app.crea8.one and create an API key under developer / API settings.
  2. Install the crea8one-agent command so it is on your PATH. The command name is crea8one-agent.
  3. Export CREA8_API_KEY in the environment the agent uses. A shell profile or the agent's secret store both work. Do not put the key in a prompt, a skill file, or a command argument.
  4. Save the skill below where that agent loads skills, or paste it into the agent's instructions.
  5. Run crea8one-agent once. The CLI prints the commands it accepts. The agent should use those, not guessed flags.

Set the key and run the CLI

export CREA8_API_KEY="your_api_key"
crea8one-agent

Skill

The skill tells the agent to call crea8one-agent for scheduling, Stalker mention monitoring, and Link-in-Bio, and to keep the API key in CREA8_API_KEY.

SKILL.md

---
name: crea8one
description: Use the crea8one-agent CLI for crea8.one scheduling, Stalker mention monitoring, and Link-in-Bio. Requires CREA8_API_KEY.
---

# crea8.one

crea8.one is a social media scheduler, Stalker (mention monitoring), and a Link-in-Bio.

Use the `crea8one-agent` command. It reads the API key from the `CREA8_API_KEY` environment variable. Do not pass the key as an argument, and do not ask for the key in the chat.

If `CREA8_API_KEY` is unset, tell the user to create a key at https://app.crea8.one under developer / API settings, then export `CREA8_API_KEY` in the environment that runs the command.

Run `crea8one-agent` and use the commands it prints. Do not invent flags or HTTP endpoints.

MCP clients should use https://mcp.crea8.one/mcp instead of this CLI. That server accepts OAuth, an `Authorization: Bearer` API key, and the same key on the path `/mcp/:apiKey`.

Usage

With CREA8_API_KEY set, ask the agent in plain language. It should run crea8one-agent and follow the command list the CLI prints.

  • Schedule a post, and say when it should go out.
  • Show what is already scheduled.
  • Check Stalker for mentions.
  • Read or update the Link-in-Bio.

The CLI does not take the API key as a flag. If a command fails because it is not authenticated, check that CREA8_API_KEY is set in that process, then run crea8one-agent again.

MCP or the CLI

Use the MCP server for ChatGPT, Claude, Claude Code, Cursor, Gemini CLI, Codex, Grok Build, Manus, and the other clients on that page. Use crea8one-agent when the agent runs commands and does not connect to an MCP server. Both use the key from developer / API settings. MCP can also sign in with OAuth, which the CLI does not.

Questions

What environment variable does the CLI read?

CREA8_API_KEY. Create the key at https://app.crea8.one under developer / API settings, then export it. The CLI does not read the key from a flag or a chat message.

Where is the command installed from?

Install the crea8one-agent command and put it on your PATH. These pages do not point at a package registry.

Can the same key be used with MCP?

Yes. MCP clients can send it as a Bearer token or as the /mcp/:apiKey path. OAuth on https://mcp.crea8.one/mcp does not need the key in the client config.