Bring Resource Planning
to Claude Desktop
Learn how to connect Dime.Scheduler to Claude Desktop and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Dime.Scheduler MCP Server?
Connect your Dime.Scheduler account to any AI agent and take full control of your resource orchestration and project scheduling workflows through natural conversation.
What you can do
- Job Orchestration — List and manage planning jobs programmatically, retrieving detailed metadata about parent entities and project requirements
- Task Lifecycle Management — Access and track individual units of work (tasks) that need to be scheduled across your resources in real-time
- Appointment Monitoring — List and inspect all appointments on the graphical planning board to maintain a high-fidelity overview of scheduled activities
- Resource Optimization — Retrieve complete directories of planable resources (people, equipment, tools) to understand team availability and capacity
- Category & Marker Intelligence — Access planning categories and time markers directly through your agent to keep your scheduling board perfectly organized
How it works
1. Subscribe to this server
2. Retrieve your X-API-KEY from your Dime.Scheduler instance settings
3. Start managing your resource planning from Claude, Cursor, or any MCP client
No more manual toggling between complex planning boards or digging through task lists. Your AI acts as your dedicated resource coordinator and scheduling strategist.
Who is this for?
- Project Managers — instantly retrieve job statuses and check task planning across multiple resources using natural language commands
- Resource Coordinators — monitor team availability and appointment loads without leaving your communication tools
- Operations Leads — track scheduled equipment and maintain board organization through simple AI queries
Built-in capabilities (7)
Get job details
List all appointments on the planning board
List all planning categories
Scheduler. List all planning jobs
List all planable resources
List all planning tasks
List available time markers
Why Claude Desktop?
Claude Desktop is the definitive way to connect Dime.Scheduler to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 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
Dime.Scheduler in Claude Desktop
Dime.Scheduler and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dime.Scheduler 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 Dime.Scheduler in Claude Desktop
The Dime.Scheduler 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 7 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
Dime.Scheduler for Claude Desktop
Every tool call from Claude Desktop to the Dime.Scheduler 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 Dime.Scheduler API Key?
Log in to your Dime.Scheduler instance and navigate to Settings > API to generate or copy your unique X-API-KEY.
What is the difference between a job and a task?
A job is the parent project or order, while a task is the specific unit of work that is scheduled on the planning board.
Can I see real-time team availability?
Yes! The list_resources and list_appointments tools allow your agent to identify open slots and currently scheduled work.
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.