Connecting n8n

n8n can talk to remote MCP servers from an AI agent node. That makes it a good fit for recurring publishing — a weekly digest, a feed-driven roundup, a batch of posts on a schedule.

The steps

1. 1Open your client's settings and find where custom MCP servers (sometimes called connectors, integrations or tools) are added.
2. 2Add a server with the URL https://mcp.pressbotics.com/mcp.
3. 3Leave any API key or token field blank — Pressbotics uses OAuth.
4. 4Connect. The client opens Pressbotics in your browser.
5. 5Sign in and click Authorize. The client now lists the Pressbotics tools.

Menu names and their nesting change between clients and between versions of the same client. The shape above is stable; the exact wording on your screen may not be. If you cannot find the setting, search your client's own documentation for "MCP server".

Automation-specific advice

• Always pass an idempotency_key derived from the source item — the feed entry id, the row id. Workflows retry, and this is what stops a retry becoming a second post.
• Keep the site under review policy while you tune the workflow. Move to guardrails or full auto once the output is boring.
• Read partial and the per-component statuses in the response and fail the workflow node when something did not land, rather than treating any response as success.

What can go wrong

• A headless runner cannot complete an interactive OAuth screen. Authorize once from a browser session; the authorization persists.
• For a fully unattended agent that cannot do OAuth at all, use an agent key instead. See Agent keys.
• Bursty workflows hit your plan's monthly post cap. Check Usage and caps.