  "arguments": ["project_slug", "source_id", "confirmed"],
  "scope": "publish",
  "confirmation": "required"
},
"refresh_source": {
  "arguments": ["project_slug", "source_id", "confirmed"],
  "scope": "publish",
  "confirmation": "required"
}

}, "prompts": [], "resources": ["list_sources", "list_recent_captures"], "platforms": [] } -->

Sources

Manage the RSS feeds and sitemaps Syndly uses for news captures. The current MCP supports list, add, refresh, and remove. It does not expose source editing.

Workflow

Resolve the project. Read the selected project_slug from setup or ask the user to choose one.
List first. Call list_sources at the start of the session. Do not trust a previous session snapshot.
Match the request to a supported operation.
- List: Return the current sources. No confirmation is required.
- Add: Collect url, name, type (rss or sitemap), and optional topic. Show the exact values, then call add_source with confirmed: true after approval.
- Refresh: Show the selected source and explain that Syndly will make a network request and save new captures. Call refresh_source with confirmed: true after approval.
- Remove: Show the selected source. Optionally call list_recent_captures to show up to 50 recent captures for context. Call remove_source with confirmed: true only after approval.
- Edit: Explain that editing is not available. Offer remove-and-add as two separately confirmed operations.
Report the server result. Preserve the exact returned error when a call fails.

Safety rules

Include project_slug in every call.
Do not claim that sources can be edited or assigned a crawl schedule.
Do not batch destructive operations behind one confirmation.
Do not retry a rejected confirmation.

syndly-sources