@gravv/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAVV_API_KEY | No | Sandbox or live key; selects the environment. Omit for docs-only mode. Get an API key from your Gravv dashboard. | |
| GRAVV_BASE_URL | No | Override the API host. | https://api.gravv.xyz |
| GRAVV_TOOLSETS | No | Comma-separated list of toolsets to load. Same as --toolsets. Defaults to all except account-applications. | |
| GRAVV_RATE_PER_MINUTE | No | Client-side request throttle. Lower if you hit rate limits. | 60 |
| GRAVV_ALLOW_LIVE_WRITES | No | Set to 'true' to permit money movement on a live key. When unset or false, money-moving tools on live keys are refused. | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchGravvDocsA | Search the Gravv documentation — integration guides, recipes, and API reference (177 pages). Use this BEFORE implementing any Gravv integration, and whenever a call fails in a way the error does not fully explain. The guides carry the ordering, prerequisites, and corridor rules that the API tool schemas do not. Returns ranked pages with excerpts; follow up with getGravvDocPage for full text. |
| getGravvDocPageA | Fetch the full text of one Gravv documentation page by slug, as returned by searchGravvDocs. Use when an excerpt is not enough — for worked examples, complete request/response bodies, or a full flow diagram. |
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 2 tools
Each tool has a distinct, non-overlapping purpose: one searches documentation, the other fetches a specific page by slug. No ambiguity between them.
Both tools follow a consistent CamelCase pattern with a verb (search, get) followed by the subject (GravvDocs, GravvDocPage). Naming is uniform and predictable.
With only 2 tools, the server is on the lean side, but for a documentation-searching purpose the pair is reasonable and well-scoped.
The tools cover the core documentation workflow—search and retrieve full text. A minor gap is the lack of a browse-all-pages feature, but the essential operations are present.