MCP server for PixlyPost — lets Claude, Cursor, and other MCP-capable AI assistants call the PixlyPost HTTP API on the user's behalf. The API key lives in the OS keychain (via `pixlypost-mcp-server lo
{ "mcpServers": { "pixlypost-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
claude mcp add pixlypost-mcp-server -- npx -y pixlypost-mcp-server@0.3.1Run in a terminal.
{ "mcpServers": { "pixlypost-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchOverview
MCP server for PixlyPost — lets Claude, Cursor, and other MCP-capable AI assistants call the PixlyPost HTTP API on the user's behalf. The API key lives in the OS keychain (via `pixlypost-mcp-server login`); the AI never sees it.
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Pixlypost runs locally over stdio.
Last checked 2026-10-26. MCP server for PixlyPost — lets Claude, Cursor, and other MCP-capable AI assistants call the PixlyPost HTTP API on the user's behalf. The API key lives in the OS keychain (via `pixlypost-mcp-server login`); the AI never sees it.
From the publisher
README is not crawled yet. Open the repository