Skip to main content
Glama
Ask GorillaDesk (gorilladesk-mcp)

Ask GorillaDesk (gorilladesk-mcp)

by daisydaines

Ask GorillaDesk (gorilladesk-mcp)

Read-only MCP server so Claude, ChatGPT, or Cursor can answer pest-business questions from your GorillaDesk account in plain English.

It looks things up. It does not create customers, change jobs, or take payments.

Example questions

  • How many customers do I have?

  • Who owes me money?

  • What’s on the schedule this week?

  • Who are my technicians?

  • How’s money this month?

  • Give me a Monday morning briefing

Related MCP server: OfficeRnD MCP Server

Auth

GorillaDesk uses a company API key (Bearer token).

  1. Open Addons → API

  2. Generate / copy the key

  3. Put it in .env as GORILLADESK_API_KEY (local) or paste it at /connect (hosted)

Docs: https://api.gorilladesk.com/docs/

Local install

cd gorilladesk-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
cp .env.example .env
# edit .env and paste GORILLADESK_API_KEY

Wire Cursor / Claude Desktop to scripts/run_mcp.sh (see mcp.json.example).

Hosted HTTP

export GORILLADESK_MCP_HOSTED=1
export GORILLADESK_VAULT_SECRET='a-long-random-string'
./scripts/run_mcp_http.sh

Path

Role

/

Landing

/gorilladesk

Product page

/connect

Paste API key → mint bearer token

/mcp

Streamable HTTP MCP

/healthz

Health

Safety

  • Client allows GET only

  • Tools annotated readOnlyHint=True

  • Owner tools return an answer string agents should read aloud

Relay

Product page lives under Relay at /gorilladesk. Marketing host: the relay-mcp Vercel project (fieldwork-mcp landing/).

Builder notes

pytest
ruff check src tests

Available Tools

19 tools
find_customerB
Read-onlyIdempotent

Answer: "Do I have a customer named ___?", "Find customer Smith"

Search customers by name, company, email, or account number.

Inputs: query (required), limit. Returns: result

get_customerA
Read-onlyIdempotent

Fetch one customer by id. Prefer find_customer first.

Inputs: customer_id (required), include. Returns: result

get_invoiceB
Read-onlyIdempotent

Fetch one invoice by id.

Inputs: invoice_id (required), include. Returns: result

get_jobA
Read-onlyIdempotent

Fetch one job by id.

Inputs: job_id (required), include. Returns: result

health_checkA
Read-onlyIdempotent

Verify GorillaDesk credentials. Run this first if other tools fail.

Calls GET /v1/company. On success returns a small company summary.

Inputs: no named parameters. Returns: result

how_is_business_doingB
Read-onlyIdempotent

Answer: "How's business?", "Give me a snapshot"

Jobs + invoiced/collected for a date window (default 30 days).

Inputs: days, end_date, start_date. Returns: result

how_many_customersA
Read-onlyIdempotent

Answer: "How many customers do I have?", "What's my customer count?"

Counts active GorillaDesk customers and breaks down by status.

Inputs: no named parameters. Returns: result

how_much_moneyA
Read-onlyIdempotent

Answer: "How much money came in?", "What did we invoice this month?"

Invoiced + collected totals for a date window (default 30 days).

Inputs: days, end_date, start_date. Returns: result

search_customersA
Read-onlyIdempotent

List/filter customers. Prefer find_customer / how_many_customers for owner questions.

Inputs: limit, offset, status, account_number. Returns: result

search_estimatesC
Read-onlyIdempotent

List/filter estimates.

Inputs: limit, offset, status, customer_id. Returns: result

search_invoicesA
Read-onlyIdempotent

List/filter invoices. Prefer who_owes_me_money / how_much_money for owners.

Inputs: limit, offset, status, end_date, +2 more. Returns: result

search_jobsB
Read-onlyIdempotent

List/filter jobs. Prefer whats_on_the_schedule for owner questions.

Inputs: limit, offset, keyword, end_date, +2 more. Returns: result

search_paymentsC
Read-onlyIdempotent

List/filter payments.

Inputs: limit, offset, end_date, start_date, +1 more. Returns: result

search_servicesA
Read-onlyIdempotent

List services. Prefer what_services_do_we_offer for owner questions.

Inputs: limit, offset. Returns: result

search_usersA
Read-onlyIdempotent

List users. Prefer who_are_my_technicians for owner questions.

Inputs: limit, offset. Returns: result

what_services_do_we_offerA
Read-onlyIdempotent

Answer: "What services do we offer?", "What's in the catalog?"

Lists GorillaDesk services.

Inputs: no named parameters. Returns: result

whats_on_the_scheduleA
Read-onlyIdempotent

Answer: "What's on the schedule?", "How many jobs this week?"

Jobs overview for a date range (default 7 days).

Inputs: days, end_date, start_date. Returns: result

who_are_my_techniciansA
Read-onlyIdempotent

Answer: "Who are my technicians?", "Who's on my team?"

Lists GorillaDesk users with roles.

Inputs: no named parameters. Returns: result

who_owes_me_moneyA
Read-onlyIdempotent

Answer: "Who owes me money?", "What's my AR?", "Who has open invoices?"

Ranks open GorillaDesk invoices by amount due.

Inputs: top_n. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation3/5

    There is overlap between natural-language query tools (e.g., how_much_money, who_owes_me_money) and generic search tools (e.g., search_invoices, search_customers), though descriptions mitigate confusion with 'Prefer' hints. A few pairs like search_customers/find_customer and search_jobs/whats_on_the_schedule are nearly interchangeable and could lead to misselection.

    Naming Consistency3/5

    The set mixes natural-language question phrases (how_much_money, who_are_my_technicians) with standard verb_noun patterns (search_customers, get_job). Each style is internally consistent, but the lack of a unified naming convention makes it harder to predict tool names across the whole server.

    Tool Count4/5

    19 tools is slightly over the ideal 3-15 range but appropriate for the breadth of the GorillaDesk domain (customers, jobs, invoices, payments, estimates, services, users). The two-layer design (answer-oriented vs. data-access) adds functionality but also inflates the count.

    Completeness4/5

    The toolkit covers the core entities needed for a read-only business assistant. Minor gaps exist, such as missing get_* tools for payments, estimates, services, and users, but the search tools likely return sufficient detail for most 'ask' scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the FieldRoutes pest-control / lawn-care operations platform — talk to your data from Claude, Cursor, or any MCP client.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that connects to an InvoiceFlash MySQL database, exposing clients, invoices, and quotes as tools for natural language querying via Claude Desktop or Claude Code.
      -