n8n
Connect FeedNest to n8n workflows via the MCP Client node or HTTP Request node.
Option A: MCP Client node (recommended)
n8n has a built-in MCP Client node that connects directly to FeedNest’s MCP server. Best for AI Agent workflows.
- 1
Add an MCP Client Tool node
In your n8n workflow, add an MCP Client Tool node (under AI → Tools).
- 2
Configure the connection
Fill in the following fields:
URL https://mcp.feednest.comAuthentication Bearer Authentication Bearer Token fn_live_... - 3
Connect to an AI Agent
Wire the MCP Client Tool node as a tool input to an AI Agent node. The agent will automatically discover all FeedNest tools.
Standalone MCP Client node
n8n also offers a standalone MCP Client node (not the Tool variant) for calling MCP tools directly in non-AI workflows. Configure it the same way with Bearer authentication.
Option B: HTTP Request node (REST API)
For traditional automation workflows without AI agents, use the HTTP Request node with FeedNest’s REST API.
- 1
Add an HTTP Request node
In your workflow, add an HTTP Request node.
- 2
Configure the request
Fill in the following fields:
Method GET (or POST/PATCH/DELETE) URL https://feednest.com/api/v1/articlesAuthentication Generic Credential Type → Header Auth Header Name Authorization Header Value Bearer fn_live_... - 3
Test the request
Click Execute Node to verify the connection returns your articles.
Common REST API endpoints
GET /api/v1/articles — list articles
GET /api/v1/feeds — list feeds
GET /api/v1/saved — list saved articles
GET /api/v1/tags — list tags
POST /api/v1/articles/{id}/read — mark as read
POST /api/v1/articles/{id}/save — save article
Troubleshooting
For more help, see the general setup guide.