Bring Job Dispatching
to Cursor
Learn how to connect Giddyup to Cursor 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 Cursor?
Cursor's Agent mode turns Giddyup into an in-editor superpower. Ask Cursor to generate code using live data from Giddyup and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Giddyup in Cursor
Giddyup and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Giddyup to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.