You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An agent can make a feed and publish to it over MCP (list_feeds, create_feed, publish_to_feed), and automations have MCP tools (automations, save_automation, test_automation, run_automation). Routines and graph workflows have none: an agent that wants "every Monday, make a podcast episode about the week's new resources and put it in my feed" has to call the REST API (POST /api/v1/workflows, POST /api/v1/workflows/test, POST /api/v1/routines, POST /api/v1/routines/{rid}/run).
Found while building the graph nodes that publish to feeds (#547). AGENTS.md principle 1 (agent-first) asks for an MCP or assistant-tool path for everything a person does in the web app.
What would close it: MCP tools to list routines with their schedule and last run, save one (name, schedule, namespaces, workflow or graph), try a graph workflow without keeping anything, and run a routine now, with the same admin and write-scope checks as the routes. Docs in docs/mcp.md and a test next to test_mcp.py's write-tool list.
Activity