charlotte — Token-Efficient Browser MCP Server

Main

• Use Charlotte when a full accessibility-tree dump is too expensive: it’s designed to return a compact orientation on navigation and expand only on demand.

• Pick a tool profile to reduce definition overhead (README lists core/browse/full); start with --profile core for minimal tools.

• For production browsing, combine navigate + find/observe so your agent asks for exactly the region or element it needs, not the whole page.

Source-backed notes

• README positions Charlotte as a structured browser MCP server and compares output size against Playwright MCP.
• README’s benchmark table includes the Hacker News example: 336 characters for Charlotte navigate vs 61k+ for Playwright’s navigate dump.
• README documents startup tool profiles and shows charlotte --profile core|browse|full as the entrypoint.

FAQ

• Do I need Docker?: No — README shows npm global install; Docker is optional.
• Will it work with my MCP client?: If your client supports stdio MCP servers, the README shows example configs for Claude Code, Cursor, and others.
• What’s the safest first test?: Run charlotte --profile core and try navigating to example.com, then use find to locate a single link.