Fewsats MCP Server
Official# fewsats-mcp: A Fewsats MCP Server
## Overview
This MCP server integrates with [Fewsats](https://fewsats.com) and allows AI Agents to purchase anything in a secure way.
MCP is
### Tools
1. `balance`
- Retrieve the balance of the user's wallet
- Input: None
- Returns: Current wallet balance information
2. `payment_methods`
- Retrieve the user's payment methods
- Input: None
- Returns: List of available payment methods
3. `pay_offer`
- Pays an offer with the specified ID from the l402_offers
- Input:
- `offer_id` (string): String identifier for the offer
- `l402_offer` (object): Offer details containing:
- `offers`: Array of offer objects with ID, amount, currency, description, title
- `payment_context_token`: Payment context token string
- `payment_request_url`: URL for payment request
- `version`: API version string
- Returns: Payment status response
4. `payment_info`
- Retrieve the details of a payment
- Input:
- `pid` (string): Payment ID to retrieve information for
- Returns: Detailed payment information
## Installation
### Using uv (recommended)
When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed. We will
use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run *fewsats-mcp*.
```bash
uvx fewsats-mcp
```
### Using PIP
Alternatively you can install `fewsats-mcp` via pip:
```bash
pip install fewsats-mcp
```
After installation, you can run it as a script using:
```bash
fewsats-mcp
```
## Configuration
### Usage with Claude Desktop
Add this to your `claude_desktop_config.json`:
**Important**: Replace `YOUR_FEWSATS_API_KEY` with the API key you obtained from [Fewsats.com](https://fewsats.com/).
<details>
<summary>Using uvx</summary>
```json
"mcpServers": {
"Fewsats Server": {
"command": "uvx",
"args": ["fewsats-mcp"],
"env": {
"FEWSATS_API_KEY": "YOUR_FEWSATS_API_KEY"
}
}
}
```
</details>
TDQS
Scored across 6 tools
Most tools have distinct purposes: balance, billing_info, payment_info, and payment_methods are clearly differentiated for wallet, billing, payment details, and payment methods respectively. However, create_x402_payment_header and pay_offer both involve payment processing and could be slightly confusing, as they target different protocols (X402 vs L402) but share overlapping payment-related functionality.
The naming follows a consistent snake_case pattern throughout (e.g., billing_info, payment_methods). However, there is a minor inconsistency with create_x402_payment_header using a more descriptive prefix (create_x402_) while others are simpler nouns or verb_noun combos, slightly deviating from a uniform style.
With 6 tools, the count is well-scoped for a payment and wallet management server. Each tool serves a specific function without redundancy, covering key areas like balance, billing, payments, and payment methods, making it efficient and manageable.
The tool set covers core payment and wallet operations well, including balance retrieval, billing info, payment details, payment methods, and payment execution for different protocols. A minor gap exists in lacking tools for updating or deleting payment methods or billing info, but agents can likely work around this with the provided tools.