Bring Resource Planning
to Cursor
Learn how to connect Dime.Scheduler to Cursor 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 Cursor?
Cursor's Agent mode turns Dime.Scheduler into an in-editor superpower. Ask Cursor to generate code using live data from Dime.Scheduler and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Dime.Scheduler in Cursor
Dime.Scheduler and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dime.Scheduler to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.