# fletch-mcp

Remote MCP server for the live Fletch deployment.

## What it does

- wraps the live Fletch Pages API
- exposes Fletch Pay, Fletch Link, Fletch Bridge, and Fletch Swap as MCP tools
- keeps agent integrations pointed at one product surface instead of hand-rolling fetch calls

## Remote endpoint

- Streamable HTTP endpoint: `https://www.fletch-pay.com/mcp`
- Public site: `https://www.fletch-pay.com`

## Environment

- `FLETCH_API_BASE_URL` defaults to `https://fletch-bank.pages.dev`
- `FLETCH_API_KEY` is reserved for future private Fletch routes

## Current tools

- `fletch_health`
- `fletch_pay_catalog`
- `fletch_pay_order`
- `fletch_pay_status`
- `fletch_link_quote`
- `fletch_link_order`
- `fletch_bridge_quote`
- `fletch_bridge_order`
- `fletch_bridge_status`
- `fletch_swap_quote`
- `fletch_swap_order`
- `fletch_swap_catalog`

## Connect

Use the remote MCP endpoint instead of local workspace paths whenever possible.

```json
{
  "mcpServers": {
    "fletch": {
      "transport": "streamable_http",
      "url": "https://www.fletch-pay.com/mcp"
    }
  }
}
```

## Local development

```bash
npm install
npm start
```

## Notes

- If the production domain changes, update `FLETCH_API_BASE_URL`
- The remote MCP surface is published at `/mcp`
- The MCP surface stays stable as long as the Pages API routes stay stable