Automate Feedqube with n8n (MCP Client Tool)

Set it up

1. Create an API key in Feedqube under Settings → AI apps → API keys. Copy it when it is shown: for your security it is shown only once. Treat it like a password and never commit it to a shared repository.
2. In your workflow, add an AI Agent node and, under Tools, add the MCP Client Tool node.
3. Set the endpoint to https://app.feedqube.com/api/mcp and the transport to HTTP Streamable.
4. Set Authentication to Bearer Auth and create a credential with your Feedqube API key (without the word Bearer).
5. Choose which Feedqube tools the agent may use (for example only create_post and list_apps).

Example workflow

• Trigger: RSS Feed Trigger on your blog.
• AI Agent: "Write a LinkedIn draft and an X draft about this article, for tomorrow at 09:00".
• Feedqube: the drafts appear on your calendar for approval.

What stays safe

Posts created by an AI app are always saved as drafts. Nothing is published until you approve it in Feedqube, and you can disconnect the app at any time in Settings → AI apps.

If something doesn't work

• Feedqube's tools don't show up: turn Feedqube on in the chat's tools or connectors menu, then start a new chat.
• The sign-in window doesn't open: allow pop-ups for the AI app, or try its web version.
• It can't connect: check that the address is exactly https://app.feedqube.com/api/mcp, and that your Feedqube trial or plan is active.
• It can read but not create drafts: the app (or the API key) is set to read-only. Change it in Feedqube under Settings → AI apps.
• An API key is rejected: it may have been deleted or copied with a space. Create a new one in Settings → AI apps → API keys.