Files
Gabriel Gordon-Hall b9c961a666 All changes have been completed successfully. Let me provide a summary of what was fixed: (#2068)
## Summary

I've fixed the MCP tool description parameter mismatches reported in Issue #1942.

### Changes Made

**1. `crates/server/src/mcp/task_server.rs`** - Fixed 4 issues:

- **`update_task`** (line 753): Removed incorrect `project_id` requirement from description
- **`delete_task`** (line 802): Removed incorrect `project_id` requirement from description
- **`get_task`** (line 820): Removed incorrect `project_id` requirement from description
- **`StartWorkspaceSessionRequest.executor`** (line 223): Added missing executors (`AMP`, `QWEN_CODE`, `COPILOT`, `DROID`) to the description

**2. `docs/integrations/vibe-kanban-mcp-server.mdx`** - Updated documentation:

- Added `list_repos` tool to the Project Operations table
- Added new "Context" section with `get_context` tool
- Renamed `start_task_attempt` to `start_workspace_session` (the actual tool name)
- Updated `start_workspace_session` parameters to show `repos` array instead of single `base_branch`
- Updated example JSON to demonstrate correct parameter format

The cargo check passes, confirming all Rust changes compile correctly.
2026-01-15 17:59:12 +00:00
..
2025-09-16 21:46:57 +01:00
2025-09-16 21:46:57 +01:00
2025-09-16 21:46:57 +01:00

Mintlify Starter Kit

Mintlify Quickstart Guide

Development

Install the Mintlify CLI to preview your documentation changes locally. To install, use the following command:

npm i -g mint

Run the following command at the root of your documentation, where your docs.json is located:

mint dev

View your local preview at http://localhost:3000.

Publishing changes

Install our GitHub app from your dashboard to propagate changes from your repo to your deployment. Changes are deployed to production automatically after pushing to the default branch.

Need help?

Troubleshooting

  • If your dev environment isn't running: Run mint update to ensure you have the most recent version of the CLI.
  • If a page loads as a 404: Make sure you are running in a folder with a valid docs.json.

Resources