Bring Job Dispatching
to Claude Desktop
Learn how to connect Giddyup to Claude Desktop and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Giddyup MCP Server?
Connect your Giddyup account to any AI agent and take full control of your roofing and construction workflows through natural conversation.
What you can do
- Lead Orchestration — List and manage potential customer records programmatically, including contact info and acquisition metadata
- Job Lifecycle — Monitor active roofing and construction projects and retrieve detailed technical metadata and status in real-time
- Customer Intelligence — Access your complete customer directory and retrieve detailed profiles to streamline field coordination
- Operational Visibility — Get a comprehensive overview of your construction pipeline using natural language commands
- Field Coordination — Access granular details for specific jobs to ensure your team has the latest project requirements
How it works
1. Subscribe to this server
2. Retrieve your API Authentication Key from your Giddyup settings (Custom Application Integration)
3. Start managing your construction CRM from Claude, Cursor, or any MCP client
No more manual toggling between project spreadsheets. Your AI acts as your dedicated construction operations coordinator.
Who is this for?
- Project Managers — instantly check job statuses and retrieve customer requirements using natural language
- Sales Teams — manage lead queues and update contact details without leaving your workspace
- Operations Leaders — monitor the entire construction pipeline and identify bottlenecks through automated queries
Built-in capabilities (13)
Verify connectivity
Create a job
Create a lead
Get customer details
Get job details
Get lead details
List customers
List invoices
List jobs
List leads
List technicians
Update a job
Update a lead
Why Claude Desktop?
Claude Desktop is the definitive way to connect Giddyup to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 13 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Giddyup in Claude Desktop
Giddyup and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Giddyup to Claude Desktop 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 Giddyup in Claude Desktop
The Giddyup 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 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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
Giddyup for Claude Desktop
Every tool call from Claude Desktop to the Giddyup 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 Giddyup API Key?
Log in to your Giddyup account and navigate to the Custom Application Integration settings to generate your unique authentication key.
Can I list specific roofing jobs by ID?
Yes! Use the get_job tool and provide the unique job identifier to retrieve detailed technical data and status updates.
Does this integration support customer profile retrieval?
Absolutely. The list_customers tool allows you to retrieve your entire client directory for better field coordination.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.