tabby-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TABBY_SECRET_KEY | Yes | Secret API key from Tabby dashboard |
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 |
|---|---|
| create_sessionB | Create a Tabby checkout session for BNPL. |
| get_sessionB | Get checkout session details. |
| create_paymentC | Create a payment from an approved session. |
| get_paymentB | Get payment details by ID. |
| captureC | Capture an authorized payment. |
| refundB | Refund a captured payment. |
| voidC | Void an authorized payment. |
| list_paymentsC | List payments with filters. |
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 8 tools
Each tool targets a distinct operation in the payment lifecycle: session creation, payment creation, capture, refund, void, and retrieval. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_session, get_payment, list_payments). No deviations.
8 tools is well-scoped for payment processing and checkout sessions. Each tool has a clear role without redundancy.
Covers the core BNPL flow: session creation, payment creation, capture, refund, void, and retrieval. Minor gap: no update or cancel session, but the essential operations are present.