junto-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOOVI_APP_ID | Yes | API key for the Woovi/OpenPix provider | |
| JUNTO_PER_TX_MAX | No | Max single transaction in cents | 20000 |
| JUNTO_DAILY_LIMIT | No | Max total spend per day in cents | 50000 |
| JUNTO_CONFIRM_ABOVE | No | Ask human before sending if the amount in cents exceeds this threshold | 5000 |
| JUNTO_ALLOWED_PROVIDERS | No | Comma-separated allowlist of providers | |
| JUNTO_ALLOWED_DESTINATIONS | No | Comma-separated type allowlist of destinations |
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 |
|---|---|
| payC | Send money to a destination via the best available provider. Amount in cents. |
| chargeC | Create a payment request, invoice, or QR code. |
| statusB | Check payment or charge status by correlation ID. |
| refundB | Refund a completed payment by correlation ID. |
| balanceB | Check available funds on a payment provider. |
| providersA | List configured payment providers and their capabilities. |
| limitsA | Check current spending limits and today's usage (all values in cents). |
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
Each tool has a clearly distinct purpose with no ambiguity: balance checks funds, charge creates payment requests, limits checks spending, pay sends money, providers lists providers, refund processes refunds, and status checks status. The descriptions clearly differentiate these operations, making it easy for an agent to select the right tool.
All tool names follow a consistent, simple noun-based pattern (balance, charge, limits, pay, providers, refund, status) that is readable and predictable. There are no deviations in style or convention, making the set coherent and easy to navigate.
With 7 tools, this server is well-scoped for payment processing, covering key operations like checking funds, creating charges, sending payments, listing providers, handling refunds, and checking status. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides strong coverage for core payment workflows, including create (charge), read (balance, limits, providers, status), and update/delete-like actions (pay, refund). A minor gap is the lack of a tool for updating payment details or managing providers beyond listing, but agents can likely work around this with existing tools.