@mcp-use/cli 3.6.5-canary.1 → 4.0.0-beta.1

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@mcp-use/cli",
   "type": "module",
-  "version": "3.6.5-canary.1",
-  "description": "The mcp-use CLI is a tool for building and deploying MCP servers with support for ChatGPT Apps, Code Mode, OAuth, Notifications, Sampling, Observability and more.",
+  "version": "4.0.0-beta.1",
+  "description": "Compatibility proxy for the CLI included in mcp-use v2",
   "author": "mcp-use, Inc.",
   "license": "MIT",
   "homepage": "https://github.com/mcp-use/mcp-use#readme",
@@ -17,58 +17,30 @@
   "keywords": [
     "mcp",
     "model-context-protocol",
-    "cli",
-    "build-tool",
-    "widget",
-    "ui",
-    "react",
-    "esbuild",
-    "bundler",
-    "typescript"
+    "cli"
   ],
   "bin": {
-    "mcp-use": "./dist/index.cjs"
+    "mcp-use": "./dist/index.js"
   },
   "files": [
     "dist"
   ],
   "engines": {
-    "node": "^20.19.0 || >=22.12.0"
-  },
-  "peerDependencies": {
-    "react": "^18.0.0 || ^19.0.0",
-    "react-dom": "^18.0.0 || ^19.0.0",
-    "react-router-dom": "^7.12.0"
+    "node": ">=22.22.2"
   },
   "dependencies": {
-    "@tailwindcss/vite": "^4.2.0",
-    "@vitejs/plugin-react": "^6.0.0",
-    "chalk": "^5.6.2",
-    "chokidar": "^5.0.0",
-    "commander": "^14.0.2",
-    "dotenv": "^17.3.1",
-    "esbuild": "0.28.1",
-    "open": "^11.0.0",
-    "tar": "^7.5.16",
-    "tsx": "^4.21.0",
-    "vite": "^8.0.16",
-    "vite-plugin-singlefile": "^2.3.2",
-    "ws": "^8.19.0",
-    "zod": "4.3.5",
-    "@mcp-use/inspector": "12.0.4-canary.1",
-    "mcp-use": "1.34.4-canary.1"
+    "mcp-use": "^2.0.0-beta.12"
   },
   "devDependencies": {
-    "@types/ws": "^8.18.1",
-    "vitest": "^4.1.0"
+    "rimraf": "^6.1.3",
+    "tsup": "^8.5.1",
+    "typescript": "^5.9.3"
   },
   "publishConfig": {
     "access": "public"
   },
   "scripts": {
-    "build": "tsup && tsc --emitDeclarationOnly --declaration",
-    "dev": "tsc --watch",
-    "test": "vitest run",
-    "test:watch": "vitest"
+    "build": "rimraf dist && tsup src/index.ts --format esm --target node22 && tsc --emitDeclarationOnly --declaration",
+    "test": "node --test tests/proxy.test.mjs"
   }
 }

package/LICENSE

@@ -1,22 +0,0 @@
-MIT License
-
-Copyright (c) 2025 mcp-use, Inc.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-

package/README.md

@@ -1,570 +0,0 @@
-<div align="center" style="margin: 0 auto; max-width: 80%;">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/mcp-use/mcp-use/main/static/logo_white.svg">
-    <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/mcp-use/mcp-use/main/static/logo_black.svg">
-    <img alt="mcp use logo" src="https://raw.githubusercontent.com/mcp-use/mcp-use/main/static/logo_white.svg" width="80%" style="margin: 20px auto;">
-  </picture>
-</div>
-
-<h1 align="center">mcp-use CLI</h1>
-
-<p align="center">
-    <a href="https://www.npmjs.com/package/@mcp-use/cli" alt="NPM Downloads">
-        <img src="https://img.shields.io/npm/dw/@mcp-use/cli.svg"/></a>
-    <a href="https://www.npmjs.com/package/@mcp-use/cli" alt="NPM Version">
-        <img src="https://img.shields.io/npm/v/@mcp-use/cli.svg"/></a>
-    <a href="https://github.com/mcp-use/mcp-use/blob/main/LICENSE" alt="License">
-        <img src="https://img.shields.io/github/license/mcp-use/mcp-use" /></a>
-    <a href="https://github.com/mcp-use/mcp-use/stargazers" alt="GitHub stars">
-        <img src="https://img.shields.io/github/stars/mcp-use/mcp-use?style=social" /></a>
-    <a href="https://discord.gg/XkNkSkMz3V" alt="Discord">
-        <img src="https://dcbadge.limes.pink/api/server/XkNkSkMz3V?style=flat" /></a>
-</p>
-
-🛠️ **mcp-use CLI** is a powerful build and development tool for creating MCP (Model Context Protocol) applications with integrated UI widgets. It enables developers to build MCP servers with custom React components that can be served alongside their MCP tools, providing rich visual interfaces for AI interactions.
-
-## 📦 Related Packages
-
-| Package                                                                                                             | Description             | Version                                                                                                         |
-| ------------------------------------------------------------------------------------------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------- |
-| [mcp-use](https://github.com/mcp-use/mcp-use/tree/main/libraries/typescript/packages/mcp-use)                       | Core MCP framework      | [![npm](https://img.shields.io/npm/v/mcp-use.svg)](https://www.npmjs.com/package/mcp-use)                       |
-| [@mcp-use/inspector](https://github.com/mcp-use/mcp-use/tree/main/libraries/typescript/packages/inspector)          | Web-based MCP inspector | [![npm](https://img.shields.io/npm/v/@mcp-use/inspector.svg)](https://www.npmjs.com/package/@mcp-use/inspector) |
-| [create-mcp-use-app](https://github.com/mcp-use/mcp-use/tree/main/libraries/typescript/packages/create-mcp-use-app) | Create MCP apps         | [![npm](https://img.shields.io/npm/v/create-mcp-use-app.svg)](https://www.npmjs.com/package/create-mcp-use-app) |
-
----
-
-## ✨ Key Features
-
-| Feature                  | Description                                                                          |
-| ------------------------ | ------------------------------------------------------------------------------------ |
-| **🚀 Auto Inspector**    | Automatically opens the MCP Inspector in your browser when development server starts |
-| **♻️ Hot Reload**        | Development mode with automatic reloading for both server code and UI widgets        |
-| **🎨 Widget Builder**    | Compiles React components into standalone HTML pages with all dependencies bundled   |
-| **📦 Production Ready**  | Optimized production builds with hashed assets for caching                           |
-| **🛠️ TypeScript First**  | Full TypeScript support with watch mode compilation                                  |
-| **🖥️ Multi-Environment** | Separate commands for development, build, and production deployment                  |
-
----
-
-## 🚀 Installation
-
-```bash
-# Install globally
-npm install -g @mcp-use/cli
-
-# Or use with npx (no installation needed)
-npx @mcp-use/cli dev
-
-# Install as a project dependency
-npm install --save-dev @mcp-use/cli
-```
-
----
-
-## 📖 Usage
-
-### Development Mode
-
-Start a development server with hot reload, automatic TypeScript compilation, and auto-opening inspector:
-
-```bash
-mcp-use dev [options]
-```
-
-**What happens in dev mode:**
-
-1. TypeScript files are compiled in watch mode
-2. UI widgets are built with hot reload
-3. Server runs with auto-restart on changes (via tsx)
-4. Inspector automatically opens in your browser at `http://localhost:3000/inspector`
-5. MCP endpoint is available at `http://localhost:3000/mcp`
-
-**Options:**
-
-- `-p, --path <path>` - Project directory (default: current directory)
-- `--port <port>` - Server port (default: 3000)
-- `--no-open` - Don't auto-open inspector in browser
-
-### Production Build
-
-Build your MCP application for production deployment:
-
-```bash
-mcp-use build [options]
-```
-
-**What happens during build:**
-
-1. TypeScript is compiled to JavaScript
-2. All `.tsx` files in `resources/` are bundled as standalone HTML pages
-3. Assets are hashed for optimal caching
-4. Output is optimized and minified
-
-**Options:**
-
-- `-p, --path <path>` - Project directory (default: current directory)
-
-### Production Server
-
-Start the production server from built files:
-
-```bash
-mcp-use start [options]
-```
-
-**Options:**
-
-- `-p, --path <path>` - Project directory (default: current directory)
-- `--port <port>` - Server port (default: 3000)
-
-### Cloud Deployment
-
-Deploy your MCP server to production via [manufact.com](https://manufact.com):
-
-```bash
-# Login to Manufact cloud
-mcp-use login
-
-# Non-interactive login with a pre-approved device code (web onboarding, agents)
-mcp-use login --device-code <code>
-
-# Non-interactive login (for agents / CI) — picks an org without prompting
-mcp-use login --org <slug|id|name>
-
-# Check authentication status
-mcp-use whoami
-
-# Deploy your MCP server
-mcp-use deploy [options]
-
-# Logout
-mcp-use logout
-```
-
-**Deploy Options:**
-
-- `--no-github` - Upload local source without connecting GitHub (platform-managed repo)
-- `--name <name>` - Custom deployment name
-- `--port <port>` - Server port (default: 3000)
-- `--runtime <runtime>` - Runtime environment: "node" or "python"
-- `--branch <name>` - Deploy branch (default: current git branch). Also scopes `--env` / `--env-file` sync to that branch's preview env.
-- `--env <key=value...>` - Set environment variable **values** (repeatable)
-- `--env-file <path>` - Load environment variable values from a `.env` file
-- `--root-dir <path>` - Subdirectory to deploy from (monorepos)
-- `--watch-paths <glob...>` - Only auto-deploy when matching files change (monorepos); set on new-server creation
-- `--wait-for-ci` - Hold GitHub auto-deploys until other check runs pass; set on new-server creation
-- `--open` - Open deployment in browser after success
-
-**Example:**
-
-```bash
-# Basic deployment (from GitHub when configured)
-mcp-use deploy
-
-# Deploy without GitHub — uploads local source
-mcp-use deploy --no-github
-
-# Deploy with custom options
-mcp-use deploy --name my-server --port 8000 --open
-
-# Deploy a branch and scope env values to its preview env
-mcp-use deploy --branch feature-x --env API_KEY=abc123
-```
-
----
-
-## ☁️ Managing cloud servers
-
-After a server exists you can update its configuration and environment
-variables without redeploying from scratch.
-
-### `servers update`
-
-Mutate server-level config in place (no delete/recreate, so the URL slug and
-env vars are preserved):
-
-```bash
-# Change the production branch (which branch triggers production deploys)
-mcp-use servers update my-server --branch main
-
-# Override build / start commands or rename the server
-mcp-use servers update my-server --build-command "npm run build" --start-command "npm start"
-mcp-use servers update my-server --name "My Server" --description "…"
-
-# Clear a build/start override (pass an empty string)
-mcp-use servers update my-server --build-command "" --start-command ""
-
-# Monorepos: scope auto-deploys to an app's own files + shared code
-mcp-use servers update my-server \
-  --watch-paths "apps/my-server/**" "packages/shared/**" \
-  --deploy-branches "release/*"
-```
-
-Flags: `--branch` (production branch), `--name`, `--description`,
-`--build-command`, `--start-command`, `--root-dir`, `--watch-paths`,
-`--deploy-branches`, `--wait-for-ci` / `--no-wait-for-ci`, `--org`. At least
-one is required. Pass an empty string to `--build-command`, `--start-command`,
-or `--root-dir` to clear it; pass an empty string to `--watch-paths` /
-`--deploy-branches` to clear the filter (deploy on any change / allow all
-branches).
-
-### `servers env` — environment variables
-
-```bash
-# List (production scope), or scope to a branch's preview env
-mcp-use servers env list --server <id>
-mcp-use servers env list --server <id> --branch feature-x
-
-# Add a variable. --env selects which environment TAGS it applies to;
-# --branch pins it to a branch's preview env (omit for production).
-mcp-use servers env add API_KEY=abc123 --server <id> --env production,preview
-mcp-use servers env add API_KEY=abc123 --server <id> --branch feature-x
-
-# Update / remove by KEY (resolved within the branch scope) or by UUID
-mcp-use servers env update API_KEY --server <id> --value newval --branch feature-x
-mcp-use servers env rm API_KEY --server <id> --branch feature-x
-```
-
-### `deployments restart`
-
-```bash
-# Restart reusing the deployment's branch, or target a different branch
-mcp-use deployments restart <deployment-id>
-mcp-use deployments restart <deployment-id> --branch feature-x
-```
-
-### Environment naming
-
-The platform models environments as `production`, `preview`, and
-`development` (the `--env` tag) plus an optional **branch** pin (`--branch`).
-There is no literal `test` environment. Common aliases map as:
-
-| You might say | Use |
-| --- | --- |
-| `prod` | `production` |
-| `dev` | `development` |
-| `staging` / per-branch | a `--branch <name>` preview (optionally tagged `preview`) |
-
-Note the two different `--env` meanings: on `deploy` it sets variable
-**values** (`KEY=VALUE`), while on `servers env` it selects the environment
-**tags** a variable applies to (`production,preview,development`).
-
----
-
-## 💡 Examples
-
-### Basic Development Workflow
-
-```bash
-# Create a new MCP app (using create-mcp-use-app)
-npx create-mcp-use-app my-mcp-server
-
-# Navigate to project
-cd my-mcp-server
-
-# Start development with auto-reload and inspector
-mcp-use dev
-
-# Browser automatically opens to http://localhost:3000/inspector
-```
-
-### Custom Port Configuration
-
-```bash
-# Development on port 8080
-mcp-use dev --port 8080
-
-# Production on port 8080
-mcp-use build
-mcp-use start --port 8080
-```
-
-### Working with Different Project Structures
-
-```bash
-# Specify custom project path
-mcp-use dev -p ./my-app
-mcp-use build -p ./my-app
-mcp-use start -p ./my-app
-
-# Development without auto-opening browser
-mcp-use dev --no-open
-```
-
-### CI/CD Pipeline Example
-
-```bash
-# In your CI/CD pipeline
-npm install
-npm run build  # Uses mcp-use build
-npm run start  # Uses mcp-use start
-
-# Or with PM2 for production
-npm run build
-pm2 start "mcp-use start" --name my-mcp-server
-```
-
----
-
-## 📁 Project Structure
-
-The CLI expects the following project structure:
-
-```
-my-mcp-app/
-├── package.json
-├── tsconfig.json
-├── src/
-│   └── index.ts         # Your MCP server entry point
-├── resources/           # UI widgets (React components)
-│   ├── todo-list.tsx    # Becomes /widgets/todo-list/index.html
-│   └── dashboard.tsx    # Becomes /widgets/dashboard/index.html
-└── dist/               # Build output
-    ├── index.js        # Compiled server
-    └── resources/
-        └── mcp-use/
-            └── widgets/
-                ├── todo-list/
-                │   ├── index.html
-                │   └── assets/
-                │       └── index-[hash].js
-                └── dashboard/
-                    ├── index.html
-                    └── assets/
-                        └── index-[hash].js
-```
-
----
-
-## 🎨 Creating UI Widgets
-
-UI widgets are React components that get compiled into standalone HTML pages. They can interact with your MCP server tools using the `useMcp` hook:
-
-```tsx
-// resources/task-manager.tsx
-import React, { useState, useEffect } from "react";
-import { useMcp } from "mcp-use/react";
-
-export default function TaskManager() {
-  const { callTool, status, error } = useMcp();
-  const [tasks, setTasks] = useState([]);
-  const [newTask, setNewTask] = useState("");
-
-  useEffect(() => {
-    loadTasks();
-  }, []);
-
-  const loadTasks = async () => {
-    const result = await callTool("list_tasks");
-    setTasks(result.tasks);
-  };
-
-  const addTask = async () => {
-    if (!newTask.trim()) return;
-
-    await callTool("create_task", {
-      title: newTask,
-      status: "pending",
-    });
-
-    setNewTask("");
-    await loadTasks();
-  };
-
-  if (status === "connecting") return <div>Connecting...</div>;
-  if (error) return <div>Error: {error.message}</div>;
-
-  return (
-    <div className="p-4">
-      <h1 className="text-2xl font-bold mb-4">Task Manager</h1>
-
-      <div className="flex gap-2 mb-4">
-        <input
-          type="text"
-          value={newTask}
-          onChange={(e) => setNewTask(e.target.value)}
-          placeholder="Add a new task..."
-          className="flex-1 p-2 border rounded"
-        />
-        <button
-          onClick={addTask}
-          className="px-4 py-2 bg-blue-500 text-white rounded"
-        >
-          Add Task
-        </button>
-      </div>
-
-      <ul className="space-y-2">
-        {tasks.map((task) => (
-          <li key={task.id} className="p-2 border rounded">
-            {task.title}
-          </li>
-        ))}
-      </ul>
-    </div>
-  );
-}
-```
-
-This widget will be available at `http://localhost:3000/widgets/task-manager` after building.
-
----
-
-## 🔧 Configuration
-
-### TypeScript Configuration
-
-Ensure your `tsconfig.json` includes:
-
-```json
-{
-  "compilerOptions": {
-    "target": "ES2020",
-    "module": "ESNext",
-    "jsx": "react-jsx",
-    "esModuleInterop": true,
-    "skipLibCheck": true,
-    "strict": true,
-    "outDir": "./dist",
-    "rootDir": "./src"
-  },
-  "include": ["src/**/*", "resources/**/*"]
-}
-```
-
-### Package.json Scripts
-
-Add these scripts for convenience:
-
-```json
-{
-  "scripts": {
-    "dev": "mcp-use dev",
-    "build": "mcp-use build",
-    "start": "mcp-use start",
-    "serve": "npm run build && npm run start"
-  }
-}
-```
-
----
-
-## 🚀 Advanced Usage
-
-### Environment Variables
-
-#### Development & Build
-
-```bash
-# Custom port via environment variable
-PORT=8080 mcp-use dev
-
-# Production build with custom output
-BUILD_DIR=./build mcp-use build
-
-# Custom MCP URL for widget asset paths
-MCP_URL=https://myserver.com mcp-use build
-```
-
-#### Deployment & Cloud
-
-For deploying to Manufact cloud, see the environment variables in this section for detailed configuration:
-
-```bash
-# Frontend URL (where /auth/cli page is)
-MCP_WEB_URL=https://mcp-use.com
-
-# Backend API URL (where /api/v1 endpoints are)
-MCP_API_URL=https://cloud.manufact.com
-
-# Example: Local development
-export MCP_WEB_URL=http://localhost:3000
-export MCP_API_URL=http://localhost:8000
-mcp-use login
-mcp-use deploy
-```
-
-See the [CLI reference docs](https://docs.mcp-use.com/typescript/server/cli-reference#environment-variables) for more examples and configuration options.
-
-### Docker Deployment
-
-```dockerfile
-# Dockerfile
-FROM node:20-alpine
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci --production
-COPY . .
-RUN npm run build
-EXPOSE 3000
-CMD ["npm", "start"]
-```
-
-### Serving Built Widgets
-
-You can serve the built widgets from any Hono app using `serveStatic`:
-
-```ts
-import { Hono } from "hono";
-import { serveStatic } from "hono/node-server/serve-static";
-
-const app = new Hono();
-
-// Serve MCP widgets
-app.use(
-  "/widgets/*",
-  serveStatic({ root: "./dist/resources/mcp-use/widgets" })
-);
-
-// Your other routes...
-```
-
----
-
-## 🐛 Troubleshooting
-
-### Common Issues
-
-**Port already in use:**
-
-```bash
-# Use a different port
-mcp-use dev --port 3001
-```
-
-**TypeScript compilation errors:**
-
-```bash
-# Check your tsconfig.json
-# Ensure all dependencies are installed
-npm install
-```
-
-**Widgets not loading:**
-
-- Ensure `.tsx` files are in the `resources/` directory
-- Check that React dependencies are installed
-- Verify the build output in `dist/resources/mcp-use/widgets/`
-
-**Inspector not opening:**
-
-```bash
-# Manually open http://localhost:3000/inspector
-# Or disable auto-open
-mcp-use dev --no-open
-```
-
----
-
-## 📚 Learn More
-
-- [mcp-use Documentation](https://github.com/mcp-use/mcp-use)
-- [Model Context Protocol](https://modelcontextprotocol.io)
-- [Creating MCP Servers](https://github.com/mcp-use/mcp-use/tree/main/libraries/typescript/packages/mcp-use#-mcp-server-framework)
-- [MCP Inspector Guide](https://github.com/mcp-use/mcp-use/tree/main/libraries/typescript/packages/inspector)
-
----
-
-## 📜 License
-
-MIT © [mcp-use](https://github.com/mcp-use)

package/dist/commands/auth.d.ts

@@ -1,34 +0,0 @@
-import type { OrgInfo } from "../utils/api.js";
-/**
- * Resolve an org identifier (slug, id, or case-insensitive name) against a list.
- * Returns null if no match.
- */
-export declare function resolveOrgFromOption(orgs: OrgInfo[], identifier: string): OrgInfo | null;
-/**
- * Prompt user to pick an organization from a numbered list.
- */
-export declare function promptOrgSelection(orgs: OrgInfo[], defaultOrgId?: string | null): Promise<OrgInfo | null>;
-/**
- * Login command using OAuth 2.0 Device Authorization Grant (RFC 8628).
- */
-export declare function loginCommand(options?: {
-    silent?: boolean;
-    apiKey?: string;
-    org?: string;
-    /**
-     * A pre-approved OAuth device code (RFC 8628). When provided, skip requesting
-     * a new code + opening a browser and poll the token endpoint directly. Used by
-     * the web onboarding flow, which creates and approves the code, then embeds it
-     * in the agent's prompt.
-     */
-    deviceCode?: string;
-}): Promise<void>;
-/**
- * Logout command - revokes API key and deletes config
- */
-export declare function logoutCommand(): Promise<void>;
-/**
- * Whoami command - shows current user info
- */
-export declare function whoamiCommand(): Promise<void>;
-//# sourceMappingURL=auth.d.ts.map