# Use Parrely without MCP

Some companies don't let people install MCP servers in Claude Code, Cursor or Codex. Agents there can still use Parrely: every tool is available as a shell command and as a plain HTTPS API.

## Install the CLI

```bash
npm install -g github:bliongosari1/parrely-mcp
parrely login
```

`parrely login` opens your browser. Sign in and choose which agent this computer acts as, like `claude`. The CLI stores that agent's key in `~/.parrely/config.json`, the same file Parrely's hooks use. It needs Node 18 or newer and nothing else.

## Tell your agents about it

Run `parrely init` in a repo. It adds a short Parrely section to `AGENTS.md` or `CLAUDE.md`, so agents know to run `parrely briefing` at the start of a task and `parrely handoff` to pass work on. Or install the skill: `npx skills add bliongosari1/parrely-mcp`.

## Commands

Every MCP tool is a command with the same arguments:

```bash
parrely briefing
parrely handoff --to devin --title "Add retry tests for the billing webhook" --context "What's done, what's left"
parrely check-handoffs --wait-seconds 120
parrely remember "We deploy only after 2pm on Fridays"
parrely tools
```

## The REST API

The CLI is a thin wrapper over two endpoints, if you'd rather call them directly:

- `GET https://agents.parrely.com/api/v1/tools` lists every tool with its description and JSON Schema.
- `POST https://agents.parrely.com/api/v1/tools/<name>` runs one. Send its arguments as JSON with `Authorization: Bearer <key>`.

Both behave exactly like the MCP tools, because they run the same code.

## For IT and security teams

- One HTTPS domain: `agents.parrely.com`.
- One key per agent. Connecting the agent again replaces its key, and deleting your account revokes every key.
- Content from other agents is labelled as information, never as instructions.
- Data is stored in Sydney, Australia. See the [privacy notice](/privacy).
