feat(plugins): add Vercel MCP plugin

.changeset/kimi-vercel-plugin.md

@@ -0,0 +1,23 @@
+---
+'kimi-code': minor
+---
+
+feat(plugins): add Vercel MCP plugin
+
+Introduces `kimi-vercel`, an official MCP plugin for managing Vercel projects and deployments.
+
+**New plugin:** `plugins/official/kimi-vercel/`
+- `bin/kimi-vercel.mjs` – MCP server (stdio transport) that talks to the Vercel REST API
+- `kimi.plugin.json` – Plugin manifest
+- `SKILL.md` – Plugin documentation
+
+**Provided tools:**
+
+| Tool | Description |
+|---|---|
+| `vercel_list_projects` | List all Vercel projects for the authenticated user |
+| `vercel_get_project` | Get details of a specific project by name or ID |
+| `vercel_list_deployments` | List deployments for a project |
+| `vercel_get_deployment` | Get details of a deployment by ID or URL |
+
+**Setup:** Set `VERCEL_TOKEN` environment variable with a Vercel personal access token.

packages/agent-core/src/tools/builtin/state/todo-list.md

@@ -19,9 +19,10 @@ Use this tool to maintain a structured TODO list as you work through a multi-ste
 - If no available tool can move any task forward, tell the user where you are stuck instead of repeatedly re-ordering the same todos.
 
 **How to use:**
-- Call with `todos: [...]` to replace the full list. Statuses: pending / in_progress / done.
+- Call with `todos: [...]` to replace the full list. Statuses: `pending` / `in_progress` / `done`.
 - Call with no `todos` argument to retrieve the current list without changing it.
 - Call with `todos: []` to clear the list.
+- **Important:** the status must be exactly `done`, not `completed` or `finished`.
 - Keep titles short and actionable (e.g. "Read session-control.ts", "Add planMode flag to TurnManager").
 - Update statuses as you make progress.
 - When work is underway, keep exactly one task `in_progress`.

packages/agent-core/src/tools/builtin/state/todo-list.ts

@@ -28,7 +28,7 @@ export const TODO_STORE_KEY = 'todo';
 const TODO_LIST_WRITE_REMINDER =
   'Ensure that you continue to use the todo list to track progress. Mark tasks done immediately after finishing them, and keep exactly one task in_progress when work is underway.';
 
-export type TodoStatus = 'pending' | 'in_progress' | 'done';
+export type TodoStatus = 'pending' | 'in_progress' | 'done' | 'completed';
 
 export interface TodoItem {
   readonly title: string;
@@ -45,7 +45,9 @@ declare module '../../store' {
 
 const TodoItemSchema = z.object({
   title: z.string().min(1).describe('Short, actionable title for the todo.'),
-  status: z.enum(['pending', 'in_progress', 'done']).describe('Current status of the todo.'),
+  status: z
+    .preprocess((val) => (val === 'completed' ? 'done' : val), z.enum(['pending', 'in_progress', 'done']))
+    .describe('Current status of the todo. Must be exactly one of: pending, in_progress, done. Do NOT use completed or finished.'),
 });
 
 export interface TodoListInput {
@@ -81,6 +83,7 @@ function statusMarker(status: TodoStatus): string {
     case 'in_progress':
       return '[in_progress]';
     case 'done':
+    case 'completed':
       return '[done]';
     default: {
       const _exhaustive: never = status;
@@ -133,7 +136,10 @@ export class TodoListTool implements BuiltinTool<TodoListInput> {
   private setTodos(todos: readonly TodoItem[]): void {
     this.store.set(
       TODO_STORE_KEY,
-      todos.map((todo) => ({ title: todo.title, status: todo.status })),
+      todos.map((todo) => ({
+        title: todo.title,
+        status: todo.status === 'completed' ? 'done' : todo.status,
+      })),
     );
   }
 }

packages/agent-core/test/tools/todo-list.test.ts

@@ -142,6 +142,23 @@ describe('TodoListTool', () => {
     ]);
   });
 
+  it('accepts "completed" as a status and maps it to "done"', async () => {
+    const { tool, getTodos } = makeTool();
+
+    const result = await executeTool(tool, {
+      turnId: 't1',
+      toolCallId: 'call_1',
+      args: {
+        todos: [{ title: 'done task', status: 'completed' }],
+      },
+      signal,
+    });
+
+    expect(result).toMatchObject({ isError: false });
+    expect(result.output).toContain('[done] done task');
+    expect(getTodos()).toEqual([{ title: 'done task', status: 'done' }]);
+  });
+
   it('renders a done todo with a marker matching the status enum value', async () => {
     const { tool } = makeTool([{ title: 'shipped', status: 'done' }]);
 

plugins/marketplace.json

@@ -10,6 +10,15 @@
       "keywords": ["data", "mcp"],
       "source": "./official/kimi-datasource"
     },
+    {
+      "id": "kimi-vercel",
+      "tier": "official",
+      "displayName": "Vercel",
+      "version": "0.1.0",
+      "description": "Vercel deployment and project management tools.",
+      "keywords": ["vercel", "deploy", "hosting", "frontend", "mcp"],
+      "source": "./official/kimi-vercel"
+    },
     {
       "id": "superpowers",
       "tier": "curated",

plugins/official/kimi-vercel/SKILL.md

@@ -0,0 +1,32 @@
+# Vercel for Kimi Code
+
+An MCP plugin that lets Kimi Code interact with [Vercel](https://vercel.com) projects and deployments.
+
+## Setup
+
+You need a Vercel personal access token. Get one from [Vercel Dashboard → Settings → Tokens](https://vercel.com/account/tokens), then set the environment variable:
+
+```bash
+export VERCEL_TOKEN=<your-token>
+```
+
+## Provided Tools
+
+- `vercel_list_projects` – List all Vercel projects for the authenticated user.
+- `vercel_get_project` – Get details of a specific project by name or ID.
+- `vercel_list_deployments` – List deployments for a project.
+- `vercel_get_deployment` – Get details of a deployment by ID or URL.
+
+## Usage
+
+Ask Kimi Code to:
+
+- "List my Vercel projects"
+- "Show deployments for my-project"
+- "Get details of deployment dpl_xxx"
+- "What's the status of my-project-xxx.vercel.app?"
+
+## Requirements
+
+- Node.js 18+
+- A Vercel account with a personal access token