Fetch content from URLs, parse RSS feeds, rewrite and transform text, import to drafts, bulk import from feeds, extract sitemap URLs.
Most content jobs start somewhere else — a feed, a sitemap, a page you need to rework. Copy and paste is where that goes wrong at any volume.
Pull a page's content in as text an agent can actually work with.
Parse a feed into items rather than scraping a rendered page.
Reshape the text before it lands, not after it is already published.
Imports arrive as drafts, so nothing goes live without a human deciding.
Take a whole feed in one operation instead of one item at a time.
Pull every URL out of a sitemap when you need the full picture of a site.
Point the agent at a URL, a feed or a sitemap and the Content Fetcher brings it in — parsed, rewritten if you want, and saved as drafts.
Turn a feed you follow into a set of drafts to work from.
Pull a sitemap to see everything a site publishes before a migration.
Fetch, rewrite in your own voice, and keep it as a draft for review.
Chain fetching and rewriting into a repeatable research workflow.
The Content Fetcher is built into NibWP and lets any MCP-compatible AI agent — Claude, Cursor, Claude Code and others — bring outside material into WordPress.
Research and migration work both start the same way: something exists elsewhere and needs to end up here, usually reshaped on the way. Doing that by hand is copy, paste, reformat, repeat, and it stops scaling around the tenth item.
Everything imported lands as a draft. An agent can fetch a hundred items and rewrite every one of them without a single thing appearing on your site until you say so.
| Tool | Type | What it does |
|---|---|---|
| nibwp/fetch-url-content | read | Fetch and extract the content of a URL. |
| nibwp/fetch-rss-feed | read | Parse an RSS feed into structured items. |
| nibwp/fetch-sitemap-urls | read | Extract every URL from a sitemap. |
| nibwp/fetch-rewrite-content | write | Rewrite or transform fetched text before it is stored. |
| nibwp/fetch-to-draft | write | Save fetched content as a WordPress draft. |
| nibwp/fetch-bulk-import | write | Import a whole feed as drafts in one pass. |
No. The Content Fetcher is built into NibWP and available on every plan, including Free.
No. Imports arrive as drafts. Publishing stays a decision someone makes.
That is your call and your responsibility. The tools fetch and transform; whether you have the right to publish the result is not something software can decide for you.
Yes. Bulk import takes the feed in one operation rather than item by item.
Activate the integration and it's live on your MCP endpoint instantly.