Pullsheet Diagnostics
Wire an agent into AI-powered elevator, escalator, and vertical-transport diagnostics when you are building field-service or maintenance software for that industry.
Overview
Pullsheet Diagnostics is an MCP server for the Build phase that gives coding agents AI-powered diagnostic access for elevator, escalator, and vertical transportation equipment.
What is this MCP server?
- Remote MCP server at a Cloudflare Workers endpoint (streamable-http) for agent clients
- AI-powered diagnostics aimed at elevator, escalator, and vertical transportation equipment
- Version 1.0.0 package with GitHub source under joshuaworth/pullsheetintent (workers/mcp-server)
- Fits agent workflows that need structured diagnostic context instead of generic web search
- Niche vertical focus: lifts and escalators rather than general-purpose developer APIs
- MCP server version 1.0.0
- Single streamable-http remote endpoint on Cloudflare Workers
- Package id io.github.joshuaworth/pullsheet-diagnostics with GitHub source in workers/mcp-server
What problem does it solve?
Building agent-assisted maintenance tools for lifts and escalators is painful when your assistant cannot reach structured, equipment-specific diagnostic logic and you end up pasting manuals or guessing fault codes.
Who is it for?
Indie or solo builders shipping technician copilots, dispatch tools, or internal apps for elevator and escalator maintenance who already use MCP in Claude Code or Cursor.
Skip if: General web SaaS, unrelated DevOps monitoring, or builders with no vertical-transport product angle who only need generic error tracking.
What do I get? / Deliverables
After you add the Pullsheet MCP remote to your agent, implementation chats can pull vertical-transport diagnostics into the same workflow where you scaffold APIs, UI, and field-service features.
- Agent-accessible Pullsheet diagnostic calls over the hosted MCP remote
- Faster integration of equipment-specific diagnostic flows into your maintenance app or copilot
- A validated MCP connection you can reference while building backend and UI around technician workflows
Recommended MCP Servers
Journey fit
Pullsheet is consumed as a remote MCP integration while you are building product capabilities, not as a launch or growth tactic on its own. The server exposes diagnostics over streamable HTTP so Claude Code, Cursor, or similar agents can call Pullsheet during implementation and agent-tooling setup.
How it compares
A hosted vertical-transport diagnostics MCP integration, not a reusable Claude skill or a full CMMS product.
Common Questions / FAQ
Who is Pullsheet Diagnostics for?
It is for developers and solo builders creating AI-assisted software for elevator, escalator, and vertical-transport maintenance, where agents need real diagnostic context during build and integration work.
When should I use Pullsheet Diagnostics?
Use it during Build while you connect agent tooling to your maintenance app prototype, especially when diagnosing equipment behavior is core to the user experience you are shipping.
How do I add Pullsheet Diagnostics to my agent?
Register the published streamable-http MCP remote URL from the server manifest in your MCP client configuration (for example Claude Code or Cursor), then verify the connection from an agent session before coding against it.