SmoothSend MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docsA | Get SmoothSend documentation for a specific topic. Use this to answer questions about installation, integration, API methods, examples, or billing. |
| estimate_creditsA | Estimate the monthly SmoothSend credit cost for a dApp based on transaction volume and type. Returns per-transaction fee and monthly total. |
| get_token_addressA | Get the Aptos Mainnet fungible asset address for a supported token (USDC, USDT, WBTC, USDe, USD1). Required when using ScriptComposerClient. |
| get_code_snippetB | Get a ready-to-use code snippet for a specific SmoothSend integration pattern. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SmoothSend Overview | Overview of SmoothSend, quick start, and pricing |
| Installation Guide | How to install @smoothsend/sdk and configure it |
| Quick Start Guide | Step-by-step guide to go gasless in minutes |
| API Reference | Full API reference for SmoothSendTransactionSubmitter and ScriptComposerClient |
| Examples | Real-world code examples for common SmoothSend use cases |
| Billing & Pricing | Credit-based pricing details for SmoothSend |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: cost estimation, code retrieval, documentation access, and token address lookup. An agent can easily differentiate between them based on their specific functions.
All tools follow a consistent verb_noun pattern (estimate_credits, get_code_snippet, get_docs, get_token_address) with 'get' used for three tools and 'estimate' for one, maintaining readability and predictability throughout.
Four tools are reasonable for a SmoothSend integration server, covering key areas like cost, code, docs, and tokens. It's slightly lean but not incomplete, as the tools address core needs without unnecessary bloat.
The tool set covers essential integration tasks: planning (estimate), implementation (code snippet), reference (docs), and configuration (token address). Minor gaps might exist, such as direct API calls or transaction execution, but agents can work around these using the provided tools.