friday-studio MCP工具

Prerequisites

The daemon orchestrates several runtimes — Friday agents can be authored in TypeScript or Python, can drive a real browser, and fan out work over a message bus. Install the four below yourself, then scripts/setup-dev-env.sh handles the rest.

You install these (we won't touch your version managers):

setup-dev-env.sh handles these — installs if missing or below min, otherwise keeps yours:

Docker (optional) skips all of the above — docker compose up runs the whole stack in containers.

You don't need a separate database for local development — the daemon persists state through its embedded JetStream bus. Postgres is only needed for production deployments of the link credential service.

1. Clone and install

git clone https://github.com/friday-platform/friday-studio
cd friday-studio
bash scripts/setup-dev-env.sh    # bootstraps deno+go+uv+nats+agent-browser, runs deno install, pre-warms Python

setup-dev-env.sh checks each tool's version against the minimums above and keeps your existing toolchain wherever it satisfies them — auto- install only kicks in for missing or stale tools. It also runs `deno install`, writes the daemon envfile, and pre-warms the uv cache. Re-run it whenever the pinned friday-agent-sdk version bumps in tools/friday-launcher/paths.go.

If the script ends with a ⚠ Skipped: block, follow the per-tool hint and re-run. Common case: agent-browser install fails on a system Node — switch to a user-scoped Node manager (fnm/volta/nvm) and re-run to enable web/browser agents.

TLS-enabled installs. The chain tries the installed-Studio location first,

then the dev location written by `scripts/setup-tls.sh`. Skip this on

plain-HTTP installs.

set -a . "${FRIDAY_HOME:-$HOME/.friday/local}/.env" 2>/dev/null \ || . "$HOME/.atlas/.env" 2>/dev/null || true set +a curl -X POST ${FRIDAY_TLS_CA:+--cacert "$FRIDAY_TLS_CA"} \ "${FRIDAYD_URL:-http://localhost:8080}/review-pr" \ -d '{"pr_url": "https://github.com/your-org/your-repo/pull/42"}'

The workspace declares an HTTP signal at `/review-pr`, an LLM agent with
the `gh` MCP server, and a system prompt scoped to your team's review
checklist. Wire it to GitHub via `webhook-tunnel` for a public URL.

**Cron — drain my inbox before 9am:**

Docker

Want it all in containers?

docker compose up

Brings up the daemon, playground, link credential service, PTY server, and webhook tunnel. Ports default to 1xxxx to avoid host collisions — see docker-compose.yml.

Quickstart

Examples

2. Configure environment

```bash cp .env.example .env

open .env and set ANTHROPIC_API_KEY (or another provider key)

```

The example file documents every variable the daemon reads — provider keys, proxies, OAuth/GitHub App credentials, integration tokens. The minimum to run a real agent is one LLM provider key.

Source the daemon .env once so $FRIDAYD_URL / $FRIDAY_TLS_CA are set on