Dime.Scheduler MCP. Coordinate field teams and resource scheduling via conversation
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Dime.Scheduler connects your scheduling board logic to your AI agent. You manage field service teams, track resources, and check job statuses using natural conversation instead of clicking through complex ERP interfaces.
It lets you pull resource availability and appointment details instantly.
What your AI agents can do
Get job
Fetches specific details and metadata for a single planning job.
List appointments
Retrieves all scheduled appointments visible on the planning board.
List categories
Lists predefined organizational categories used for organizing planning data.
Retrieves specific details about a single job instance.
Lists all scheduled events and appointments on the planning board, often filtered by date or resource.
Gathers a directory of every planable resource, including people, tools, and equipment, to assess team capacity.
Provides lists of all individual tasks that need to be scheduled or managed across your site's resources.
Retrieves a high-level list of every planning job currently active in the system.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Dime.Scheduler MCP with 7 Tools
These tools let your agent read all the core data from your scheduling system: jobs, appointments, resources, and tasks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Dime.Scheduler on Vinkius019dd0e0get job
Fetches specific details and metadata for a single planning job.
019dd0e0list appointments
Retrieves all scheduled appointments visible on the planning board.
019dd0e0list categories
Lists predefined organizational categories used for organizing planning data.
019dd0e0list jobs
Provides a complete list of all active planning jobs in the system.
019dd0e0list resources
Retrieves a directory listing of every resource that can be scheduled, including people and equipment.
019dd0e0list tasks
Lists all individual tasks assigned to resources needing scheduling attention.
019dd0e0list time markers
Provides a list of specific time markers or date boundaries for planning views.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Dime.Scheduler, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Dime.Scheduler. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
The old way of planning service calls
Today, scheduling a team involves juggling at least three systems. You start by pulling the job list from your ERP dashboard. Then you open a separate calendar view to see appointments and manually cross-reference that with a resource tracker sheet to check for equipment conflicts. It’s clicking through five different tabs just to plan one day.
With this MCP, you tell your agent what needs scheduling. The tool handles the complex data pulling behind the scenes, synthesizing job details, available resources, and open appointments into a single, conversational answer. You get instant answers without leaving your chat.
Using list_jobs and list_resources
Manually figuring out if the correct personnel are available requires running separate reports on staffing directories, then cross-referencing those names against job assignments to see which resources are actually allocated. This is slow, error-prone, and takes time away from actual problem solving.
Now, you ask your agent to combine `list_jobs` with `list_resources`. It immediately shows you the gap: 'Job #1024 needs a Level 3 Tech, but only two are available.' The system gives you clear, actionable gaps.
What you can do with this MCP connector
Need to coordinate field staff or project crews? This MCP brings the full power of Dime.Scheduler into your AI agent. You can manage entire scheduling workflows just by talking to your client. Instead of jumping between planning boards, task lists, and team directories, you ask your agent for exactly what you need—from checking which resources are available today to listing all appointments scheduled next week.
For instance, if you have a complex project that requires multiple steps across different teams, you can build those automations by chaining this MCP with other services. This means your scheduling data talks directly to your messaging or billing systems, running through the secure architecture of Vinkius. You don't worry about where credentials sit; they pass through a zero-trust proxy and never stay on disk.
The agent acts as your dedicated operations coordinator. It handles job status checks, tracks individual units of work, and keeps an eye on every scheduled activity without you ever having to manually toggle between complex planning views or dive into separate task management screens.
019dd0e0-946a-7137-a928-e807c7c9f938 
How Dime.Scheduler MCP Works
- 1 Subscribe to this MCP and retrieve your X-API-KEY from your Dime.Scheduler settings.
- 2 Connect your AI agent to the Vinkius platform using that key.
- 3 Tell your agent what you need—for example, 'List all resources available next Tuesday'—and it executes the call.
The bottom line is: your agent talks directly to Dime.Scheduler and pulls live scheduling data into your chat window.
Who Is Dime.Scheduler MCP For?
This MCP helps Project Managers, Operations Leads, and Field Service Coordinators who are tired of manual dashboard checks. If you spend time jumping between an ERP system, a task board, and email to figure out team capacity, this is for you.
Uses the MCP to monitor overall team availability and check if equipment or personnel are overbooked across multiple sites without leaving their chat interface.
Retrieves job statuses and tracks task progress, allowing them to report on project health using natural language commands instead of running complex reports.
Checks the entire appointment schedule for multiple days at once, ensuring no resource is accidentally double-booked before sending out manifests.
What Changes When You Connect
- Stop manually checking job status across multiple tabs. Use the agent to instantly fetch details for any single job using
get_job. - Maintain a high-fidelity overview of operations by calling
list_appointments, which pulls every scheduled event from your planning board in one go. - Determine true team capacity immediately. The
list_resourcestool gives you the full directory, showing who's available and what tools are ready to deploy. - Keep your scheduling data perfectly organized by accessing planning categories through
list_categories, ensuring every query is scoped correctly. - Manage project progress at a high level. Use
list_jobsto see all parent entities active in the system, giving you an immediate status report.
Real-World Use Cases
Identifying Resource Gaps
A coordinator needs to schedule four new installations next week. Instead of opening the resource directory and manually checking availability for each crew member and van, they ask their agent to combine list_resources with list_tasks. The agent instantly flags which resources are overbooked or missing required equipment.
Daily Operations Briefing
The operations lead needs a quick update on the day's work. They ask the agent to run list_appointments for today and then follow up by calling get_job on any jobs that were marked as 'delayed', getting all necessary context in one chat session.
Project Scope Check
A project manager is starting a new phase. They need to know the overall scope of work. They ask for list_jobs first, then use the resulting job IDs to run list_tasks, ensuring every required step has an owner and a deadline.
Planning Board Audit
A maintenance engineer needs to audit how planning is structured. They ask the agent for all available time markers using list_time_markers and then review the overall structure by calling list_categories, ensuring data integrity across the board.
The Tradeoffs
Treating it like a simple task list.
Trying to use this MCP just for basic to-do lists. You only ask list_tasks, but you don't know which resource is actually assigned or if the equipment is available.
→
Always pair list_tasks with list_resources. This combination shows who needs to do what, and whether they have the necessary tools to complete it.
Asking for a 'full board view' without context.
Saying, 'Show me everything on the board.' The agent can't guess your focus, so you get a massive dump of data that is hard to read and useless.
→
Be specific. Instead of general requests, use list_appointments combined with date parameters, or narrow down scope by calling list_jobs first.
Relying on manual copies/pastes between systems.
Copying a job ID from an email into the agent's prompt. This is slow and introduces copy-paste errors every time.
→
Let your agent run list_jobs first; it gives you structured, clean data you can reference directly in conversation.
When It Fits, When It Doesn't
Use this MCP if your workflow involves coordinating physical work or field service across multiple resources, locations, and timeframes. The core strength is linking the scheduling board's complex logic (jobs, appointments, tasks) into a conversational flow.
Don't use it if you only need to manage simple data records that don't relate to resource availability; for example, if you are just tracking client feedback or writing internal memos. In those cases, a standard messaging MCP is better suited. If your primary goal is creating new scheduled jobs (i.e., updating status), remember that these tools are read-only endpoints—you need to pair this with an explicit write/update tool for full automation.
Common Questions About Dime.Scheduler MCP
How do I check job status using list_jobs and get_job? +
You first run list_jobs to see all parent entities. Then, if the agent identifies a specific ID you need more details on, it automatically calls get_job. This two-step process lets you narrow down your search quickly.
Can I find out what equipment is available? (list_resources) +
Yes. Running list_resources provides a complete directory of planable assets, including tools and vehicles. This confirms if the required gear for an appointment or job is in stock.
What are appointments listed with list_appointments? +
This tool pulls all scheduled events visible on your planning board. It's your quick view into today’s schedule, showing who and what is booked for any given time frame.
Do I need to use list_tasks before listing appointments? +
No. While tasks define the work, list_appointments gives you the final scheduled view. Use both tools together if you want to know which specific units of work (tasks) are tied to an upcoming appointment.
What are planning categories and how do I see them using list_categories? +
The function provides a complete directory of organizational buckets. These help you categorize and filter job data, allowing your agent to show you only the specific types of work or projects you care about.
How do I check available time slots for planning using list_time_markers? +
You get a list of predefined temporal markers, such as 'Morning Shift' or 'Emergency Window.' This ensures your scheduling is organized by official time segments rather than just dates.
If I use list_jobs, how does the data help me understand project scope? +
The output of listing jobs includes detailed metadata about parent entities and overall project requirements. This lets your agent grasp the full context of a job before you even check individual tasks.
How can I filter for specific resource types using list_resources? +
The results from listing resources provide clear classifications, like 'Person' or 'Tool.' You pass these filters to your agent so it only checks availability and capacity for the exact equipment categories you need.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.