Curated audio-news: search articles, narrated audio, vertical briefings, topic subscriptions.
Most developer tooling work still happens through a UI a human drives. Storyflo MCP server moves it into the conversation instead. Curated audio-news: search articles, narrated audio, vertical briefings, topic subscriptions.
Official Model Context Protocol server for Storyflo — curated audio news + daily briefings + the public Declassified library (FBI/CIA/NSA/NASA/DOJ/AARO releases) + market-linked story signals, all exposed as a callable surface for any LLM agent.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 14 tools. What each one is for:
search_articles — search the curated article corpus by query/verticalget_article — fetch the full record + body text + audio URL by slugget_audio_url — resolve the playable audio URL for an articleget_trending_topics — what's hot on Storyflo right nowget_personas — the host voices (Theo / Mason / Riley / Iris / Brock / Wit)get_vertical_landscape — one-shot per-vertical context for onboarding a listenerlist_podcasts — the full catalog of audio shows (per-host + Declassified)digest — top-N articles aggregated across verticals for a windowget_market_linked_stories — stories matched to Kalshi event contracts (editorial, not advice)get_crypto_market_link — Kraken affiliate markets link-out for crypto-relevant storiessearch_declassified — substring search across the Declassified case archiveget_declassified_case — full Declassified case record by slugConfiguration is passed through the environment: STORYFLO_TOKEN, STORYFLO_MCP_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Storyflo's toolset — search_articles, get_article, get_audio_url and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Alisammour; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_articles | search the curated article corpus by query/vertical |
| get_article | fetch the full record + body text + audio URL by slug |
| get_audio_url | resolve the playable audio URL for an article |
| get_trending_topics | what's hot on Storyflo right now |
| get_personas | the host voices (Theo / Mason / Riley / Iris / Brock / Wit) |
| get_vertical_landscape | one-shot per-vertical context for onboarding a listener |
| list_podcasts | the full catalog of audio shows (per-host + Declassified) |
| digest | top-N articles aggregated across verticals for a window |
| get_market_linked_stories | stories matched to Kalshi event contracts (editorial, not advice) |
| get_crypto_market_link | Kraken affiliate markets link-out for crypto-relevant stories |
| search_declassified | substring search across the Declassified case archive |
| get_declassified_case | full Declassified case record by slug |
| digest_declassified | most-recently-published Declassified cases over a window |
| subscribe_topic | mint/update a personal podcast RSS feed scoped to verticals |
{
"mcpServers": {
"storyflo": {
"command": "npx",
"args": ["-y", "storyflo-mcp"],
"env": { "STORYFLO_TOKEN": "<optional bearer>" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| STORYFLO_TOKEN | Credential the server authenticates with. | Yes |
| STORYFLO_MCP_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.