Curated
Curated is a platform that enables users to collect, curate, and publish newsletters, integrating with various services through its API.
Verdict
Common use cases
- Draft next week's newsletter from chat
- Add curated links to upcoming issue
- Check subscriber growth before campaign
- Review recent issues for content gaps
- Coordinate editorial calendar across team
Integration
- Vendor
- Curated
- Category
- other
- Auth
- API_KEY
- Tools
- 6
- Composio slug
curated
Tools
- Create Collected Link
Tool to create a collected link for a publication. use when you want to add a new link (with url, title, etc.) to a publication's collection.
- Create Draft Issue
Tool to create a draft issue for a publication. use after confirming the publication id. applies default settings if optional fields are omitted.
- List Categories
Tool to list all categories for a publication. use after you have the publication id and need to fetch its categories.
- List Email Subscribers
Tool to list all email subscribers for a publication. use after confirming the publication id.
- List Issues
Tool to list all issues for a publication. use after you have the publication id and need to fetch its issues (supports pagination).
- List Publications
Tool to list all publications accessible by the api key. use when you need to retrieve your publication ids for further api calls. example prompt: "list my publications".
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Curated in the MCP directory and click Connect. 3. Log into your Curated account at curated.co and go to Settings > API Keys. 4. Generate a new API key with permissions to read publications and write issues and links. 5. Copy the key and paste it into Switchy's connection dialog, then click Authorize. 6. Return to any Space and type '@Curated list my publications' to confirm the connection works. 7. You'll see your publication IDs, which you'll reference in future prompts. 8. To test creating content, try '@Curated create a draft issue for publication [ID]' and check your Curated dashboard to verify the draft appears.
What teammates see: by default, memories from Curated are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Publications
@Curated list my publications so I can see which ones are available to work with.Open in a Space →
Create Draft Issue
@Curated create a draft issue for publication ID 12345. Use default settings for now.Open in a Space →
Add Link to Collection
@Curated create a collected link for publication 12345 with URL https://example.com/article, title 'How to Scale Content Teams', and note 'Great resource on hiring writers'.Open in a Space →
Check Subscriber Count
@Curated list all email subscribers for publication 12345 so I can see our current audience size.Open in a Space →
Review Recent Issues
@Curated list the last 10 issues for publication 12345 so we can review what we've covered recently.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Curated list all my publications and show me the subscriber count for each one
Found 2 publications accessible with your API key: 1. **Weekly Dev Digest** (ID: pub_abc123) - 1,247 email subscribers - Last issue published 3 days ago 2. **Product Updates** (ID: pub_xyz789) - 412 email subscribers - Last issue published 1 week ago Both publications are active. The subscriber counts reflect confirmed email subscribers only and exclude unsubscribed or bounced addresses.
This example combines two read operations: listing publications and fetching subscriber data. The MCP requires a valid API key with read permissions for both endpoints. Actual publication metadata and subscriber counts will vary by account. Use this workflow to audit your Curated properties before performing write operations.
@Curated add this link to my Weekly Dev Digest collection: https://example.com/new-framework with title 'New React Framework Released' in the Frameworks category
Successfully created collected link in **Weekly Dev Digest**: - **Title:** New React Framework Released - **URL:** https://example.com/new-framework - **Category:** Frameworks - **Status:** Collected (not yet published) - **Link ID:** link_def456 This link is now in your collection and can be included in your next draft issue. It won't appear in published issues until you explicitly add it to a draft and send that issue to subscribers.
This write operation demonstrates content curation workflow. The MCP creates a collected link but does NOT automatically publish it—you must add it to a draft issue separately. Requires API key with write permissions. If the specified category doesn't exist, the operation may fail or create the link without a category, depending on Curated's API behavior.
@Curated review the last 5 issues of Product Updates and draft a new issue that summarizes common themes across those releases
Analyzed the last 5 issues of **Product Updates** (spanning March 2024): **Common themes identified:** - Performance improvements (mentioned in 4/5 issues) - Mobile app updates (3/5 issues) - API versioning changes (2/5 issues) **Draft issue created** (ID: draft_ghi789): - **Subject:** Q1 2024 Recap: Performance & Mobile Focus - **Preview text:** This quarter we shipped major speed improvements and rebuilt our mobile experience - **Status:** Draft (not scheduled) The draft includes a synthesized intro paragraph highlighting these themes. Review and edit the draft in Curated before scheduling it for delivery.
This synthesis example chains multiple MCP operations: fetching historical issues, analyzing content with AI reasoning, then creating a new draft. The AI's thematic analysis is interpretive—verify accuracy before sending. Draft creation uses Curated's default settings (template, send time). Requires both read and write API permissions.
Use-case deep-dives
When Curated fits a small editorial team's newsletter workflow
A 3-person content team ships a weekly industry roundup to 2,000 subscribers. They collect links in Slack all week, then spend 90 minutes Friday morning assembling the draft in Curated. This MCP is the right call if you want AI to handle the grunt work: paste a URL, the agent creates the collected link with metadata; ask for subscriber count, it pulls the list; request a draft issue, it scaffolds the template. The 6-tool scope covers the full publish cycle without touching the Curated UI. The trade-off: if your team needs custom layouts or A/B subject lines, you'll still open the dashboard for final edits. This works best when your newsletter format is stable and the bottleneck is link entry, not design iteration.
Using Curated to automate help-article newsletters at scale
A 5-person support team at a B2B SaaS company sends a monthly digest of new help docs and feature announcements to 8,000 users. They maintain three publications (one per product tier) and want AI to draft issues by pulling recent articles from Notion. The Curated MCP handles the multi-publication setup well: list publications to confirm IDs, then create draft issues with category tags pulled from the List Categories tool. The API key auth means the agent can run unattended in a scheduled workflow. The boundary: if you need to merge content from multiple sources or apply conditional logic (e.g., only send tier-specific features), you'll script that upstream before the MCP creates the draft. This is a win when the newsletter structure is predictable and you're batching 10+ links per issue.
When Curated is overkill for a founder's monthly investor memo
A solo founder sends a monthly update to 40 angel investors, including 3-5 press mentions and a metrics snapshot. Curated's MCP can create collected links and draft the issue, but the 6-tool overhead doesn't justify the setup if you're only sending 12 emails a year to a static list. The List Email Subscribers tool is useful if your investor base grows past 100 and you need to audit who's subscribed, but below that threshold a shared Google Doc or a plain Substack post is faster. The MCP makes sense if you're also running a public-facing newsletter on the same Curated account and want to reuse the link collection across both audiences. Otherwise, skip the integration and use a lighter tool.
Frequently asked
What does the Curated MCP do in Switchy?
It connects your Curated newsletter publications to Switchy's AI workspace. Your team can list publications, create draft issues, add collected links, fetch categories, and pull subscriber lists — all through natural language prompts. Useful if you're managing multiple newsletters and want AI to help with content curation or issue prep without switching tabs.
Do I need admin access to connect Curated?
You need a Curated API key with write permissions to the publications you want to manage. Curated issues API keys per user, so whoever connects it in Switchy controls which publications the team can access. If your key only has read access, you'll be able to list issues and subscribers but not create drafts or add links.
Can the Curated MCP publish issues or send newsletters?
No. It creates draft issues and adds collected links, but it won't publish or send anything. You still approve and send newsletters from Curated's own interface. Think of this MCP as a content-prep assistant — it stages work for you, but the final send button stays in your hands.
Why use this instead of Curated's web app directly?
Speed and context. If your team already works in Switchy for research or content planning, the MCP lets you add links or draft an issue without leaving the conversation. You skip the tab-switching and manual copy-paste. For one-off tasks, the web app is fine; for repetitive curation workflows, the MCP saves time.
Who on the team should connect the Curated MCP?
Whoever owns the Curated account and has an API key. Once connected, anyone in your Switchy workspace can use the tools, so they'll inherit that person's publication access. If you have multiple editors, connect the key that covers all the publications your team needs to manage together.