このMCPでできること
Aggregates RSS feeds, newsletters, and monitored web searches into personalized AI news briefings with source management, feedback, and research requests.
機能
ツール
28
ツール
add_feed
Add an RSS feed
Add an RSS/Atom feed to a topic inbox. You can pass the site address instead of the feed URL — the server fetches the page and discovers the feed. If it fails, the reason is precise (blocked by the site, gone, unreadable) so it can be reported honestly.
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['source_id', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Feed URL or plain site address, e.g. "ilpost.it"'}, 'source_id': {'type': 'string', 'description': 'Which inbox (from list_sources)'}}, 'additionalProperties': False}
add_web_search
Monitor a web search
Monitor a Google query every day and feed the results into a topic inbox: the standing-search way to follow a company, a person, a law or a niche subject that has no RSS feed. kind "news" watches the news index, "search" the whole web.
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['source_id', 'query'], 'properties': {'kind': {'enum': ['news', 'search'], 'type': 'string', 'description': 'Default news'}, 'query': {'type': 'string', 'description': 'The query, as you would type it into Google'}, 'source_id': {'type': 'string', 'description': 'Which inbox (from list_sources)'}}, 'additionalProperties': False}
correct_briefing
Correct the briefing in plain words
Tell the briefing what was wrong with it, in plain language — "too much crypto and not enough on the EU regulation", "keep it shorter", "explain the technical parts more simply", "follow this story". An AI editor reads the note against the actual briefing and turns it into concrete adjustments: topic preferences, settings, deep-dive requests. This is the main way a person retunes their news feed by talking.
入力スキーマ
{'type': 'object', 'required': ['note'], 'properties': {'note': {'type': 'string', 'description': 'What was wrong or what they want changed, in their own words'}, 'entry_id': {'type': 'string', 'description': 'Optional: the specific story the note is about (entry id from get_briefing)'}, 'briefing_id': {'type': 'string', 'description': 'Which briefing the note refers to. Omit for the latest.'}}, 'additionalProperties': False}
create_source
Create a topic inbox
Create a new topic inbox: a themed container with its own dedicated email address (subscribe newsletters to it), which can hold RSS feeds and monitored web searches. This is how you add a whole new subject to someone's information diet.
入力スキーマ
{'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': 'Short name, e.g. "AI research" or "Local news"'}, 'description': {'type': 'string', 'description': 'Optional brief: what the reader expects from this inbox and what to skip — the editor reads it at every briefing'}}, 'additionalProperties': False}
delete_source
Delete a topic inbox
Permanently delete a topic inbox with all its feeds, searches and collected content. Irreversible: the dedicated email address stops working too. Prefer update_source with is_active false when in doubt.
破壊的操作あり
冪等
入力スキーマ
{'type': 'object', 'required': ['source_id'], 'properties': {'source_id': {'type': 'string', 'description': 'Id from list_sources'}}, 'additionalProperties': False}
discover_sources
Find sources for a subject
Describe a subject in plain words and get back real, working sources for it: RSS feeds validated live by the server (dead ones are dropped before you see them), web searches worth monitoring, and newsletters worth subscribing to. Nothing is added — it returns proposals to pass to add_feed / add_web_search.
読み取り専用
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['source_id', 'description'], 'properties': {'source_id': {'type': 'string', 'description': 'The inbox the proposals are for (its existing sources are excluded)'}, 'description': {'type': 'string', 'description': 'What they want to follow, in plain words'}}, 'additionalProperties': False}
generate_briefing
Generate a briefing now
Generate a briefing immediately instead of waiting for the scheduled time, using everything collected so far. Costs real AI money and takes a couple of minutes, so use it only when explicitly asked. Returns the id to poll with get_briefing.
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
get_account
Account and usage
Account status: plan, whether the briefing is currently running, when the next one is due, how many sources and stories are in the system, and the AI cost accrued this month.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
get_briefing
Read the daily briefing
Read the user's personal AI-written news briefing (daily digest) in full markdown: every story selected today from their newsletters, RSS feeds and monitored web searches, with sources. Returns the latest briefing by default, or a specific one by id or date. Also returns an index of entry ids, needed to rate or correct individual stories.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {'briefing_id': {'type': 'string', 'description': 'Specific briefing id (from list_briefings). Omit for the latest.'}, 'include_markdown': {'type': 'boolean', 'description': 'Include the full text. Default true; set false for just the index.'}}, 'additionalProperties': False}
get_information_diet
Read the information diet
Read everything that shapes what reaches this person: delivery schedule, length, technicality, depth, stance and tone, stated interests and no-go topics, the profile the system has learned about them, the per-topic preferences built from their feedback (affinity, muted, followed themes) and the specific stories they pinned with "follow" (every development of those gets reported). This is the full picture of their news filter — read it before changing anything.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
get_podcast_episode
Get the podcast episode
Get the audio episode generated from a briefing: a private podcast narrated in the user's language, with a playable URL and the show notes listing every source. Returns the latest episode by default.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {'briefing_id': {'type': 'string', 'description': 'Episode of a specific briefing. Omit for the latest.'}}, 'additionalProperties': False}
get_source
Inspect one source
Inspect one topic inbox in detail: every RSS feed (with its health and last fetch), every monitored web search, X/Twitter profiles, and the newsletters currently arriving at its dedicated address. Use it before removing or reorganising anything.
読み取り専用
入力スキーマ
{'type': 'object', 'required': ['source_id'], 'properties': {'source_id': {'type': 'string', 'description': 'Id from list_sources'}}, 'additionalProperties': False}
import_opml
Import an OPML subscription file
Import subscriptions from another RSS reader (Feedly, Inoreader, FreshRSS, NetNewsWire) by passing the OPML file contents. Set dry_run true first to see what is in it and what is already present; then run it for real to add them (they are validated one by one, and the ones that fail come back with the reason).
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['source_id', 'opml'], 'properties': {'opml': {'type': 'string', 'description': 'The full OPML/XML file contents'}, 'limit': {'type': 'integer', 'maximum': 40, 'minimum': 1, 'description': 'Max feeds to add in this call (default 20 — big imports go in batches)'}, 'dry_run': {'type': 'boolean', 'description': 'true = only list what would be imported'}, 'source_id': {'type': 'string', 'description': 'Which inbox to import into'}}, 'additionalProperties': False}
list_briefings
List past briefings
List the user's past daily briefings (most recent first) with date, title, number of stories and whether an episode exists. Use it to find the id of a specific day before reading or correcting it.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {'limit': {'type': 'integer', 'maximum': 50, 'minimum': 1, 'description': 'How many, default 10'}}, 'additionalProperties': False}
list_deep_dives
List pending deep dives
List the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
list_read_later
List the read-later queue
List what is queued in the read-later inbox: links and forwarded emails that are guaranteed to be covered in the next briefing.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
list_sources
List information sources
List the topic inboxes this person feeds their briefing with: each one has a dedicated email address for newsletter subscriptions, plus RSS feeds and monitored web searches. Shows how much each produced recently, its priority and whether it is included in the briefing.
読み取り専用
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
rate_briefing_entry
Rate one story
Give a precise up/down signal on one story of a briefing: more like this, less like this, more technical, simpler, deeper, shorter, or mute its topics. These apply to the topics of that story, so the next briefing weighs them differently. A story usually has several topics: pass `topics` to hit only some of them (e.g. "less" of "demographics" but not of "japan"). Sending the same signal again with different topics REPLACES the previous one: the topics you drop are restored, nothing is double-counted. "follow" is different: it pins THIS story — from then on every development of this specific story (and only of it) gets a full entry flagged as an update; "unfollow" releases it. Pinned stories are listed by get_information_diet.
入力スキーマ
{'type': 'object', 'required': ['entry_id', 'signal'], 'properties': {'signal': {'enum': ['more', 'less', 'more_technical', 'simpler', 'deeper', 'shorter', 'more_often', 'less_often', 'mute', 'follow', 'unfollow'], 'type': 'string', 'description': 'The signal to record'}, 'topics': {'type': 'array', 'items': {'type': 'string'}, 'maxItems': 5, 'description': 'Only these topics of the story (as listed by get_briefing). Omit to apply to all of its topics.'}, 'entry_id': {'type': 'string', 'description': 'Entry id from get_briefing'}, 'briefing_id': {'type': 'string', 'description': 'Which briefing. Omit for the latest.'}}, 'additionalProperties': False}
remove_feed
Remove an RSS feed
Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it.
破壊的操作あり
冪等
入力スキーマ
{'type': 'object', 'required': ['feed_id'], 'properties': {'feed_id': {'type': 'string', 'description': 'Id from get_source'}}, 'additionalProperties': False}
remove_web_search
Stop monitoring a search
Stop monitoring a standing web search: no new results from that query will reach the briefing. What it already collected stays where it is.
破壊的操作あり
冪等
入力スキーマ
{'type': 'object', 'required': ['search_id'], 'properties': {'search_id': {'type': 'string', 'description': 'Id from get_source'}}, 'additionalProperties': False}
report_missing_story
Ask why a story was missing
The reader expected a story and the briefing did not have it. Describe it in their words; the editor investigates their own sources of the last days, today's briefing, their preferences and a web search, and answers with a verdict: it was in the briefing, none of their sources carried it (and proposes the missing source), it was dropped because of a preference (and corrects it), it was seen but undervalued, or it could not be found. Topics get followed so similar stories do not slip again; a deep-dive may be queued for the next briefing. Five per day.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'What story they expected, in their own words'}, 'briefing_id': {'type': 'string', 'description': 'Which briefing it was missing from. Omit for the latest.'}}, 'additionalProperties': False}
request_deep_dive
Queue a deep dive
Ask the next briefing to investigate a topic properly, with fresh web research: it will include a mini-dossier with sources. Use it whenever the person says "I want to know more about X" or "keep digging on this".
冪等
入力スキーマ
{'type': 'object', 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': 'The question or topic to research'}}, 'additionalProperties': False}
save_for_later
Save something into the next briefing
Put a link or a note into the read-later queue: whatever lands there is guaranteed to be covered in the next briefing. The page is fetched and its text stored, so it can be summarised even if the site later blocks access.
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'The link to save'}, 'text': {'type': 'string', 'description': 'Alternative to url: a free-text note to keep'}, 'title': {'type': 'string', 'description': 'Optional title for a text note'}}, 'additionalProperties': False}
set_learned_profile
Rewrite the learned profile
Read or rewrite the free-text profile the briefing uses to know who this person is — their work, projects, recurring interests, what they already know. Appending is usually better than replacing: pass mode "append" to add a line.
破壊的操作あり
入力スキーマ
{'type': 'object', 'required': ['text'], 'properties': {'mode': {'enum': ['append', 'replace'], 'type': 'string', 'description': 'Default append'}, 'text': {'type': 'string', 'description': 'The profile text, or the line to add'}}, 'additionalProperties': False}
tune_topic
Tune one topic
Tune how a single topic is treated in future briefings: more or less of it, more or less technical, deeper or shorter, more or less often, muted entirely, or followed so every development of that WHOLE THEME gets reported (to follow one specific story, use rate_briefing_entry with "follow" on that entry). This is the precise instrument — for a vague comment like "too much crypto lately" use correct_briefing instead.
入力スキーマ
{'type': 'object', 'required': ['topic', 'action'], 'properties': {'topic': {'type': 'string', 'description': 'The topic, as it appears in get_information_diet or in a briefing entry (e.g. "intelligenza artificiale")'}, 'action': {'enum': ['more', 'less', 'more_technical', 'simpler', 'deeper', 'shorter', 'more_often', 'less_often', 'mute', 'unmute', 'follow', 'unfollow'], 'type': 'string', 'description': 'What to change about it'}}, 'additionalProperties': False}
unsubscribe_newsletter
Unsubscribe from a newsletter
Unsubscribe from a newsletter arriving in one of the inboxes. When the sender supports one-click unsubscribe the server does it directly; otherwise it returns the URL a human has to open, and says so honestly.
破壊的操作あり
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['newsletter_id'], 'properties': {'newsletter_id': {'type': 'string', 'description': 'Id from get_source (newsletters)'}}, 'additionalProperties': False}
update_information_diet
Change how the briefing is written
Change how and when the briefing reaches this person: delivery time and days, length, technicality, depth, stance, tone, stated interests and topics to avoid, language, timezone, podcast and email delivery. Pass only the keys you want to change. Read get_information_diet first — these are global settings, not per-topic ones (for a single topic use tune_topic).
冪等
入力スキーマ
{'type': 'object', 'properties': {'tone': {'type': 'string', 'description': 'come deve scrivere («diretto, zero fuffa»)'}, 'avoid': {'type': 'string', 'description': 'cosa non vuole leggere mai'}, 'depth': {'type': 'integer', 'maximum': 5, 'minimum': 1, 'description': '1 solo i fatti … 5 analisi e implicazioni'}, 'stance': {'type': 'integer', 'maximum': 5, 'minimum': 1, 'description': "1 neutro … 5 l'editor si sbilancia"}, 'language': {'enum': ['it', 'en', 'es', 'de', 'fr'], 'type': 'string', 'description': 'lingua del briefing e del podcast'}, 'timezone': {'type': 'string', 'description': 'fuso orario IANA (Europe/Rome)'}, 'entry_mix': {'type': 'integer', 'maximum': 5, 'minimum': 1, 'description': '1 poche voci trattate a fondo … 5 tante voci brevi (la lunghezza totale non cambia)'}, 'interests': {'type': 'string', 'description': 'cosa seguire, in linguaggio naturale'}, 'digest_days': {'type': 'array', 'items': {'type': 'integer', 'maximum': 7, 'minimum': 1}, 'description': 'giorni della settimana, ISO 1=lunedì … 7=domenica'}, 'digest_time': {'type': 'string', 'description': "orario di consegna, HH:MM nel fuso dell'utente"}, 'technicality': {'type': 'integer', 'maximum': 5, 'minimum': 1, 'description': '1 divulgativo … 5 da addetti ai lavori'}, 'digest_length': {'enum': ['short', 'medium', 'long', 'xlong', 'full'], 'type': 'string', 'description': 'quanto deve essere lungo'}, 'serper_enrich': {'type': 'boolean', 'description': 'arricchire il briefing con ricerche web fresche'}, 'chicca_enabled': {'type': 'boolean', 'description': "nei giorni senza notizie, una storia vera dall'archivio"}, 'digest_enabled': {'type': 'boolean', 'description': 'ricevere o meno il briefing quotidiano'}, 'podcast_accento': {'enum': ['us', 'gb', 'au', 'ie', 'in', 'es', 'latam', 'fr', 'ca', 'de', 'at', 'ch'], 'type': 'string', 'description': "accento della voce, per la lingua scelta: inglese us/gb/au/ie/in, spagnolo es/latam, francese fr/ca, tedesco de/at/ch (l'italiano non ha varianti)"}, 'podcast_enabled': {'type': 'boolean', 'description': "generare anche l'episodio audio"}, 'podcast_formato': {'enum': ['show', 'classico'], 'type': 'string', 'description': 'show = due conduttori che si rispondono (il formato di casa); classico = una voce che legge il briefing'}, 'podcast_minutes': {'type': 'integer', 'maximum': 20, 'minimum': 2, 'description': "durata desiderata dell'episodio"}, 'email_digest_enabled': {'type': 'boolean', 'description': 'ricevere il briefing anche per email'}, 'smalltalking_enabled': {'type': 'boolean', 'description': 'ogni giorno, in coda al briefing, due o tre storie brevi da raccontare'}, 'weekly_recap_enabled': {'type': 'boolean', 'description': 'riepilogo settimanale di ciò che non è stato letto'}}, 'description': 'Any subset of the settings.', 'additionalProperties': False}
update_source
Update a topic inbox
Change a topic inbox: rename it, change its description, raise or lower its priority in the briefing, set a per-inbox technicality level, temporarily exclude it from the briefing or pause it entirely.
冪等
入力スキーマ
{'type': 'object', 'required': ['source_id'], 'properties': {'name': {'type': 'string', 'description': 'New name for the inbox'}, 'priority': {'type': 'integer', 'maximum': 5, 'minimum': 1, 'description': '1 marginal … 5 always first'}, 'is_active': {'type': 'boolean', 'description': 'false = stop collecting entirely'}, 'source_id': {'type': 'string', 'description': 'Id from list_sources'}, 'description': {'type': 'string', 'description': 'The inbox brief: what the reader expects from it and what to skip — the editor reads it at every briefing'}, 'technicality': {'type': 'integer', 'maximum': 5, 'minimum': 1, 'description': 'Override just for this inbox'}, 'include_in_digest': {'type': 'boolean', 'description': 'false = keep collecting but leave it out of the briefing'}}, 'additionalProperties': False}
履歴
最近のツール変更
変更
rate_briefing_entry
2026年9月19日2:52
変更
tune_topic
2026年9月19日2:52
変更
get_information_diet
2026年9月19日2:52
追加
unsubscribe_newsletter
2026年9月17日12:37
追加
import_opml
2026年9月17日12:37
追加
discover_sources
2026年9月17日12:37
追加
remove_web_search
2026年9月17日12:37
追加
add_web_search
2026年9月17日12:37
追加
remove_feed
2026年9月17日12:37
追加
add_feed
2026年9月17日12:37
追加
delete_source
2026年9月17日12:37
追加
update_source
2026年9月17日12:37
追加
create_source
2026年9月17日12:37
追加
generate_briefing
2026年9月17日12:37
追加
save_for_later
2026年9月17日12:37
追加
request_deep_dive
2026年9月17日12:37
追加
set_learned_profile
2026年9月17日12:37
追加
report_missing_story
2026年9月17日12:37
追加
rate_briefing_entry
2026年9月17日12:37
追加
correct_briefing
2026年9月17日12:37
追加
tune_topic
2026年9月17日12:37
追加
update_information_diet
2026年9月17日12:37
追加
get_account
2026年9月17日12:37
追加
list_deep_dives
2026年9月17日12:37
追加
list_read_later
2026年9月17日12:37
追加
get_podcast_episode
2026年9月17日12:37
追加
get_source
2026年9月17日12:37
追加
list_sources
2026年9月17日12:37
追加
get_information_diet
2026年9月17日12:37
追加
list_briefings
2026年9月17日12:37
関連MCP
類似のMCPサーバー
mu
mu.micro/mu
Supports personal and collaborative tasks including web browsing, app creation, blogs, bookmarks, discussions, and contact manage…
Timeapi Io
io.github.pipeworx-io/timeapi-io
Provides timezone and date utilities, along with routed access to structured research and data sources.
Asana
io.github.pipeworx-io/asana
Manages Asana workspaces, projects, tasks, and task search, while also providing routed data research and AI brand-visibility che…
Afrotech.guide
io.github.yadasa/afrotech-guide
Searches and plans AfroTech conference events, sessions, jobs, companies, attendees, food, networking targets, and saved itinerar…
remoet-mcp
io.github.remoet-labs/remoet-mcp
Searches and tracks technology jobs and companies, manages saved jobs and profiles, supports applications, and creates link-tree …
netcafe-docs
com.ainetcafe/netcafe-docs
Extracts and validates data from PDFs, invoices, bank statements, tables, and CSVs; also supports web research, document conversi…
getjobzi-mcp
io.github.getjobzi/getjobzi-mcp
Searches UK jobs and supports resume analysis, job matching, cover letters, career planning, skill-gap analysis, and salary bench…
CaseMagic — Court Case Monitor
io.github.sustany/casemagic
Finds and monitors U.S. federal court cases, retrieves docket filings and deadlines, stores case records and supports reviewed ca…