GorillaDesk
GorillaDesk is field service management software for pest control and other service businesses, covering customers, jobs, estimates, invoices, payments, and related operations.
Verdict
Common use cases
- Pull invoice history during support calls
- Check estimate status before follow-up
- Log customer conversation notes instantly
- Review job documents without switching apps
- Create customer records from chat intake
Integration
- Vendor
- GorillaDesk
- Category
- crm
- Auth
- API_KEY
- Tools
- 13
- Composio slug
gorilladesk
Tools
- Create Customer
Create a GorillaDesk customer together with the required primary service location. This is a permanent side effect: GorillaDesk exposes no customer-delete API, so the created business record cannot be removed with this toolkit.
- Create Customer Note
Permanently add a text note to a GorillaDesk customer and optionally notify users. The API cannot remove a created note. This action excludes attachments and must not be retried after an ambiguous result because a retry can create a duplica
- Get Company
Return the company profile selected by the connected GorillaDesk API key, including contact, address, timezone, and office-hours details.
- Get Credits
Retrieve one customer credit by ID, or list credits, optionally filtering to one customer.
- Get Customers
Retrieve one customer by ID, or search and page through customers using status, state, account number, timestamps, expansions, and sorting.
- Get Documents
Retrieve one document by ID, or search documents by customer, job, state, status, creation time, keyword, and sorting.
- Get Estimates
Retrieve one estimate by ID, or search estimates by customer, job, state, status, signature status, date, keyword, expansions, and sorting.
- Get Invoices
Retrieve one invoice by ID, or search invoices by customer, job, state, payment/signature status, date, keyword, expansions, and sorting.
- Get Jobs
Retrieve one job by ID, or search jobs by customer, state, date, keyword, expansions, and sorting.
- Get Payments
Retrieve one payment by ID, or search payments by customer, invoice, status, date, expansions, and sorting.
- Get Services
Retrieve one GorillaDesk service by ID, or list configured services with sorting and offset pagination.
- Get Users
Retrieve one GorillaDesk user by ID, or list the company's users when no ID is supplied.
- List Phone Types
List the configured customer phone-type definitions, including IDs, names, default flags, and states.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > MCP Servers. 2. Click 'Add MCP Server' and select GorillaDesk from the catalog. 3. Log in to your GorillaDesk account, go to Settings > API, and generate a new API key with read and write permissions. 4. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will verify the key by fetching your company profile; you'll see a green checkmark when authentication succeeds. 6. Open any Project and type '@GorillaDesk get customers' to test the connection — the MCP should return a list of your customer records. 7. To create a customer, use '@GorillaDesk create customer' followed by name and service address; remember this action is permanent and cannot be undone through the API.
What teammates see: by default, memories from GorillaDesk are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Customer Account Summary
@GorillaDesk search for customer 'Smith Residence' and show me their account status, primary service location, and any open invoices or estimates
Overdue Invoice Report
@GorillaDesk get all invoices with payment status unpaid, filter to those past due date, and sort by oldest first
Log Support Call Note
@GorillaDesk create a note on customer ID 12345 saying 'Called about missed service on 4/15 — rescheduled for 4/22, waived trip fee'
Estimate Follow-Up List
@GorillaDesk search estimates with signature status unsigned, created more than 7 days ago, and show customer name and estimate total
New Customer Intake
@GorillaDesk create customer 'Johnson Lawn Care' with service location 456 Oak Street, Austin TX 78701, and tag as residential
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@GorillaDesk show me all unpaid invoices from the last 30 days, grouped by customer, and highlight any over $500
Found 47 unpaid invoices from the past 30 days across 23 customers. Top balances: Riverside Property Management ($2,340 across 3 invoices), Martinez Landscaping ($1,890, 2 invoices), Green Valley HOA ($1,450, 1 invoice). 8 invoices exceed $500. The largest single invoice is #INV-8821 for $1,200 to Riverside, issued 12 days ago. 15 invoices are under 7 days old; 32 are 8+ days outstanding. This data reflects your GorillaDesk account state as of this query.
This read-heavy example demonstrates invoice search with date and status filters, plus AI synthesis to surface high-value accounts. Requires API key with invoice read scope. Results depend on your live customer and billing data; the MCP cannot modify invoice records through this query.
@GorillaDesk create a new customer named Oakwood Estates with service address 450 Maple Drive, Austin TX 78701, phone 512-555-0199, and tag them as commercial
Customer created successfully. Oakwood Estates is now in your GorillaDesk account with ID CUST-9847. Primary service location set to 450 Maple Drive, Austin, TX 78701. Contact phone: 512-555-0199. Customer type: Commercial. You can now create jobs, estimates, and invoices for this account. Note: GorillaDesk does not expose a customer-delete API, so this record is permanent unless removed manually through the web interface.
This write example shows customer creation with required service location. The side effect is permanent—the MCP cannot delete customers via API, so test carefully in production environments. Requires API key with customer write scope. The commercial tag and contact details are stored immediately.
@GorillaDesk pull the last 20 estimates marked as accepted, then draft a brief sales summary showing total value, average ticket size, and most common service types
Retrieved 20 accepted estimates from the past 45 days, totaling $34,680 in committed work. Average estimate value: $1,734. Most common services: Lawn Maintenance (9 estimates, $12,400), Tree Removal (5 estimates, $11,200), Irrigation Repair (4 estimates, $6,900), Pest Control (2 estimates, $4,180). Highest single estimate: $4,200 for commercial tree removal at Riverside Property Management. 14 estimates were signed within 48 hours of issue; 6 took 5+ days. This snapshot reflects your recent sales velocity and service mix.
This synthesis example pairs estimate retrieval with AI analysis to surface sales trends. Useful for weekly pipeline reviews or service-mix planning. Requires API key with estimate read scope. The MCP fetches raw estimate data; the AI performs grouping and math. Results vary by your estimate history and date range.
Use-case deep-dives
When GorillaDesk wins for lawn care and pest control teams
A 6-person lawn care company runs daily routes and needs to pull customer histories, check open invoices, and log service notes from Slack without opening GorillaDesk on mobile. The MCP handles this well: the Get Customers and Get Invoices tools let dispatchers answer "did we bill the Smith property last month?" in seconds, and Create Customer Note logs completion details or damage reports immediately. The 13-tool scope covers the full service lifecycle—estimates, jobs, documents, credits—so your team can triage most questions without context-switching. The threshold: if you're creating more than 20 customers a week, remember the API has no delete endpoint, so test customer creation in a sandbox first. For field service teams under 15 people who live in Slack or a shared workspace, this MCP cuts GorillaDesk lookups from 8 clicks to one prompt.
Fast invoice and payment status checks for support reps
A 3-person support team at a pest control franchise fields 40+ billing calls a day. Customers ask "did my payment go through?" or "can you email my invoice again?" and reps currently log into GorillaDesk, search by name, and click through to invoices. The MCP collapses that into a single query: Get Invoices filters by customer, payment status, and date, returning the answer in under 3 seconds. Get Documents pulls signed estimates or service agreements if the customer disputes a charge. The API key scopes to one company profile, so multi-location franchises need separate keys per territory. If your support volume is under 100 tickets a week and most questions are "where's my invoice" or "what's my balance," this MCP pays for itself in the first week. For higher-touch support that needs to modify invoices or void payments, you'll still need the GorillaDesk UI.
When to use (and not use) GorillaDesk for CRM intake
A 4-person HVAC startup wants to create GorillaDesk customers from inbound form submissions and immediately log the intake call notes. The MCP's Create Customer tool works, but there's a critical constraint: GorillaDesk exposes no delete API, so every test run or duplicate submission becomes a permanent customer record. If your intake process is still messy—high duplicate rates, frequent data corrections, or you're experimenting with lead qualification—don't automate customer creation yet. Clean up your funnel first, then use the MCP to batch-create vetted leads with Create Customer and tag them with Create Customer Note. The Get Credits and Get Estimates tools let you track the full sales cycle once a customer is in. For teams doing under 10 new customers a week with a stable intake process, this MCP removes the manual GorillaDesk data-entry step entirely.
Frequently asked
What can Switchy do with GorillaDesk MCP?
Switchy can read your GorillaDesk customers, invoices, estimates, and documents, plus create new customers and add notes to existing records. The MCP surfaces 13 tools covering the core CRM workflows — customer lookup, job tracking, billing status — but cannot delete customers or remove notes once created. Think of it as read-heavy access with selective write permissions for customer onboarding and note-taking.
Do I need admin access to connect GorillaDesk?
You need an API key from your GorillaDesk account settings. GorillaDesk doesn't publish granular permission requirements in their API docs, but generating an API key typically requires admin or owner-level access. The key is scoped to your entire company profile — there's no per-user or per-module restriction — so treat it like a master credential and store it in Switchy's encrypted vault.
Can the MCP delete customers or invoices?
No. GorillaDesk's API doesn't expose customer deletion, and the MCP inherits that constraint. Once you create a customer via Switchy, the record is permanent in GorillaDesk. The same applies to notes — you can add them but not remove them. Invoice and estimate deletion also aren't supported. If you need to clean up test data, you'll have to archive or mark records inactive inside GorillaDesk's web UI.
How does this compare to using GorillaDesk's web app?
The MCP gives your AI agents structured access to customer and billing data without switching tabs or copying IDs. You lose the visual job board, drag-and-drop scheduling, and attachment uploads — those stay in the web app. Use Switchy when you want to query invoice status, pull customer history, or create records from chat. Use the web app for scheduling, photo uploads, and anything requiring GorillaDesk's mobile-optimised UI.
Who on the team should connect this MCP?
Whoever owns your GorillaDesk account and can generate API keys — usually the office manager or business owner. Since the API key grants company-wide read/write access, you want one trusted person to connect it in Switchy, then share the workspace with dispatchers, sales reps, or admins who need AI-assisted customer lookups. Don't let every team member generate their own key; centralise the connection to avoid credential sprawl.