Pixelletter MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 44 installs a week from npm. Last commit 19 Oct 2026.
Send physical letters and faxes through the PixelLetter interface, test mode included.
Today is the operative word: we check Pixelletter MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 pixelletter-mcp -e 'PIXELLETTER_EMAIL=<PIXELLETTER_EMAIL>' -e 'PIXELLETTER_PASSWORD=<PIXELLETTER_PASSWORD>' -- npx -y pixelletter-mcp
{
"mcpServers": {
"pixelletter-mcp": {
"command": "npx",
"args": [
"-y",
"pixelletter-mcp"
],
"env": {
"PIXELLETTER_EMAIL": "<PIXELLETTER_EMAIL>",
"PIXELLETTER_PASSWORD": "<PIXELLETTER_PASSWORD>"
}
}
}
}
[mcp_servers.pixelletter-mcp]
command = "npx"
args = ["-y", "pixelletter-mcp"]
env = { PIXELLETTER_EMAIL = "<PIXELLETTER_EMAIL>", PIXELLETTER_PASSWORD = "<PIXELLETTER_PASSWORD>" }
{
"mcpServers": {
"pixelletter-mcp": {
"command": "npx",
"args": [
"-y",
"pixelletter-mcp"
],
"env": {
"PIXELLETTER_EMAIL": "<PIXELLETTER_EMAIL>",
"PIXELLETTER_PASSWORD": "<PIXELLETTER_PASSWORD>"
}
}
}
}
{
"servers": {
"pixelletter-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pixelletter-mcp"
],
"env": {
"PIXELLETTER_EMAIL": "<PIXELLETTER_EMAIL>",
"PIXELLETTER_PASSWORD": "<PIXELLETTER_PASSWORD>"
}
}
}
}
Put your own values in place of
<PIXELLETTER_EMAIL> (E-mail address the PixelLetter account is registered with), <PIXELLETTER_PASSWORD> (PixelLetter account password).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
PIXELLETTER_DEFAULT_DESTINATION (Default destination country as a two letter ISO code, for example DE), PIXELLETTER_FORCE_TEST_MODE (Force test mode for every order, so nothing is printed, sent or charged).
Customer and prospect voice interviews, feedback, and testimonials through a hosted MCP connector.
List, create and move tasks through todo, in progress and done.
Internal test MCP server for local dev and Bifrost integration testing.
Agentic UX testing for real Electron apps: launch, inspect, interact, and assert through MCP.
Test-network group buying through nine buyer and seller tools.
Run e2e flows on real iOS and Android phones through the local Proofsheet hub (macOS).
Find retiring LLM calls in code and test the replacement model on real traffic before switching.
A real Mac for your agent: build, test, run, and tap through iOS apps on the simulator.
Answers built from our own checks of this server.