Skip to main content
Glama
README.md
# buttonwall-mcp

MCP server for [The Button Wall](https://thebuttonwall.com): a 1000×1000 px wall where every rented area is a real, clickable button.

Lets an AI assistant check how full the wall is, quote a button, find free space and create a Stripe checkout link. **The agent never pays:** the buyer opens the link and pays on Stripe, and every button is reviewed by a person before it goes live (full refund if rejected).

## Tools

| Tool | What it does |
|---|---|
| `get_wall_status` | % claimed, live buttons, pricing and rules |
| `quote_spot` | Price for a size and plan, and whether a position is free |
| `find_free_spots` | Free positions for a size, nearest to a point first |
| `create_checkout_link` | Stripe checkout link for a new button (human pays) |

## Install

Claude Desktop / Claude Code / Cursor (`mcpServers` config):

```json
{
  "mcpServers": {
    "buttonwall": { "command": "npx", "args": ["-y", "buttonwall-mcp"] }
  }
}
```

Claude Code: `claude mcp add buttonwall -- npx -y buttonwall-mcp`

## Pricing

€0.10 per pixel per 30 days (10×10 px = €10). 6 months −10%, 12 months −20%. Prepaid, never auto-renews.

## Example prompts

- "How full is The Button Wall right now?"
- "Find me a free 120×40 spot near the centre and tell me what 6 months costs."
- "Put a button for my SaaS on The Button Wall: text 'Try Acme free', link https://acme.dev, brand colour #ff5a1f."

## Limits

Checkout links are rate-limited to 10 per 10 minutes per IP. The server uses the same public, read-only endpoints as thebuttonwall.com.

## License

MIT

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation4/5

The four tools target distinct steps in the purchase flow, but quote_spot (price + exact availability) overlaps with find_free_spots (available positions) and get_wall_status (fullness + pricing rules). Descriptions help clarify boundaries, but an agent could still hesitate between quote_spot and find_free_spots when checking a specific location.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: create_checkout_link, get_wall_status, quote_spot, find_free_spots. The convention is predictable and readable throughout.

Tool Count5/5

Four tools form a tight, purposeful set for a niche purchasing workflow: discovery (find_free_spots), pricing/availability (quote_spot), context (get_wall_status), and purchase initiation (create_checkout_link). Nothing feels redundant or missing from the core flow.

Completeness4/5

The surface covers the essential pre-purchase and checkout steps, but lacks post-purchase operations such as checking order/review status or viewing one's existing buttons. These are minor gaps an agent can work around or that may be intentionally out of scope.

Maintenance

ActivityMaintained
ResponsivenessSyncing