scrapeatlas-setuplisted
Install: claude install-skill ScrapeAtlas/social-media-agent-skills
# ScrapeAtlas setup
Install the `scrapeatlas` CLI, give it a ScrapeAtlas API key without exposing the
key, and verify the connection with a free account read.
If the agent's runtime can connect to a remote MCP server with a custom header,
that also works: URL `https://api.scrapeatlas.com/mcp`, header
`Authorization: Bearer <API key>`, with the key taken from the runtime's secret
settings. The steps below cover the CLI.
## 1. Check Node.js
```bash
node --version
```
The CLI requires Node.js 22 or newer. If Node is missing or older, tell the user;
do not change the system Node installation without their approval.
## 2. Install the CLI
```bash
npm install -g @scrapeatlas/cli
scrapeatlas --version
```
If global installs are not allowed, run every command through npx instead:
`npx @scrapeatlas/cli@latest <command>`. To update an existing install, run
`npm install -g @scrapeatlas/cli@latest`.
## 3. Get an API key
Ask the user to create a key at https://scrapeatlas.com/dashboard/keys/. Calls
spend credits from that account.
Ask the user to store the key themselves as `SCRAPEATLAS_API_KEY` in the runtime's
secret or environment settings (for example the bot's environment variables, a
container secret or a CI secret). This keeps the key out of the conversation and
the agent's logs. Restart or reload the agent if the runtime requires it for new
variables.
## 4. Authenticate
The CLI reads credentials in this order: `--api-key`, then `SCRAPEATLAS_API_KEY`,
then the key saved