pushtodisplay
OfficialThis MCP server lets you manage Push To Display boards and send real-time content updates to display devices.
Send styled text updates to a board or the default board, including blocks, colors, alignment, panel targeting, full-panel mode, and density.
List boards and retrieve details for a specific board.
Create, update, and permanently delete boards.
Set a default board for future sends.
List active device-board stream connections.
Allows GitHub Copilot (VS Code Copilot) to send updates to display boards and manage boards (create, list, delete, set default) via the MCP protocol.
pushtodisplay
Command-line interface and MCP server for Push To Display — send real-time updates to display boards from your terminal or AI agents.

Get the app
Turn any screen into a live display board — get Push to Display on iOS and Android.
![]()
Related MCP server: widget-studio
Install
Run directly with npx (no install needed):
npx pushtodisplay --helpOr install globally:
npm install -g pushtodisplayRequires Node.js 18+. See the PushToDisplay documentation for guides, use cases, and API details.
Quick start
# Log in (opens browser)
pushtodisplay auth login
# Send an update (uses your default board)
pushtodisplay send "Hello, Display!"
# Send to a specific board
pushtodisplay send -b <board-id> "Deploy completed"
# List your boards
pushtodisplay boards listAuthentication
Log in with your Push To Display account — the same account you use in the mobile app.
Browser login (default)
pushtodisplay auth loginOpens your browser. Sign in and the CLI receives your credentials automatically.
Device code login (headless)
For machines without a browser — SSH sessions, containers, or remote servers:
pushtodisplay auth login --device-codeThe CLI prints a URL and a one-time code. Open the URL on any device, enter the code, and approve the login.
Credentials are stored in your OS keychain (macOS Keychain, Linux libsecret, Windows Credential Manager). Falls back to ~/.config/pushtodisplay/ if the keychain is unavailable.
# Check auth status
pushtodisplay auth status
# Machine-readable status for scripts/agents (exit 0 = authenticated)
pushtodisplay auth status --json
# Log out (clear stored credentials)
pushtodisplay auth logoutauth status reports effective auth: an expired access token is still
reported as authenticated when a valid refresh token can renew it transparently
(a will refresh automatically note is shown instead of the raw token expiry).
It exits 0 when authenticated and 1 when not, so it is safe to gate
scripts on it.
{
"authenticated": true,
"method": "oauth",
"accessTokenExpired": true,
"canRefresh": true,
"sessionExpiresAt": "2026-06-01T00:00:00.000Z"
}Commands
send
Send a display update to a board.
# Simple text
pushtodisplay send -b my-board-id "Deploy succeeded"
# Styled text
pushtodisplay send -b my-board-id "Status" --size large --weight bold --color "#00FF00"
# Multiple inline runs — they stay on ONE line
pushtodisplay send -b my-board-id "Build:" "passing" --color "#22C55E"
# Panel targeting with layout options
pushtodisplay send -b my-board-id --panel 2 "Right panel content"
pushtodisplay send -b my-board-id --panel 1 --full-panel --density compact --align-x center "Alert"
# Per-run styling with JSON (repeatable)
pushtodisplay send -b my-board-id \
--block '{"text": "API Health", "size": "large", "weight": "bold"}' \
--block '{"text": "Uptime: 99.97%", "color": "#22C55E"}'
# Pipe a full JSON payload from stdin
echo '{"boardId":"my-board-id","blocks":[{"text":"From pipe"}]}' | pushtodisplay send --stdinIf no -b flag is provided, the server uses your default board.
How text renders
Blocks are inline runs, not lines. Think of <span>, not <p>. The blocks
of one message flow onto a single line in order, and wrap like a paragraph when
they run out of width:
pushtodisplay send -b my-board-id "Build:" "passing" --color "#22C55E"renders as one line:
Build: passingnot as two lines. Each run keeps its own size, weight, colour, and background, so a message is one paragraph with styled runs inside it.
To put content on separate lines, send separate messages. Every send is its own entry in the panel's scrollable history, so multiple lines are multiple messages. Newlines inside a single message are not a layout mechanism.
--density sets the line height used when that paragraph wraps — it is not
the spacing between messages.
Note: in
--full-panelmode blocks are currently stacked on separate lines. That legacy behaviour is being removed so full-panel matches the inline model above.
Style flags
Flag | Values | Description |
|
| Text size |
|
| Font weight |
| Hex color ( | Text color |
| Hex color ( | Background color |
Panel flags
Flag | Values | Description |
|
| Target panel number |
| — | Enlarge to the whole board |
|
| Line height when text wraps |
|
| Horizontal alignment |
|
| Vertical alignment |
Other flags
Flag | Description |
| Board ID |
| Inline styled run as JSON (repeatable) |
| Read full JSON request from stdin |
boards
pushtodisplay boards list # List all boards
pushtodisplay boards get <id> # Get board details
pushtodisplay boards create -n "Name" # Create a board
pushtodisplay boards create -n "Dash" -l 4 # Create with a layout
pushtodisplay boards delete <id> # Delete a boardCreate options:
Flag | Description |
| Board name (required) |
| Board description |
| Layout ID |
devices
pushtodisplay devices list # List active device-board streamsconfig
pushtodisplay config # Show current configuration
pushtodisplay config show # Same as aboveJSON output
Add --json to any command for machine-readable output:
pushtodisplay boards list --json
pushtodisplay send -b my-board "test" --jsonConfiguration
Configuration is resolved in order: environment variables → config file → defaults.
Env var | Description | Default |
| API endpoint |
|
| Service endpoint |
|
| Identity provider |
|
| Config directory |
|
MCP server
The CLI includes a built-in Model Context Protocol server, giving AI agents (Claude, Cursor, VS Code Copilot, and others) direct access to your display boards.
The MCP server inherits your CLI session — if you've run pushtodisplay auth login, it authenticates automatically.
Setup
Claude Code
claude mcp add pushtodisplay -- npx pushtodisplay mcpClaude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"pushtodisplay": {
"command": "npx",
"args": ["pushtodisplay", "mcp"]
}
}
}Cursor
Open Settings → MCP Servers → Add Server, or edit .cursor/mcp.json:
{
"mcpServers": {
"pushtodisplay": {
"command": "npx",
"args": ["pushtodisplay", "mcp"]
}
}
}VS Code (GitHub Copilot)
Add to .vscode/mcp.json:
{
"servers": {
"pushtodisplay": {
"command": "npx",
"args": ["pushtodisplay", "mcp"]
}
}
}Other MCP clients
Any MCP client that supports stdio transport can use Push To Display. The server command is:
npx pushtodisplay mcpAvailable MCP tools
Tool | Description |
| Send content to a board |
| List all boards |
| Get details of a board |
| Create a new board |
| Update a board's name, description, or layout |
| Set a board as your default |
| Delete a board permanently |
| List active device connections |
Commands at a glance
Command | Description |
| Log in (browser or device code) |
| Remove stored credentials |
| Show current auth status |
| Send a display update |
| List your boards |
| Get board details |
| Create a new board |
| Delete a board |
| List active device connections |
| Show current configuration |
| Start the MCP server |
API key authentication
For CI/CD pipelines and scripts where interactive login isn't available, you can authenticate with an API key. Create one from the mobile app or the web portal. API keys start with pt_.
# Via environment variable
export PTD_API_KEY=pt_your_key_here
pushtodisplay send "From CI"
# Or store in keychain
pushtodisplay auth login --api-key pt_your_key_hereNote: API key auth only supports the
sendcommand. Useauth loginfor full access to boards, devices, and config management.
Screenshots
4-panel layout — regional status at a glance
Multi-panel with CI/CD pipeline and infrastructure logs
Incident timeline with color-coded severity
License
Available Tools
8 toolspushtodisplay_create_boardC
Create a new board.
Inputs: name (required), description, layoutId.
pushtodisplay_delete_boardADestructive
Permanently delete a board and all its data. This action cannot be undone.
Inputs: boardId (required).
pushtodisplay_get_boardB
Get details of a specific board by ID.
Inputs: boardId (required).
pushtodisplay_list_boardsA
List all boards owned by the authenticated user.
Inputs: no named parameters.
pushtodisplay_list_devicesB
List active device-board stream connections.
Inputs: no named parameters.
pushtodisplay_send_updateA
Send a display update to a PushToDisplay board. Publishes text content to all devices connected to the specified board.
Inputs: blocks (required), boardId, panelId, fullPanel, +4 more.
pushtodisplay_set_default_boardA
Set a board as the user's default board. The default board is used when no board ID is specified in send_update.
Inputs: boardId (required).
pushtodisplay_update_boardB
Update an existing board's name, description, or layout.
Inputs: boardId (required), name, description, layoutId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct action/resource: board CRUD, device listing, sending updates, and setting defaults. No overlapping functionality.
All tools follow a consistent pattern: `pushtodisplay_verb_noun` in snake_case, making them predictable and easy to differentiate.
8 tools provide a balanced scope for board management and display updates, neither too few nor too many.
Covers full CRUD for boards plus device listing, sending updates, and default board setting. Minor gap: no device management beyond listing.
Maintenance
Related MCP Connectors
Publish, search, and promote time-sensitive news and messages through a public remote MCP server.
Send notifications, updates and daily digests to a person's phone — typed cards in a private feed.
Push notifications with personalized sounds - manage and trigger your vybits via MCP
Publish and schedule content across supported platforms, with publishing state and per-platform adaptation. Built by AutomateLab. Product and documentation: https://automatelab.tech/products/mcp/content-distribution-mcp/
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude to build and preview mobile apps on multiple iOS and Android devices simultaneously, with live streaming and touch control, all via MCP.11 npm1MIT
- AlicenseAqualityDmaintenanceMCP server that lets agents create, display, and export rich UI widgets (cards, dashboards, charts, forms) inline in conversations, with interactive iframe support in MCP Apps hosts and PNG image fallback for other clients.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents running in separate consoles to exchange direct and broadcast messages through a blocking receive tool that releases instantly when mail arrives, so delivery feels push-like rather than polled. It also provides a live browser dashboard showing message flow, presence and per-agent profiles, plus CLI and HTTP endpoints for sending, tailing and replaying the log.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables building configurable workplace dashboards with eight MCP apps/widgets for agenda, brief, attention, goals, leave, learning, updates, and actions, all backed by synthetic live data via a standard MCP server.MIT