Whagons MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Whagons MCPShow my assigned tasks across all workspaces"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Whagons MCP
Read Whagons tasks and workspace information from an MCP client. Each person supplies their own Whagons API key and tenant. The server exposes six read-only tools. It does not create, change, approve, or delete tasks.
Preview release. Protocol and adapter tests pass. All six read-only API checks passed against production on September 5, 2026 using the correct tenant credential. An earlier 401 came from using another tenant's key, not a backend failure. Desktop-client installation and end-to-end client verification remain pending. This package has not been accepted into the ChatGPT or Claude public directories.
Install in Claude Desktop
Download whagons-0.1.0.mcpb from the releases page. Open it in Claude Desktop using its local extension installer. Supply your API key and tenant in the extension settings. Requires a client that supports MCP bundles and a Node.js 22 or newer runtime. Desktop installation on macOS and Windows is not yet verified.
Create a Whagons API key with ext:read scope in Settings > Integrations > API Keys. Your account's permissions still apply. Keep the key in the client's sensitive configuration field. Never put it in a prompt, source file, or GitHub issue.
Related MCP server: Azure DevOps MCP Server
Install as a Claude plugin
In Claude Code, add this public marketplace and install the plugin:
/plugin marketplace add Desarso/whagons-mcp
/plugin install whagons@whagonsClaude prompts for your API key and tenant when you enable the plugin. Requires Node.js 22 or newer. The bundled server has no runtime npm-install step. Cowork compatibility is not yet verified.
Other MCP clients
Clone the repository or extract the source archive. Configure a stdio MCP server with command node, the absolute path to dist/server.mjs as its argument, and these environment variables supplied through your client's credential settings:
Variable | Purpose |
| Your read-enabled Whagons API key |
| The tenant associated with that key |
| Optional operator override; defaults to |
Only change the API URL to an HTTPS service you trust. The configured service receives your key. Redirects are refused. The Codex manifest uses a plugin-relative working directory and inherited environment variables. Set them in your client environment before enabling it.
ChatGPT
The public ChatGPT connector needs a hosted MCP endpoint and per-user authentication. This preview contains a local stdio server. It does not provide a hosted OAuth service, and installing the Codex package does not publish a ChatGPT connector. OpenAI publisher verification and directory review are separate steps.
Tools
Tool | Purpose |
| List accessible workspaces |
| Search tasks; filter by workspace, status, priority, or your assignments |
| Read a task by its canonical ID |
| Read task comments |
| Resolve status names |
| Resolve priority names |
Collection tools default to 25 results and accept up to 100. Pass a returned nextCursor into the next call. Task text and comments are user-authored data and may contain untrusted instructions.
Backend changes
Whagons is changing its Gonvex backend. src/adapter.mjs is the only backend-specific module. It calls the supported external API and sends tenant routing in a header at that boundary. It does not define application Queries, Reducers, Actions, or tenant arguments. Keep the six public tool contracts stable and reverify the adapter against the intended production release after staging ships.
Develop and test
npm ci --ignore-scripts
npm run build
npm test
claude plugin validate .The test suite uses synthetic data and a real MCP stdio client. It checks tool discovery and calls, rejection of tenant overrides and write tools, credential-safe failures, response limits, and standalone bundle startup. It does not prove backend authorization or desktop-client compatibility.
Read PRIVACY.md for this package's data flow. For support, open an issue without keys or private task data. Published by Gabriel Malek using a personal account. The Whagons logo is the existing application mark.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
- TimequipOAuthcom.timequip
Manage Timequip projects, tasks, comments, members, and dashboards through MCP.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
BridgeApp workspace over MCP: tasks, chats, threads, pages, and projects.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceIntegrates with Google Tasks to enable searching, listing, creating, updating, and deleting tasks through MCP tools. It provides a comprehensive interface for managing task lists and individual task details via the Google Tasks API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading and updating Azure DevOps work items, comments, metadata, and relations from an MCP-compatible client.517 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools for TaskMarket, enabling users to list open tasks, inspect task details, and prepare delegation drafts with approval fingerprints.MIT
- FlicenseNot gradedqualityBmaintenanceEnables managing tasks through a simple task tracker with REST API and MCP tools for listing, creating, updating, assigning, and deleting tasks.-