gingr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GINGR_API_KEY | Yes | A Gingr API key with read access | |
| GINGR_SUBDOMAIN | Yes | Your Gingr subdomain (e.g., 'mybiz' or 'mybiz.gingrapp.com' or full https URL) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gingr_list_ownersA | List pet owners (customers) from the connected Gingr facility — IDs, names, contact details, and signup dates. Use to analyze customer base size, growth, and retention. |
| gingr_list_animalsA | List animals (pets) registered at the Gingr facility — species, breed, age, owner, and notes. Use to analyze the pet population (breed mix, size distribution, etc.). |
| gingr_list_reservationsA | List boarding/daycare reservations — dates, services, animals, statuses, and revenue. Use to analyze occupancy, demand patterns, peak/off-peak periods, and revenue trends. Tip: keep the date range to ≤30 days; very wide ranges can time out. |
| gingr_get_owner_reservationsA | Get all reservations for a specific owner (customer). Use to analyze a customer's history, frequency, and lifetime value. Get owner_id from gingr_list_owners first. |
| gingr_list_appointmentsA | List grooming, spa, bathing, or training appointments. Returns dates, services, animals, and statuses. Note: Gingr has no separate appointments endpoint — these are reservations whose category (Training, Grooming, SPA, Bathing) this tool filters for. |
| gingr_list_servicesA | List the services offered at the facility (boarding tiers, grooming packages, daycare options, etc.) with IDs, names, descriptions, and prices. Use to understand the offering before recommending pricing or marketing. |
| gingr_list_employeesA | List staff/employees at the facility. Use to analyze staffing, roles, and capacity. Read-only — no personal data is modified. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
All seven tools have clearly distinct purposes: owners, animals, appointments (filtered by category), employees, owners, reservations (boarding/daycare), and services. No overlap or ambiguity.
All tools follow the consistent 'gingr_verb_noun' pattern (e.g., list_animals, get_owner_reservations). No mixing of conventions.
Seven tools is well-scoped for a pet facility management server. Each tool covers a core entity (owners, animals, employees, services, reservations in two flavors) without being excessive or minimal.
The server is read-only but covers the main entities needed for analysis. Minor gaps exist (e.g., no get_animal_by_id, no filtering by date for appointments), but overall it provides a solid analytical surface.