Your podcast, available to ask.
StoryFunnels speaks MCP — the open standard for connecting an assistant to a tool. Point whichever one you use at a single URL and the whole product answers in conversation, on your real episodes.
- 01
Paste the URL
mcp.storyfunnels.ai
- 02
Tick what it may touch
workspace and scopes
- 03
Ask for the work
nothing installed
We test against Claude; any client that implements MCP with OAuth connects exactly the same way.
Server URL
https://mcp.storyfunnels.ai
|
- transcribe_episode48:30
- generate_chapters7
- generate_shorts6 clips
- plan_schedule18 posts
You do not have to learn tool names.
Each brief knows the running order, and where it has to stop and ask you.
It reaches only what you tick.
This is the screen you see when you connect. Try the toggles — it is the real list, in the product’s own words.
- Checked on every call
- Expiry, revocation, and that the token was issued for this server and no other.
- Destructive tools are marked
- Anything that deletes or publishes says so, so your client can ask first.
- Revoke and it stops
- The next call fails. There is no cached copy of your permission.
Prefer to write the call yourself? The same surface is a REST API with keys, the same scopes and the same limits.
Workspace
James Cook Media
A scope you leave off is not refused later — those tools are never offered to the model at all.