# stapler MCP server

> Reduces memory bloat by running MCP servers as a single shared daemon with thin-client proxies for multiple AI agent sessions.

- Repository: https://github.com/tstapler/stapler-mcp
- Page: https://hostedmcp.org/servers/tstapler/stapler-mcp
- Transport: —
- Stars: 0
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `STAPLER_MCP_BROWSER_PROFILE_DIR` | no | no |  |
| `STAPLER_MCP_TOOL_PROFILE` | no | no |  |

## Tools (19)

- `fetch_page`
- `brave_web_search`
- `read_website`
- `read_saved_page`
- `download_website`
- `stapler_browser_close_session`
- `stapler_browser_tabs`
- `stapler_browser_hover`
- `stapler_browser_select_option`
- `stapler_browser_press_key`
- `stapler_browser_wait_for`
- `stapler_browser_list_sessions`
- `stapler_browser_close_all_sessions`
- `stapler_daemon_status`
- `web`
- `browser-core`
- `browser-advanced`
- `docs`
- `daemon`

## FAQ

### Can I run this as a persistent background service?

Yes, it provides templates for Linux (systemd user service) and macOS (launchd agent) to ensure the daemon survives reboots.

### Does it support HTTP transport?

Yes, it offers an opt-in Streamable HTTP endpoint protected by a bearer token for clients that can speak MCP-over-HTTP directly.

### How do I update the server?

You must update both the thin client and the daemon separately, as the daemon is not replaced automatically during a rebuild.
