Gripp MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRIPP_API_URL | No | URL of the Gripp API endpoint. | https://api.gripp.com/public/api3.php |
| GRIPP_API_TOKEN | Yes | Your Gripp API token for authentication. | |
| GRIPP_REQUEST_TIMEOUT_MS | No | Timeout in milliseconds for API requests. | 30000 |
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 |
|---|---|
| gripp_list_entitiesA | List available Gripp API entities, fields counts, and supported method names. |
| gripp_describe_entityA | Describe one Gripp API entity, including fields, references, enum values, methods, and examples. |
| gripp_getB | Retrieve Gripp entities with filters, paging, and ordering. Uses the entity.get API method. |
| gripp_getoneA | Retrieve a single Gripp entity. Uses the entity.getone API method and returns the first matching item. |
| gripp_createB | Create a Gripp entity. Requires confirm=true because this writes to Gripp. |
| gripp_updateA | Update a Gripp entity by ID. Requires confirm=true because this writes to Gripp. |
| gripp_deleteA | Delete a Gripp entity by ID. Requires confirm=true because this permanently changes Gripp data. |
| gripp_callB | Call any Gripp API method by full method name. Non-read methods require confirm=true. |
| gripp_batchB | Execute multiple Gripp API calls in one Gripp transaction. Non-read calls require confirm=true per item. |
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 9 tools
Most tools have clearly distinct purposes. However, 'gripp_call' is a catch-all that can replicate other tools, and 'gripp_get' vs 'gripp_getone' may cause minor confusion, but descriptions help differentiate.
All tools follow a 'gripp_verb' or 'gripp_verb_entity' pattern. Minor deviations: 'describe_entity' and 'list_entities' are slightly more descriptive than imperative, and 'getone' breaks the verb-noun pattern.
With 9 tools, the set covers essential operations (CRUD, batch, metadata) without being overwhelming. The count is well-scoped for a generic API wrapper.
The tool surface covers most needed operations: listing, describing, CRUD, batch, and raw calls. Missing advanced search or count, but the general call and batch can fill minor gaps.