Dev.to/Forem MCP for AI. Manage your entire published portfolio from chat.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Dev.to (Forem) MCP connects your AI agent to manage technical content and community profiles across Dev.to and Forem. You can list existing articles, draft new posts with markdown support, update drafts, or check user details directly from chat.
It handles the whole article lifecycle, letting you manage everything from drafting code examples to publishing full-stack tutorials without ever leaving your IDE.
What your AI can do
Create article
Drafts and publishes an entirely new technical article on Dev.to/Forem.
Get article by id
Retrieves the full content of a single published article using its unique ID number.
Get article by path
Fetches an article's data when you know the user and the clean slug (URL path).
Drafts a brand new technical article or post on Dev.to/Forem directly through conversation.
Fetches the full details of an article using either its unique ID or its web path (username and slug).
Modifies the content of a published or draft article, supporting rich markdown formatting.
Retrieves details about yourself or any other user by their username or ID.
Lists articles and members associated with a specific community group or organization.
Ask an AI about this
Waiting for input…
Dev.to (Forem) MCP: 12 Tools
This collection of tools lets you manage the entire publishing lifecycle for Dev.to or Forem content, handling everything from creating new articles to auditing user profiles.
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) on VinkiusCreate Article
Drafts and publishes an entirely new technical article on Dev.to/Forem.
Get Article By Id
Retrieves the full content of a single published article using its unique ID number.
Get Article By Path
Fetches an article's data when you know the user and the clean slug (URL path).
Get Me
Pulls your own authenticated profile details, like username and full name.
Get User
Retrieves the profile information for any user by their unique ID or handle.
List Articles
Lists all articles that have been published and are currently live on the platform.
List My Articles
Shows a list of every article associated with your own account (drafts and published).
List Org Articles
Gets a listing of all articles published by an entire organization or group.
List Org Users
Lists the usernames and profiles of people who belong to a specific organization.
List Videos
Retrieves articles that contain embedded video content, making them easy to find.
Unpublish Article
Takes a specific article and takes it offline immediately (requires permissions).
Update Article
Replaces the content of an existing article with new text or markdown.
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), then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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 (Forem). 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 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing technical content means constantly switching tools.
Right now, if you draft an article in your IDE, publish it to Dev.to, and then need to check what posts the organization published last month, you open three different tabs: your editor, the CMS dashboard, and a spreadsheet for tracking names. You copy usernames into one place, hit 'Filter' on another, and paste content somewhere else.
With this MCP, that manual process vanishes. Your agent handles it all in one chat window. Need to check organizational posts? Ask the agent to `list_org_articles`. It gives you the data directly, letting you keep your focus where it belongs: writing.
Update an existing article with pinpoint accuracy.
If a client points out a mistake or you realize you missed a crucial section, the manual process is getting back into the CMS editor, locating the post by its path, and then carefully re-pasting all the new markdown content. It’s slow, error-prone, and interrupts flow.
Now, just give your agent the article's ID and the corrected content. The `update_article` tool replaces the old text with the new version in a single command. That’s it.
What your AI can actually do with this
This MCP lets you handle all of your technical writing and community interactions through natural conversation. You don't have to switch tabs or copy a URL into a separate CMS dashboard just to check an article status. Your agent can list published work, search for specific posts by tags, or even update existing content drafts using full markdown support—all within your chat environment.
This kind of direct access saves time and keeps your focus where it belongs: writing code. It's one thing to write a great tutorial; it’s another thing entirely to distribute it correctly. By connecting this MCP via Vinkius, you give your agent the necessary tools to manage article drafts, inspect user profiles, and check organization membership right alongside your coding workflow.
019e3889-9fd2-733e-aa59-22cae7ef2aba Here's how it actually works
The bottom line is that it routes complex publishing tasks through simple conversation commands.
First, subscribe to this MCP on Vinkius and input your Dev.to/Forem API key.
Next, tell your AI agent what you need—for example, 'List all articles published by the Acme Corp organization.'
Finally, the agent executes the necessary tool calls and returns a structured list of content or user data into your chat.
Who is this actually for?
This MCP serves the technical writer who hates context switching, the community manager burdened by manual content audits, and the developer needing to programmatically query platform data. It's for anyone whose job requires moving between writing code/docs and managing the public-facing publication workflow.
Drafting articles on a topic, then using the MCP to check if similar posts already exist or list their own published works.
Auditing an organization's content by listing all articles associated with it and checking who the key contributors are.
Automating the retrieval of user profiles or published article data to feed into a metrics dashboard or documentation generator.
What Changes When You Connect
Draft and publish content without leaving your IDE. You can use create_article to draft a full piece, then immediately use update_article if you need to fix a citation or adjust the tone before publishing.
Quickly audit user activity. Need to know who belongs to a group? Use list_org_users. Want to see what they posted? Run list_org_articles to get an instant overview of organizational content.
Deep dive into specific content. Don't rely on searching the frontend. You can fetch a single article using either get_article_by_id or get_article_by_path, which is much faster for automated checks.
Full lifecycle control. If an article needs to come down temporarily, you don't have to manually delete it; just call unpublish_article and take it offline instantly.
Understand your own footprint. Use list_my_articles to see every piece of content associated with your account—both published work and drafts waiting for a final pass.
See it in action
The Quarterly Content Audit
A community manager needs to prove that all departmental articles are up-to-date. Instead of clicking through 50 profiles, they ask their agent to list_org_articles and then loop through the results to check if any article hasn't been touched in six months.
The Broken Link Fix
A developer finds an old piece of content with a broken reference. They use get_article_by_path to pull the current content, fix the markdown references, and then immediately call update_article without needing to open the CMS editor.
Profiling New Contributors
A product lead wants to vet a potential collaborator. They use get_user to check basic credentials, then run list_my_articles for that user to see their publishing history and quality of work.
Cross-Platform Content Promotion
A writer finishes a tutorial draft. They use create_article, publish it, and immediately ask the agent to list all articles with videos using list_videos so they can promote the new piece on social media.
The honest tradeoffs
Treating it like a search engine
Asking, 'Show me everything about JavaScript that's popular.' The system doesn't have a single keyword search tool; you can only list existing or specific content.
If you know the general area, use list_articles to see tags and categories. If you need something highly specific, retrieve it using get_article_by_path.
Updating article titles manually
Calling a generic 'modify post' command when the API requires the content body or path.
Always use update_article, which requires specifying which article you are modifying and providing the full, new markdown content.
Trying to find deleted posts
Asking for an article that was taken down last week.
If you need to change status, use unpublish_article. If it's gone from the public list, there is no tool to recover historical drafts.
When It Fits, When It Doesn't
Use this MCP if your workflow involves a continuous loop between writing technical content and managing its publication lifecycle. Specifically, you need tools that cover drafting (create_article), modifying published work (update_article), or auditing existing posts (list_org_articles). Don't use it if your primary goal is simple search—the system doesn't have a free-text search endpoint; instead, filter by ID or path. If you just want to see popular topics across the whole platform without ownership context, you might be better served by a dedicated analytics tool rather than relying on list_articles alone. This MCP is for control and manipulation of content records.
Questions you might have
How do I use the list_my_articles tool? +
The list_my_articles tool shows you every article associated with your account, whether they're drafts or published. This is useful for seeing what content you own but haven't finalized yet.
Can I find an article using only its name? +
No, the system requires more specific identifiers. You must use either get_article_by_id (the unique ID number) or get_article_by_path (the username and clean slug).
What if I want to take down an article quickly? +
Use the unpublish_article tool. It instantly removes the article from public view, which is necessary for moderation or temporary takedowns.
Does get_user need a username or just an ID? +
The get_user tool accepts either a user's unique ID number or their handle (username). You only need to provide one of those two pieces of information.
If I try to use the `update_article` tool, what level of permissions do I need? +
You must have write access assigned to your API key. The system checks for publishing rights before running the update. If you only have read permission, the call will fail with an authorization error.
How does using `list_org_articles` differ from checking my own posts with `list_my_articles`? +
When you use list_my_articles, you only see content published by your specific user account. However, list_org_articles pulls all published content associated with the organization's profile, giving you a broader view of group contributions.
What information do I need to provide when calling `create_article`? +
You must supply at least a title and the main article body. The content needs to be in standard markdown format for proper rendering on Dev.to or Forem.
What happens if I use `list_articles` and there are thousands of results? +
The tool handles large datasets through pagination. You'll need to specify the starting point and limit for your query, rather than asking for everything at once.
Can I publish a new post directly from the chat? +
Yes! Use the create_article tool by providing a title and the markdown content. You can also set the published status to true or false for drafts.
How do I see my own drafts and published posts? +
You can use the list_my_articles tool. It allows you to filter by type, such as 'all', 'published', or 'unpublished' (drafts).
Can I look up another user's profile information? +
Yes, use the get_user tool with either their unique User ID or their username to retrieve their public profile details.
We've already built the connector for Dev.to/Forem. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 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.