+ 📄 Print-friendly! Use your browser's print function (Ctrl/Cmd + P) to get a landscape-oriented version perfect for events and quick reference. The layout will automatically adjust for optimal printing.
+
+
+
+
+
+
+ Install Arcade CLI globally using `uv` (recommended) or `pip`.
+
+ ```bash
+ uv tool install arcade-mcp # Recommended
+ pip install arcade-mcp # Alternative
+ ```
+
+ Verify installation:
+
+ ```bash
+ arcade --version
+ ```
+
+ Create and run your first server:
+
+ ```bash
+ arcade new my_server
+ cd my_server
+ arcade mcp http
+ ```
+
+ Get help on any command:
+
+ ```bash
+ arcade --help
+ arcade --help
+ ```
+
+ Use `uv` for faster installs and better dependency management
+
+
+
+
+
+ Authenticate with Arcade Cloud for deployments and secrets management.
+
+ | Command | Description |
+ |---------|-------------|
+ | `arcade login` | Opens browser for OAuth authentication |
+ | `arcade login --host ` | Login to custom Arcade instance |
+ | `arcade logout` | Clear local credentials |
+ | `arcade whoami` | Show logged-in user and active context |
+ | `arcade dashboard` | Open Arcade web UI in browser |
+ | `arcade dashboard --local` | Open local dashboard |
+
+ Credentials are stored in `~/.arcade/credentials.yaml`
+
+
+
+
+
+ Organizations group projects and team members. Projects contain servers, secrets, and configurations.
+
+ ```bash
+ # List all organizations
+ arcade org list
+
+ # Switch active organization
+ arcade org set
+ ```
+
+ Switching organization also resets your active project to that org's default.
+
+ Projects contain servers, secrets, and configurations.
+
+ ```bash
+ # List projects in active org
+ arcade project list
+
+ # Switch active project
+ arcade project set
+ ```
+
+ All deploy/secret commands use your active project context.
+
+
+ Use `arcade whoami` to see current org/project.
+
+
+
+
+
+ Scaffold a new MCP server project with boilerplate code.
+
+ ### Minimal Template (Quick Start)
+
+ ```bash
+ arcade new my_server
+ ```
+ Creates **pyproject.toml**, **src/my_server/__init__.py**, **src/my_server/server.py**.
+
+ ### Full Template (Production)
+
+ ```bash
+ arcade new my_server --full
+ ```
+
+ Creates: **pyproject.toml**, **my_server/** (package with tools), **tests/**, **evals/**, **Makefile**, **.pre-commit-config.yaml**, **.ruff.toml**, **LICENSE**, **README.md**.
+
+ ### Options
+
+ | Flag | Description |
+ |------|--------------|
+ | `--dir ` | Output directory (default: current) |
+ | `--full`, `-f` | Create full starter project |
+
+
+
+
+
+ Start your server locally for development and testing.
+
+ ### Transport Types
+
+ ```bash
+ # For MCP clients (Claude, Cursor)
+ arcade mcp stdio
+
+ # For web/API testing
+ arcade mcp http
+ ```
+
+ ### Examples
+ ```bash
+ arcade mcp http --port 8080 --reload --debug
+ arcade mcp stdio --tool-package github
+ arcade mcp http --discover-installed --show-packages
+ ```
+
+ Use `--reload` for faster development iteration
+
+
+
+
+
+ View available tools and their schemas from local or remote servers.
+
+ ```bash
+ # List all tools
+ arcade show
+
+ # Show local tools only
+ arcade show --local
+
+ # Show tool details
+ arcade show -t
+
+ # Full response structure
+ arcade show -t --full
+
+ # Filter by server
+ arcade show -T
+ ```
+
+ ### Options
+
+ | Flag | Description |
+ |------|--------------|
+ | `-t`, `--tool ` | Show specific tool details |
+ | `-T`, `--server ` | Filter by server |
+ | `--local`, `-l` | Show local catalog only |
+ | `--full`, `-f` | Show complete response (auth, logs) |
+
+
+
+
+
+ Auto-configure MCP clients to connect to your server.
+
+ ### Supported Clients
+
+ | Client | Command |
+ |------|--------------|
+ | Claude Desktop (`stdio` only) | `arcade configure claude` |
+ | Cursor IDE (`stdio` or `http`) | `arcade configure cursor` |
+ | VS Code (`stdio` or `http`) | `arcade configure vscode` |
+
+ Claude Desktop only supports `stdio` transport via configuration file.
+
+ ### Options
+
+ | Flag | Description | Default |
+ |------|-------------|--------|
+ | `--transport ` | `stdio` or `http` | `stdio` |
+ | `--host ` | `local` or `arcade` | `local` |
+ | `--port ` | Port for HTTP transport | `8000` |
+ | `--name ` | Server name in config | directory name |
+ | `--entrypoint ` | Entry file for stdio | `server.py` |
+
+
+
+
+
+ Deploy your MCP server to Arcade Cloud for production use.
+
+ ```bash
+ arcade deploy
+ ```
+
+ ### Options
+
+ | Flag | Description | Default |
+ |------|-------------|--------|
+ | `-e`, `--entrypoint ` | Python file that runs MCPApp | `server.py` |
+ | `--server-name ` | Explicit server name | auto-detected |
+ | `--server-version ` | Explicit server version | auto-detected |
+ | `--skip-validate` | Skip local health checks | off |
+ | `--secrets ` | Secret sync mode (see below) | `auto` |
+
+ ### Secrets Handling
+
+ | Mode | Description |
+ |------|-------------|
+ | `auto` | Sync only required secret keys (default) |
+ | `all` | Sync entire .env file |
+ | `skip` | Don't sync any secrets |
+
+ Run from your project root (where `pyproject.toml` is located).
+
+
+
+
+
+ Manage deployed servers in Arcade Cloud.
+
+ ```bash
+ # List all servers
+ arcade server list
+
+ # Get server details
+ arcade server get
+
+ # Enable a server
+ arcade server enable
+
+ # Disable a server
+ arcade server disable
+
+ # Delete a server (permanent!)
+ arcade server delete
+ ```
+
+
+ Delete is permanent and cannot be undone
+
+
+
+
+
+ View and stream logs from deployed servers.
+
+ ```bash
+ # View recent logs (last 1h)
+ arcade server logs
+
+ # Stream live logs
+ arcade server logs -f # Stream live logs
+ ```
+
+ ### Time Range Options
+
+ | Flag | Description | Example |
+ |------|-------------|---------|
+ | `-s`, `--since
+
+
+
+ Store API keys and sensitive configuration for your deployed servers. Secrets are encrypted and scoped to your active project.
+
+ ### List Secrets
+ ```bash
+ arcade secret list
+ ```
+ Shows: Key, Type, Description, Last accessed.
+
+ ### Set Secrets
+
+ ```bash
+ arcade secret set KEY=value
+ arcade secret set KEY1=v1 KEY2=v2
+ ```
+
+ ### From `.env` File
+
+ ```bash
+ arcade secret set --from-env
+ arcade secret set --from-env -f .env.prod
+ ```
+
+ ### Delete Secrets
+ ```bash
+ arcade secret unset KEY1 KEY2
+ ```
+
+
+ Use `arcade secret set --from-env` to sync local .env to Arcade Cloud before deploying.
+
+
+
+
+
+ Test tool-calling accuracy with evaluation suites.
+ ### Run Evaluations
+ ```bash
+ arcade evals # Current dir
+ arcade evals ./evals/ # Specific dir
+ ```
+ ### Capture Mode
+ ```bash
+ arcade evals --capture
+ ```
+### Output Options
+
+| Flag | Description |
+| ---------------------- | ------------------------------------------------- |
+| `--details`, `-d` | Show detailed results |
+| `--failed-only`, `-f` | Show only failed evals |
+| `--file ` | Write results to file |
+| `--format ` | Output format: `txt`, `md`, `html`, `json`, `all` |
+| `--max-concurrent ` | Concurrent evaluations (default: 1) |
+| `--add-context` | Include system/additional messages
+
+
+
+
+
+
+
+
--host
Bind address (127.0.0.1)
+
--port
Port number (8000)
+
--reload
Auto-reload on changes
+
--debug
Verbose logging
+
--tool-package
Load specific package
+
--discover-installed
Find arcade-* packages
+
--show-packages
List loaded packages
+
--env-file
Path to .env file
+
--name
Server name
+
--version
Server version
+
--otel-enable
Send logs to OTel
+
+
+
+
+
+
+
+ Available on most commands:
+
+ | Flag | Description |
+ |------|-------------|
+ | `-h`, `--help` | Show command help |
+ | `-v`, `--version` | Show CLI version |
+ | `-d`, `--debug` | Enable debug output |
+ | `--host ` | Arcade Engine host |
+ | `--port ` | Arcade Engine port |
+ | `--tls` | Force TLS connection |
+ | `--no-tls` | Disable TLS connection |
+
+
+ Use `--debug` when troubleshooting issues
+
+
+
+
+ Set these in your shell or `.env` file:
+
+ | Variable | Description |
+ |----------|--------------|
+ | `OPENAI_API_KEY` | OpenAI API key (for evals) |
+ | `ANTHROPIC_API_KEY` | Anthropic API key (for evals) |
+ | `ARCADE_API_BASE_URL` | Override Arcade API URL |
+
+ ```bash
+ # In shell
+ export OPENAI_API_KEY=sk-...
+
+ # Or in .env file
+ OPENAI_API_KEY=sk-...
+ ANTHROPIC_API_KEY=sk-ant-...
+ ```
+
+
+
+
+ ### Minimal Template (`arcade new my_server`)
+
+
+
+
+ Add `.env` (local secrets) and `.env.example` (template) to your project.
+
+
+
+
+
+ ### Common Issues
+
+ | Error | Solution |
+ |-------|-----------|
+ | "Not logged in" | Run `arcade login` |
+ | "Legacy credentials" | Run `arcade logout` then `arcade login` |
+ | "Module not found" | Run `uv pip install arcade-mcp[evals]` |
+ | "Server not healthy" | Check `arcade server logs -f` |
+ | "No tools found" | Verify `--tool-package` or `--discover-installed` |
+
+ ### Debug Tips
+ ```bash
+ arcade --debug # Verbose output
+ arcade server logs -f # Stream live logs
+ arcade show --local # Verify local tools
+ ```
+
+
+
+
+ - Use `--reload` during development for faster iteration
+ - Use `stdio` transport for Claude Desktop and Cursor
+ - Use `http` transport for web testing and debugging
+ - Always set secrets before deploying servers
+ - Run evaluations before every deploy
+ - Use `--full` template for production projects
+ - Check logs immediately after deploying
+ - Use `--debug` flag to see detailed request info
+ - Keep `.env.example` updated for your team
+ - Use project context when working with multiple projects
+
+
+
+
+ Standard development cycle for building MCP servers:
+
+ 1. **`arcade login`** — Authenticate with Arcade Cloud
+ 2. **`arcade new my_server`** — Create project (Minimal template)
+ 3. **Edit `src/my_server/server.py`** — Add your tools
+ 4. **`arcade mcp http --reload`** — Run locally with hot reload
+ 5. **`arcade configure cursor`** — Connect your IDE
+ 6. **Test tools in IDE** — Verify functionality
+ 7. **`arcade evals`** — Run evaluation suites
+ 8. **`arcade secret set --from-env`** — Sync secrets
+ 9. **`arcade deploy`** — Deploy to cloud (requires `server.py` entrypoint)
+ 10. **`arcade server logs -f`** — Monitor logs
+
+
+
+
diff --git a/public/llms.txt b/public/llms.txt
index 286da23b9..e6ae3115e 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -1,4 +1,4 @@
-
+
# Arcade
@@ -27,6 +27,7 @@ Arcade delivers three core capabilities: Deploy agents even your security team w
## API Reference
- [Arcade API Reference](https://docs.arcade.dev/en/references/api.md): The Arcade API Reference documentation provides users with essential information on how to interact with the Arcade API, including the base URL for requests and links to the OpenAPI specification. It emphasizes the requirement of having an account in good standing and adherence to the Terms of
+- [Arcade CLI Cheat Sheet](https://docs.arcade.dev/en/references/cli-cheat-sheet.md): The Arcade CLI Cheat Sheet serves as a quick reference guide for users to efficiently utilize all commands related to the Arcade CLI, including installation, authentication, project management, and server operations. It is designed for easy printing and provides essential commands and tips for various
- [Arcade MCP (MCP Server SDK) - Python Overview](https://docs.arcade.dev/en/references/mcp/python/overview.md): This documentation page provides an overview of the Arcade MCP (MCP Server SDK) for Python, detailing its purpose as a secure framework for programmatically building MCP servers with a minimal API. Users will learn about the key components, such as the `M
- [Errors](https://docs.arcade.dev/en/references/mcp/python/errors.md): This documentation page provides an overview of domain-specific error types associated with the MCP server and its components, detailing the MCP exception hierarchy for improved error handling and debugging. Users can learn about various exceptions, such as `MCPError`, `ServerError`,
- [Middleware](https://docs.arcade.dev/en/references/mcp/python/middleware.md): This documentation page provides an overview of the Middleware component in the Arcade MCP Server SDK for Python, detailing how users can intercept and modify requests and responses during processing. It outlines the base classes and methods for creating custom middleware, as well as built-in middleware