Bring Resource Planning
to VS Code Copilot
Learn how to connect Dime.Scheduler to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Dime.Scheduler data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Dime.Scheduler in VS Code Copilot
Dime.Scheduler and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dime.Scheduler to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.