Shatale MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHATALE_API_KEY | No | Your Shatale API key (sandbox key sk_sandbox_*). Omit to run in guest mode. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| explain_shataleA | Entry point. Reports the current mode (GUEST / DEMO(SANDBOX) / LIVE), the tools available in that mode, the recommended first prompt, and how to move from demo to live. Call this first. No API key required. |
| simulate_purchase_flowA | Simulates the Shatale agent payment lifecycle in guest mode: policy check, approval decision (approved / declined / requires_approval), virtual card step and timeline. No real API call or payment is made. Use this before registering for a sandbox key. |
| generate_policy_templateB | Generates a spending policy template for a use case AND validates it: risk level, warnings, and recommended controls (approval threshold, max transaction, blocked categories). Never returns a silently unsafe policy. No API key required. |
| list_capabilitiesA | Lists all capabilities currently available on this MCP server, based on the configured API key mode. |
| list_mcc_codesA | Search or list MCC (Merchant Category Codes) used for spending policy configuration. |
| search_merchantsA | Search the Shatale merchant catalog. Find merchants by category, capability, keyword, or country. Returns merchants with their MCP capabilities so you can determine which merchants support agent-driven purchases. |
| get_merchant_detailsA | Get detailed information about a specific merchant, including their MCP server configuration, available tools, rate limits, and capabilities. Use this after search_merchants to get integration details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| shopping-policy | Draft a spending policy for shopping and try it against simulated purchases |
| travel-policy | Draft a spending policy for travel and try it against simulated bookings |
| policy-designer | Design a spending policy for an AI agent, then check it against simulated purchases |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Shatale Quickstart Guide | 5-minute guide to get started with Shatale AI agent payments |
| Policy Engine Guide | How Shatale policies and skills control agent spending |
| Vertical Use Cases | Examples of AI agent payment setups for different industries |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: simulate, generate, search, and explain each target a different workflow step. The only mild overlap is between explain_shatale and list_capabilities, since both can describe what is available in the current mode.
Every tool follows a consistent verb_noun snake_case pattern: explain_, simulate_, generate_, list_, search_, and get_. There are no mixed naming conventions or vague action verbs.
Seven tools is well-scoped for an onboarding and discovery server: orientation, simulation, policy generation, capability listing, MCC lookup, merchant search, and merchant details. Each tool earns its place without redundancy.
The tool surface covers the full exploration journey from first prompt through policy simulation, validation, and merchant research. The main gap is that registration or progression to sandbox/live mode is explained but not exposed as a tool, leaving a small external workflow step.