Skip to main content
Glama
@gravv/mcp

@gravv/mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GRAVV_API_KEYNoSandbox or live key; selects the environment. Omit for docs-only mode. Get an API key from your Gravv dashboard.
GRAVV_BASE_URLNoOverride the API host.https://api.gravv.xyz
GRAVV_TOOLSETSNoComma-separated list of toolsets to load. Same as --toolsets. Defaults to all except account-applications.
GRAVV_RATE_PER_MINUTENoClient-side request throttle. Lower if you hit rate limits.60
GRAVV_ALLOW_LIVE_WRITESNoSet 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.

Gravv — payments infrastructure for global money movement.

ENVIRONMENT: no API key configured. Documentation tools work; API tools are unavailable until GRAVV_API_KEY is set.

START WITH THE DOCS. Call searchGravvDocs before implementing anything. The API tool schemas describe individual calls; they do not describe how the flows fit together. The guides do — ordering, prerequisites, corridor rules, and worked examples.

PROMPTS walk through whole goals: open-account, onboard-customer, send-payout, send-remittance, send-crypto, convert-currency, issue-card, collect-payment, set-up-savings, reconcile, fix-stuck-transfer. When the user starts one of these, suggest they pick the matching prompt in their client.

Only searchGravvDocs and getGravvDocPage are available. To execute API calls, set GRAVV_API_KEY to a sandbox key and restart.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchGravvDocsA

Search the Gravv documentation — integration guides, recipes, and API reference, every page the docs site lists. 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

NameDescription
open-accountChoose and open a bank account or the business's card account, unblock an application, or give out deposit details.
onboard-customerCreate a person or a business and verify them, on a hosted page or server to server; resubmit a rejection; read their KYC documents.
send-payoutPay a US bank account by ACH, wire or RTP, a supplier or person abroad by SWIFT, a euro or UK account by SEPA or Faster Payments, or move money between a customer's own accounts.
send-remittancePay a bank account or mobile money wallet in Africa, Latin America or Asia from a USD balance, with a locked rate and the fee shown before the user confirms.
send-cryptoSend stablecoins to an outside wallet on the same network, ask about another network, or convert USDT to USDC between one customer's wallets.
convert-currencyQuote and place an FX order, pay the proceeds to a settlement instruction, and follow or cancel orders.
issue-cardVerify a cardholder and issue a USD card, fund it, set its limit, freeze or block it, close it, or give the same person another card.
collect-paymentReceive stablecoins at a wallet address, a bank deposit into an account, a local bank transfer, a card payment through a hosted checkout, or a charge to a saved card.
set-up-savingsOpen a savings account, save into it, withdraw from it, read interest and statements, and test it all in sandbox.
reconcileMatch transactions against the books, trace one transfer through its webhooks, total the fees, and catch up on missed webhook events.
fix-stuck-transferTell pending, paused, under review, waiting for approval and failed apart, and answer a pause for documents, sender details or a limit.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools form the classic search-then-fetch pair with clearly disjoint roles: one returns ranked excerpts across the docs corpus, the other returns full text for a single slug returned by the first. The descriptions explicitly state the handoff ("follow up with getGravvDocPage" / "by slug, as returned by searchGravvDocs"), leaving no room for misselection.

Naming Consistency5/5

Both names follow the same camelCase verb+noun pattern with a shared Gravv/Doc domain prefix: searchGravvDocs and getGravvDocPage. The verbs (search vs get) correctly signal breadth vs single-item retrieval, so the convention is both predictable and semantically informative.

Tool Count4/5

Two tools is thin relative to the 3-15 guideline, but for a pure documentation-retrieval server the search/fetch pair is the minimal complete surface and neither tool is redundant. Nothing is padded, though a third tool (e.g. list/index pages) would round it out.

Completeness4/5

Search plus full-page fetch covers the documentation lookup lifecycle end to end, including the excerpt-to-full-text escalation path. The only minor gap is the absence of any way to browse or enumerate page slugs or check docs versioning without a prior search hit.

Maintenance

ActivityMaintained
ResponsivenessLimited data