Versions: * arcade-mcp\==1.0.0rc1 * arcade-mcp-server\==1.0.0rc1 * arcade-core\==2.5.0rc1 * arcade-tdk\==2.6.0rc1 * arcade-serve\==2.2.0rc1 ### Summary Adds first-class MCP support across Arcade, introduces a new MCP server and CLI, unifies the project under the arcade-mcp name, overhauls templates/scaffolding, and improves developer tooling, secrets management, and examples. ### Highlights - **MCP Server & Core** - New MCP server with stdio and HTTP/SSE transports, session management, resumability, and lifecycle handling. - FastAPI-like `MCPApp` for building servers with lazy init; integrated worker+MCP HTTP app option. - Middleware system (logging and error handling), robust exception hierarchy, and Pydantic-based settings. - Async-safe managers for tools, resources, and prompts backed by registries and locks. - Developer-facing, transport-agnostic runtime context interfaces (logs, tools, prompts, resources, sampling, UI, notifications). - Conversion from Arcade ToolDefinition to MCP tool schema; OpenAI JSON tool schema converter. - Parser supports `@app.tool`/`@app.tool(...)` decorators. - **CLI** - New `mcp` command to run MCP servers with stdio or HTTP/SSE. - New `secret` command to set/list/unset tool secrets (supports .env input, preserves original casing for lookups). - `new` command refactored; option to create a full toolkit package with scaffolding. - `chat` command removed. - `serve.py` imports updated to `arcade_serve.fastapi.telemetry`; version retrieval now uses `arcade-mcp`. - `show.py` refactor to use new local catalog utilities. - `display_tool_details` improved: adds “Default” column and handles nested properties. - **Configuration & Discovery** - New `configure.py` to set up Claude Desktop, Cursor, and VS Code to connect to local or Arcade Cloud MCP servers. - Discovery utilities to find/install toolkits, build `ToolCatalog`s, analyze files for tools, load kits from directories (pyproject parsing), and build minimal toolkits. - Better handling of provider API key resolution and evaluation suite loading. - **Templates & Scaffolding** - Reorganized template structure (minimal vs full); moved `.pre-commit-config.yaml`, `.ruff.toml`, license, Makefile, README, tests, and tools layout to correct paths. - Minimal template adds `.env.example` for runtime secret injection. - Template pyproject updated for MCP servers; includes sample server with greeting and secret-reveal tools. - Authorization flow in templates simplified. - **Repo-wide Renaming & Examples** - Migrates references from `arcade-ai` to `arcade-mcp` across READMEs, scripts, and package metadata. - Examples updated (LangChain/LangGraph/AI SDK/TypeScript) and package name changed to `arcade-mcp-sdk`. - **Evals & Core Utilities** - Evals now use OpenAI tooling format (`OpenAIToolList`, `to_openai`); `tool_eval` takes `provider_api_key`. - Core utilities: fixed `does_function_return_value` by dedenting before parse; version bump to `2.5.0rc1` and dependency cleanup. - **Tooling & CI** - `setup-uv-env` action splits toolkit vs contrib dependency installation. - Pre-commit: excludes `libs/arcade-mcp-server/mkdocs.yml` and `libs/tests/` from YAML and Ruff hooks; Ruff per-file ignores (e.g., C901 in `libs/**/*.py`, TRY400 in server docs paths). - Makefile updates for uv env setup, quality checks, tests, builds, and new `shell` target. - Added Makefile to MCP server library to streamline dev workflow. - **Cleanup** - Removed `claude.json` config. - Simplified stdio entrypoint; removed unused imports (`arcade_gmail`, `arcade_search`). ### Breaking Changes - **CLI**: `chat` command removed; use `mcp`, `secret`, and updated `new`. - **Naming**: All users should update references from `arcade-ai` to `arcade-mcp`. - **Templates**: File paths moved; downstream scripts referencing old template locations may need updates. ### Getting Started - Run an MCP server: - `arcade mcp --stdio --toolkits your_toolkit` - `arcade mcp --http --toolkits your_toolkit` - Manage secrets: - `arcade secret set your_toolkit KEY=value` - `arcade secret list your_toolkit` - `arcade secret unset your_toolkit KEY` - Configure clients: - `arcade configure` to set up Claude Desktop, Cursor, and VS Code for local/Arcade Cloud MCP. --------- Co-authored-by: Sam Partee <sam@arcade-ai.com> Co-authored-by: Shub <125150494+shubcodes@users.noreply.github.com>
123 lines
3.3 KiB
Markdown
123 lines
3.3 KiB
Markdown
# Arcade Docker Compose Guide
|
|
|
|
This guide provides detailed instructions on how to set up and run Arcade using Docker Compose.
|
|
|
|
## Prerequisites
|
|
|
|
- **Docker** installed on your system. [Install Docker](https://docs.docker.com/get-docker/)
|
|
- **Docker Compose** installed. It comes bundled with Docker Desktop on Windows and macOS. For Linux, follow the [Docker Compose installation guide](https://docs.docker.com/compose/install/).
|
|
|
|
## Getting Started
|
|
|
|
### 1. Clone the Repository
|
|
|
|
Begin by cloning the Arcade repository:
|
|
|
|
```bash
|
|
git clone https://github.com/ArcadeAI/arcade-mcp.git
|
|
```
|
|
|
|
### 2. Build package wheels
|
|
|
|
From the root of the arcade-mcp repository:
|
|
|
|
```bash
|
|
make full-dist
|
|
```
|
|
|
|
### 3. Copy and Configure Environment Variables
|
|
|
|
Change to the `docker` directory:
|
|
|
|
```bash
|
|
cd arcade-mcp/docker
|
|
```
|
|
|
|
Copy the example environment file to `.env`:
|
|
|
|
```bash
|
|
cp env.example .env
|
|
```
|
|
|
|
Open the `.env` file in your preferred text editor and fill in the required values. At a minimum, you **must** provide the `OPENAI_API_KEY`:
|
|
|
|
```env:.env
|
|
### LLM ###
|
|
|
|
OPENAI_API_KEY=your_openai_api_key_here
|
|
```
|
|
|
|
If you plan to use other Large Language Model (LLM) providers, add their API keys as well:
|
|
|
|
```env:.env
|
|
ANTHROPIC_API_KEY=your_anthropic_api_key_here
|
|
```
|
|
|
|
### 4. Run Docker Compose
|
|
|
|
Start the Arcade services using Docker Compose:
|
|
|
|
```bash
|
|
docker compose up
|
|
```
|
|
|
|
This command will build and start all the services defined in the `docker-compose.yml` file and make their ports available to your host machine.
|
|
|
|
### 5. Verify the Engine is Running
|
|
|
|
In a separate terminal window, check if the engine is running:
|
|
|
|
```bash
|
|
curl http://localhost:9099/v1/health
|
|
```
|
|
|
|
You should receive a response indicating that the engine is healthy:
|
|
|
|
```json
|
|
{ "healthy": "true" }
|
|
```
|
|
|
|
Open a browser and navigate to http://localhost:9099/dashboard to view the Arcade dashboard.
|
|
|
|
## Adding Authentication Providers
|
|
|
|
Arcade supports various authentication providers. To add an auth provider, follow these steps:
|
|
|
|
### 1. Enable the Auth Provider in the Configuration
|
|
|
|
Edit the `docker.engine.yaml` file to enable the desired auth provider. For example, to enable Google authentication, modify the file as follows:
|
|
|
|
```yaml:docker.engine.yaml
|
|
auth:
|
|
providers:
|
|
- id: google
|
|
enabled: true # Change from false to true
|
|
```
|
|
|
|
### 2. Add Client ID and Secret to the `.env` File
|
|
|
|
Obtain the client ID and client secret from your auth provider and add them to the `.env` file:
|
|
|
|
```env:.env
|
|
GOOGLE_CLIENT_ID="your_google_client_id"
|
|
GOOGLE_CLIENT_SECRET="your_google_client_secret"
|
|
```
|
|
|
|
Repeat this step for any other auth providers you wish to enable.
|
|
|
|
### 3. Restart the Docker Compose Services
|
|
|
|
After making changes to the configuration, restart the services:
|
|
|
|
```bash
|
|
docker compose down
|
|
docker compose up
|
|
```
|
|
|
|
## Troubleshooting
|
|
|
|
- **Engine Health Check Fails**: Ensure that all environment variables are correctly set in the `.env` file and that the services have started without errors.
|
|
- **Port Conflicts**: If the default ports are already in use, modify the ports in the `docker-compose.yml` file.
|
|
- **Authentication Errors**: Double-check the client IDs and secrets provided for auth providers.
|
|
|
|
NOTE: `arcade login` will not work within a docker container, you must copy your credentials into the container if you would like to use it.
|