Bring Task Management
to Claude Desktop
Learn how to connect Worksection to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Worksection MCP Server?
Connect your Worksection account to any AI agent to automate your project management and team productivity workflows. Worksection provides a comprehensive set of tools for managing tasks, tracking time, and monitoring real-time project activities through natural conversation.
What you can do
- Project Lifecycle Management — List all projects, create new ones, and manage tasks across your entire organization programmatically.
- Time Tracking & Timers — Monitor active timers for team members and stop time trackers directly from the AI interface.
- Activity Monitoring — Retrieve a detailed event log of recent account activities to stay updated on project changes and completions.
- Stakeholder Collaboration — Access task comments, project members, and attached files to maintain a clear overview of team collaboration.
- Hierarchical Oversight — Navigate project folders and task sub-trees using simple natural language commands.
How it works
1. Subscribe to this server
2. Enter your Worksection Account Name (subdomain) and Administrative API Key
3. Start managing your projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — automate task status reports and monitor team timers without manual oversight.
- Operations Leads — track real-time activity across multiple projects and folders via natural conversation.
- Distributed Teams — streamline task coordination and ensure all project stakeholders are aligned programmatically.
Built-in capabilities (12)
Finish a task
Add new task
Get project info
Get full task info
Check running timers
List company users
List team on project
List tasks in project
List workspace projects
Get event log
Restore a task
Finish time tracking
Why Claude Desktop?
Claude Desktop is the definitive way to connect Worksection to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Worksection in Claude Desktop
Worksection and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Worksection to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Worksection in Claude Desktop
The Worksection MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Worksection for Claude Desktop
Every tool call from Claude Desktop to the Worksection MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Worksection Administrative API Key?
Log in to Worksection, navigate to Account Settings > API, and you will find your Administrative API Key listed there along with your account subdomain.
Can the AI stop active timers for team members?
Yes! Use the stop_timer tool and provide the task identifier (page) to stop any active time tracking for that specific task in your account.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.