Charlotte runs on your own machine — the client starts it, so there is no endpoint to ping. 661 installs a week from npm. Last commit 12 Sep 2026.
Renders web pages into structured, agent-readable representations using headless Chromium.
What the code does
We read the source, 18 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const filePath = path.join(this._screenshotDir, filename);
"docker run --cap-add SYS_ADMIN --shm-size 2g -p 3737:3737 ghcr.io/ticktockbent/charlotte";
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add charlotte -- npx -y @ticktockbent/charlotte{
"mcpServers": {
"charlotte": {
"args": [
"-y",
"@ticktockbent/charlotte"
],
"command": "npx"
}
}
}[mcp_servers.charlotte]
command = "npx"
args = ["-y", "@ticktockbent/charlotte"]{
"mcpServers": {
"charlotte": {
"args": [
"-y",
"@ticktockbent/charlotte"
],
"command": "npx"
}
}
}{
"mcpServers": {
"charlotte": {
"args": [
"-y",
"@ticktockbent/charlotte"
],
"command": "npx"
}
}
}Alternatives to Charlotte
same job, measured the same wayWeb browsing & research for AI agents — fetch/read pages, structured extraction, Exa search.
Render Markdown and LLM output into accessible PDF/UA-1 PDFs. No headless Chromium.
AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real
Headless browser primitives for AI agents when sites need real JS rendering.
Browserless MCP — wraps the Browserless headless-Chromium REST API (browserless.io)
Reliable web access for AI agents: smart HTTP, rotating proxies, and full-browser rendering.
A headless painting engine for AI agents: brushes, paint load, wet blending, canvas texture.
Charlotte — questions
Answers built from our own checks of this server.