Pushwing for
Cursor
Cursor runs the tools from the editor; Pushwing holds the tokens. One entry in mcp.json adds the server, one sign-in connects it.
{ "mcpServers": { "pushwing": { "url": "https://mcp.pushwing.com/mcp" } } }.cursor/mcp.json { "mcpServers": { "pushwing": { "url": "https://mcp.pushwing.com/mcp" } } } ✓ pushwing · 25 tools enabled
Set up in three steps
Add the server
{ "mcpServers": { "pushwing": { "url": "https://mcp.pushwing.com/mcp" } } }Add the entry to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project. Cursor Settings → MCP shows it.
Approve the sign-in
Cursor prompts for OAuth the first time: approve the Pushwing sign-in and consent screen once.
Try it
In chat, ask: "List my connected accounts and today's publishing limits."
Cursor note
Cursor handles the OAuth prompt itself; if it shows "needs login", click it and approve again. Tools appear under the MCP section of the chat.
Six prompts that work on day one
How it feels in Cursor
Public actions come back as a preview. Cursor shows it; you answer in the terminal.
Questions
Do I need an API key?
No. Your client signs in with OAuth. Keys exist for scripts and CI.
Can I use several channels?
Connect once per channel; Google's chooser lets you pick a different one each time.
Why are uploads private?
YouTube's rule for API projects that haven't passed its audit. Ours is pending.
How do I disconnect?
Dashboard → Connections → Disconnect; it revokes at Google.
Publish from Cursor.
Join the waitlist. We’ll email you when your invitation is ready.