What kind of math does this MCP use?

The MCP uses queue theory to model lift line dynamics and predict wait times.

Can I use this with Claude or Cursor?

Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, Windsurf, and VS Code.

How does it handle lunch rushes?

The simulate_daily_operations capability specifically accounts for lunch rush impacts when forecasting daily capacity.

Do I need to host the MCP myself?

No, Vinkius hosts and manages the MCP for you. You just connect your client and start using the capabilities.

Can it help me choose new lift equipment?

Yes, the compare_lift_options capability allows you to compare different hardware configurations for specific crowd sizes.

How does the wait time calculation work?

The get_estimated_wait_time capability calculates wait times by analyzing the ratio of current queue length to the lift's hourly capacity, adjusted by the resort density factor.

Does the simulation account for peak demand?

Yes, simulate_daily_operations includes a parameter for lunch rush activity, which simulates the reduced throughput during high-demand periods.

Can I compare different lift types?

Yes, you can use compare_lift_options to evaluate multiple lift configurations against a target line length and current resort density.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Lift Capacity Timing Engine to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Predict lift line wait times and optimize daily resort throughput.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Lift Capacity Timing.

01
Calculate optimal cycle time
This capability finds the most efficient duration for a single lift cycle. It helps you balance speed and passenger loading.
02
Compare lift options
Use this to evaluate different lift configurations against specific crowd sizes. It helps you pick the best hardware setup for the job.
03
Get estimated wait time
This capability predicts how many minutes people will spend in a lift line. It uses current resort density to provide an estimate.
04
Simulate daily operations
This capability forecasts total daily capacity. It can account for specific events like lunch rushes to show how they impact throughput.

Real work

What teams actually run

Managing Peak Crowds

Use the MCP to predict wait times when resort density increases during holiday weekends.

Hardware Planning

Compare different lift options to see which configuration handles your expected crowd most efficiently.

Daily Capacity Planning

Run a daily operation simulation to forecast total passenger capacity including lunch rush slowdowns.

Operational Tuning

Calculate the best cycle time for a specific chair capacity to keep the lift running at peak efficiency.

One connector, every AI

Lift Capacity Timing works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Lift Capacity Timing to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

853ms average. Fast in production.

Lift Capacity Timing is checked daily against the live service.

Daily averagePeak 993ms

Oct 3Today

Fastest day: 702ms
Slowest day: 993ms
14-day trend: Stable-1%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Lift Capacity Timing, so you can see the experience inside your AI.

It does not authenticate your account with Lift Capacity Timing. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Lift Capacity Timing Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_BIVJxTViMRrpLaXjYQlJk7VqOODWYIkD1GKkxRxu/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Lift Capacity Timing capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "lift-capacity-timing-engine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_BIVJxTViMRrpLaXjYQlJk7VqOODWYIkD1GKkxRxu/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Lift Capacity Timing in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Lift Capacity Timing owners hand off.

This MCP is designed for professionals managing mountain operations and resort logistics.

01
Resort Operations Manager
Hands off crowd density data to the AI to get immediate wait time predictions.
02
Lift Maintenance Engineer
Uses the capability to model how different cycle times affect total daily throughput.
03
Logistics Planner
Runs daily simulations to prepare for peak periods like lunch rushes.

FAQ

Questions Lift Capacity Timing owners ask.

01
What kind of math does this MCP use?
The MCP uses queue theory to model lift line dynamics and predict wait times.
02
Can I use this with Claude or Cursor?
Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, Windsurf, and VS Code.
03
How does it handle lunch rushes?
The simulate_daily_operations capability specifically accounts for lunch rush impacts when forecasting daily capacity.
04
Do I need to host the MCP myself?
No, Vinkius hosts and manages the MCP for you. You just connect your client and start using the capabilities.
05
Can it help me choose new lift equipment?
Yes, the compare_lift_options capability allows you to compare different hardware configurations for specific crowd sizes.
06
How does the wait time calculation work?
The get_estimated_wait_time capability calculates wait times by analyzing the ratio of current queue length to the lift's hourly capacity, adjusted by the resort density factor.
07
Does the simulation account for peak demand?
Yes, simulate_daily_operations includes a parameter for lunch rush activity, which simulates the reduced throughput during high-demand periods.
08
Can I compare different lift types?
Yes, you can use compare_lift_options to evaluate multiple lift configurations against a target line length and current resort density.

Explore

More in Analytics

Connect Lift Capacity Timing to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-04

Calculate optimal cycle time

Compare lift options

Get estimated wait time

Simulate daily operations

What teams actually run

Managing Peak Crowds

Hardware Planning

Daily Capacity Planning

Operational Tuning

Building your own app? The connector is yours to use.

Lift Capacity Timing Connector

Claude Desktop

Resort Operations Manager

Lift Maintenance Engineer

Logistics Planner

What kind of math does this MCP use?

Can I use this with Claude or Cursor?

How does it handle lunch rushes?

Do I need to host the MCP myself?

Can it help me choose new lift equipment?

How does the wait time calculation work?

Does the simulation account for peak demand?

Can I compare different lift types?

Innovation Time-to-Market Engine AI Connector

Dog Park Capacity Planner AI Connector

Mosaic (Resource Planning & Workforce Management) AI Connector

Well Intervention Planning Engine AI Connector

Suggestions

Time-Series Seasonality Engine AI Connector

Daily Screen Time Planner AI Connector

Wine Cellar Capacity Planner AI Connector

QuestDB (Time-Series) AI Connector