Dev.to (Forem API) MCP for AI. Manage all your developer community content.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Dev.to (Forem Developer Community API) manages your entire developer content presence. You can publish new articles, update drafts, list all user comments, and track engagement metrics—all directly from your AI agent.
This MCP lets you treat your community writing like it's right in your workspace.
What your AI can do
Create article
Generates a new blog article draft on Dev.to.
Create display ad
Creates a display advertisement for the platform.
Create page
Builds a new static page on the Dev.to site.
Write new posts or change existing content by creating drafts and updating published pieces.
Fetch, list, and manage all comments on your articles to monitor audience reaction.
Retrieve detailed information about users, organizations, followers, or even pages within the Dev.to ecosystem.
Search for articles using tags or paths, and list all available resources like podcast episodes and display ads.
If authorized, you can suspend users or unpublish entire articles directly through your agent.
Ask an AI about this
Waiting for input…
Dev.to (Forem Developer Community API) 36 Tools
These tools give you full programmatic access to every function on the platform, from creating articles to managing user profiles and tracking site activity.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Dev.to (Forem Developer Community API) on VinkiusCreate Article
Generates a new blog article draft on Dev.to.
Create Display Ad
Creates a display advertisement for the platform.
Create Page
Builds a new static page on the Dev.to site.
Create Reaction
Adds a reaction (like or heart) to content.
Delete Page
Removes an existing page by its ID.
Get Article By Path
Fetches an article by the user's name and the post's URL slug.
Get Article
Retrieves a specific article using its unique ID.
Get Comment
Gets a single comment using its ID number.
Get Display Ad
Retrieves details for an advertisement by its ID.
Get Me
Pulls your own authenticated user profile data.
Get Organization
Gets the profile details for a specified organization.
Get Page
Retrieves the content of a specific page by its ID.
Get Profile Image
Gets the profile picture for any user using their username.
Get User
Retrieves a complete user profile by providing their unique ID.
List Articles
Lists all published articles available on the platform.
List Comments
Fetches a list of comments that have been left on content.
List Display Ads
Lists all active display advertisements currently running.
List Followed Tags
Shows a list of tags you are tracking or following on the site.
List Followers
Gets a list of users who follow your profile.
List My All Articles
Lists every article you've ever created, published or otherwise.
List My Articles
Shows a general list of all articles associated with your account.
List My Published Articles
Gets only the articles you've successfully published to the public.
List My Unpublished Articles
Lists your drafts and unpublished content that isn't live yet.
List Organization Articles
Retrieves a list of articles created by an entire organization.
List Organization Users
Lists all user accounts belonging to a specific organization.
List Pages
Fetches a list of every page created on the Dev.to site.
List Podcast Episodes
Lists all podcast episodes that have been released.
List Reading List
Shows the contents of your personalized reading list.
List Tags
Retrieves a complete index of all tags used across the community.
List Videos
Lists articles that contain video content.
Suspend User
Suspends a user's account (requires admin rights).
Toggle Reaction
Adds or removes a reaction to content.
Unpublish Article
Takes an article and makes it private again (admin/moderator tool).
Update Article
Changes the title, body, or status of an existing article.
Update Display Ad
Modifies the details of an existing advertisement.
Update Page
Edits the content or structure of a static page.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Dev.to (Forem Developer Community API), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Dev.to. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 36 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The headache of managing content across tabs and platforms
Today, publishing a single technical article is painful. You write it in your editor, copy the text, then switch to Dev.to's web interface. After hitting publish, you have to open another tab just to check comments, copy user names for follow-ups, and maybe manually update a related page or ad on the side of the site.
With this MCP, that whole process gets absorbed by your agent. You tell it what needs doing—'Draft an article about X, then check all existing drafts, and finally, list the top 10 comments.' The agent runs the sequence through its tools and gives you a unified report.
Get Content Management with `update_article`
You used to have to find an old article, click into the editor, manually fix paragraphs of text, save it as a draft, and then remember to hit publish. It was tedious clicking through multiple web forms.
Now, you just tell your agent: 'Update Article ID 123456 with this new section.' The tool handles the data injection and state change for you. Done.
What your AI can actually do with this
Your technical writing life just got a serious upgrade. Instead of bouncing between Dev.to and your editor to post content or check feedback, this connector gives your agent full control over your Forem account. You can create new articles from scratch using raw text and metadata. Need to respond to comments? Your agent grabs the latest discussions and lets you manage reactions or even draft replies.
It also helps you keep tabs on what's working by listing all published content, whether it's your own work or an organization's. When you connect this MCP through Vinkius, you get a complete picture of your developer community without ever leaving your AI client.
019e5d11-f288-714d-ba32-a3bfc2e16ea9 Here's how it actually works
The bottom line is that this MCP turns Dev.to’s complex API calls into natural conversation prompts within your AI client.
First, subscribe to the MCP and enter your Dev.to API key in your AI client's settings.
Next, tell your agent what you want to do—for example, 'List all my unpublished articles that mention Rust.'
Finally, your agent executes the necessary tools, fetches the data, and presents the results right back to you for review or action.
Who is this actually for?
This is for the developer advocate who's tired of manually checking comments across multiple tabs, or the content marketer who needs to publish a week's worth of articles before lunch. It’s built for people whose job revolves around keeping technical knowledge flowing.
Drafting and publishing new blog posts, managing drafts using tools like create_article, and updating old content with update_article.
Monitoring community feedback by listing comments (list_comments) and responding quickly via reactions or drafting replies to keep the conversation moving.
Tracking content performance across different sources, checking who follows an organization with list_followers, and managing cross-posted assets.
What Changes When You Connect
Publish and revise articles easily. Need to publish a new deep dive or adjust an old draft? You can use create_article and then run update_article against existing posts, keeping everything in one workflow.
Stay on top of community sentiment. Don't manually check comments across multiple tabs. Your agent fetches the latest discussions using list_comments, letting you address feedback immediately.
Build out your presence completely. Beyond articles, this MCP lets you manage static content (create_page), track who follows your organization (list_followers), and even list all associated podcast episodes.
Gain full visibility into your history. You don't have to remember if an article is live or just a draft. Running list_my_all_articles gives you one single source of truth for everything you've written.
Monitor the developer landscape. Use tools like get_user and list_organization_users to build out directories, check profile details, and understand who your core audience is.
See it in action
Updating a poorly received post.
A developer advocate finds that an article on 'Advanced React Hooks' got confused comments. Instead of manually logging into Dev.to, running get_article pulls the content, and your agent uses update_article to correct technical details and improve the introduction based on the feedback from list_comments.
Launching a new product feature announcement.
A content marketer wants to announce a new tool. They use create_article for the main blog post, then run get_organization and update_page simultaneously to make sure all related landing pages point to the correct, updated information.
Analyzing competitor activity.
You need to see what's popular. Your agent runs list_articles filtered by tags or popularity metrics and cross-references that data with who is following the organization using list_followers, giving you a content strategy map.
Cleaning up old, outdated posts.
You find several articles that are no longer accurate. Instead of manually finding each one and deleting it, your agent uses list_my_all_articles to pull the list, then iterates through them using unpublish_article.
The honest tradeoffs
Treating articles and pages as separate entities.
A user might try to update a page by calling update_page, but then forgets they also need to change the associated blog post. They end up with mismatched information across platforms.
Always check if you're modifying core content or structural elements. If it needs to be read like an article, use update_article. If it’s a static resource (like documentation), use update_page and remember to link them both.
Over-relying on profile names.
Relying only on the user's display name when trying to fetch data. If the username changes, your agent fails because it was looking up the wrong identifier.
When retrieving specific users or organizations, always use get_user and pass the unique ID, not just the visible name.
Ignoring drafts entirely.
Publishing an update without first checking for unpublished changes. The agent might only check list_my_published_articles, missing a crucial draft that needs final review before going live.
When It Fits, When It Doesn't
Use this MCP if your job requires managing the full lifecycle of developer content: drafting, publishing, tracking comments, and updating associated site elements. It's perfect for people who need to treat their blog like a single system, not a collection of separate web pages.
Don’t use it if you only need pure data retrieval (like reading user lists) without any writing or modification capability; in that case, simple read-only API connectors might suffice. Also, if your primary goal is solely internal company documentation and doesn't involve public posting to Dev.to, this MCP won't help—you’ll need a dedicated CMS integration instead.
Questions you might have
How do I use `list_my_all_articles`? +
Running list_my_all_articles gives a comprehensive list of every article you've ever written on Dev.to, whether it's published to the public or still sitting in your drafts.
Can I update an existing post using `update_article`? +
Yes. You must provide the specific ID of the article you want to change; otherwise, the tool won't know which piece of content to modify.
What is the difference between `list_my_articles` and `list_my_all_articles`? +
list_my_articles gives a general list, but list_my_all_articles provides the full history of everything you've ever created on Dev.to.
How do I check my followers using `list_followers`? +
You tell your agent to run list_followers for your profile, and it pulls a list of every user who has followed you on the platform.
What happens if I use `get_user` with an invalid ID? +
The MCP returns a clear error message. Your agent must check for this specific status code before trying to retrieve any data associated with the user, like their articles or followers.
What information is needed when I use `create_page`? +
You need at minimum a page title and body content. The tool accepts structured input for rich text formatting, allowing you to build pages that go beyond simple markdown articles.
How can I check available tags using `list_tags`? +
Yes, this command pulls a full list of every tag used in the community. This is useful for ensuring your new articles are accurately categorized before you publish them.
What permissions are required to run `list_organization_articles`? +
You need explicit Admin or Owner rights for that specific organization. The MCP will halt execution and flag an authorization failure if the API key lacks the necessary organizational permissions.
Can I see both my published and unpublished articles? +
Yes! You can use list_my_all_articles to see everything, or use specific tools like list_my_published_articles and list_my_unpublished_articles to filter your content.
How do I find the top articles for a specific tag like 'javascript'? +
Use the list_articles tool and provide 'javascript' in the tag parameter. You can also use the top parameter to find the most popular ones over a certain number of days.
Can I manage my reading list through the AI? +
You can retrieve your reading list using the list_reading_list tool, allowing your AI to summarize or organize articles you've saved for later.
We've already built the connector for Dev.to (Forem API). Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 36 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.