Content Fetcher FAQs

Question 1

Is the content tracking data persistent across restarts?

Accepted Answer

Yes, Content Fetcher persistently stores its content tracking data in a local configuration file (`~/.config/goose/content-fetcher-mcp/last_seen.json`) to ensure continuity even after server restarts.

Question 2

What is Content Fetcher?

Accepted Answer

Content Fetcher is a tool that automates fetching and tracking of new content from YouTube channels, RSS feeds, and GitHub repositories, primarily designed for seamless integration with the Goose platform.

Question 3

Which content sources can Content Fetcher monitor?

Accepted Answer

It can monitor YouTube channels for new videos, any RSS feed URL for blog posts, and specified GitHub repositories for new software releases.

Question 4

How does Content Fetcher help identify new content?

Accepted Answer

Content Fetcher tracks all previously seen content. You use its `isNewContent` tool to check if an item is genuinely new before processing, ensuring you only engage with fresh updates.

Question 5

How does Content Fetcher integrate with the Goose platform?

Accepted Answer

It functions as an MCP server using stdio transport, allowing you to easily register and configure it as a local MCP server within your Goose platform settings.

Content Fetcher

Content Fetcher

Key Features

Use Cases

Key Features

Use Cases