A Dev.to MCP without running a server yourself
Connect one free API key and the DEV Community API becomes workflow steps: the public article feed with tag filters, search, your drafts and published posts, the create and publish switch, threaded comments, followers, and organizations. An AI agent can cross-post an article with the canonical URL set correctly, a scheduled workflow can drain a draft queue, and the results land next to your tasks and databases.
What the DEV Community MCP connector does
The DEV Community connector for Mattering Automations is 25 nodes on the Forem API v1 that powers dev.to: the public article feed with tag, author, freshness, and top-N-days filters, chronological latest-articles reads, full-text article search, your own published and draft articles, article create and update with publishing riding the published flag, threaded comment trees, your followers and followed tags, your reading list, the platform's tags and organizations, podcast episodes, and video articles. One free API key authenticates all of it.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can search DEV for what is already written on a topic, draft an article with tags and a canonical URL, hold it as a draft for review, and flip it live with an update, without anyone opening the dev.to dashboard.
There is no official Dev.to MCP server: Forem, the organization behind dev.to, does not ship one, and the servers you find on GitHub are community projects you install and run yourself. Connecting DEV Community here gets you the same API surface over MCP with nothing to host: the credential is stored once in Mattering, the nodes are maintained with the platform, and they sit on the automation canvas next to every other connector, so a DEV cross-post can start from your CMS webhook and end in a review task.
The safety modeling is stated plainly. Of the 25 nodes, 22 read and 3 act. The two article writes are reversible: publishing rides the published flag, and setting it back to false reverts a live article to draft. One node carries a destructive flag even though it deletes nothing: Follow Users or Organizations, because the public API has no unfollow endpoint, so a follow made by an automation persists until undone by hand. And one absence is worth knowing up front: the public API has no article delete at all, so a draft an automation creates stays in the dashboard until a person removes it. Admin and moderator endpoints, like user lookup by email, organization management, and the dedicated unpublish route, are deliberately not shipped.
One connection, three surfaces
- Visual automations. Drag DEV Community nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every DEV Community node, ready to drop on the canvas
25 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 22
DEV Community: Get Article
Fetch one published article by its numeric ID: the complete article object including its HTML and Markdown body, tags, and author profile.
DEV Community: Get Article by Path
Fetch one published article by its URL path parts - the author (or organization) username and the article slug - resolving a dev.to article URL straight into its API object.
DEV Community: Get Comment
Fetch one comment and all of its nested descendant replies by the comment's alphanumeric id_code.
DEV Community: Get My User
Fetch the user the API key belongs to: id, username, name, profile links, badge ids, and follower count. Requires a valid key (a bad one returns 401), so this is the credential health check to run first in any DEV automation.
DEV Community: Get Organization
Fetch one organization's full public profile by slug (username) or numeric id: name, summary, tech stack, tagline, story, links, and joined date.
DEV Community: Get User
Fetch a single user's public profile by numeric ID: name, summary, social handles, location, and profile image. The API reference says a username works in the same field, but on dev.to a username here returns 404 (live-verified 2026-08-11) - pass the numeric id, which follower and article payloads carry.
DEV Community: List Articles
List published articles from the public feed - by default featured articles ordered by descending popularity. Filter by tag(s), author or organization username, freshness state, a top-N-days popularity window, or a series (collection). Returns article ids, titles, URLs, tags, reaction and comment counts, and author profiles.
DEV Community: List Comments
List the comments on an article (a_id) or podcast episode (p_id) as threaded conversations - each top-level comment carries its replies nested recursively in children. Fill exactly one of a_id or p_id. Omit page to get the full tree in one payload; with page, pagination applies to top-level comments only.
DEV Community: List Followed Tags
List the tags the authenticated user follows, each with its tag id, name, and the user's interest points for it.
DEV Community: List Latest Articles
List published articles ordered strictly by descending publication date, bypassing the feed's popularity ranking - the endpoint for chronological timelines and latest-posts monitoring.
DEV Community: List My Articles (All)
List ALL of the authenticated user's articles - unpublished drafts first (reverse creation order), then published articles (reverse publication order). This is the full editable universe, and the source the Update Article picker draws from.
DEV Community: List My Followers
List the users who follow the authenticated user, with each follower's user_id, name, profile path, and image - the read behind follower-growth tracking and new-follower notifications.
DEV Community: List My Published Articles
List the authenticated user's PUBLISHED articles in reverse chronological publication order - the honest source for 'my live posts' dashboards and cross-posting automations.
DEV Community: List My Unpublished Articles
List the authenticated user's DRAFT (unpublished) articles in reverse chronological creation order - the queue a publish-on-schedule automation drains.
DEV Community: List Organization Articles
List an organization's published articles (by username or numeric id) in reverse chronological publication order - the feed behind a company-blog mirror or digest.
DEV Community: List Organization Users
List the public member profiles of an organization (by username or numeric id) - team directory reads for org pages and mention lists.
DEV Community: List Organizations
List the platform's organizations as compact rows: numeric id, name, slug, summary, tagline, profile image, and URL (the list rows are thinner than the single-org get). The slug from here feeds the organization get/users/articles nodes.
DEV Community: List Podcast Episodes
List published podcast episodes in reverse chronological order, optionally filtered to one podcast by its slug. Episode ids here are the p_id the List Comments node takes.
DEV Community: List Reading List
List the articles saved to the authenticated user's reading list (the posts they reacted to with save), as standard article objects - read-it-later export and digest automations start here.
DEV Community: List Tags
List the platform's tags ordered by popularity, with each tag's id, name, and colors. The tag names feed the List Articles tag filter and article-write tags.
DEV Community: List Video Articles
List published articles that carry an uploaded video, ordered by descending popularity, with each video's duration, source URL, and thumbnail.
DEV Community: Search Articles
Search published articles: the query matches against titles, tags, and body content, optionally restricted to articles published in the last N days.
Action nodes 3
DEV Community: Create Article
Create an article - as a draft by default, or live immediately with published=true. Publishing is reversible (DEV Community: Update Article with published=false reverts it to draft), but note the public API has no article DELETE: a created draft persists until removed by hand in the DEV dashboard. Returns 201 with the article; 422 with an error message on validation failures.
DEV Community: Follow Users or Organizations
NO API UNDO: follow users and/or organizations in bulk on behalf of the authenticated user. Nothing is deleted, but the public API has no unfollow endpoint, so every follow made here persists until undone by hand in the DEV UI - treat it like an irreversible action in automations and never run it in a blind test.
DEV Community: Update Article
Update one of YOUR articles (the key must belong to the author); only the fields you fill are sent. This node is also the publish/unpublish switch: published=true takes a draft live, published=false reverts a live article to draft (the docs' supported author-side unpublish - the dedicated unpublish endpoint is moderator-only).
Connecting DEV Community takes one credential
DEV authenticates API requests with a single API key sent as the api-key header. Keys are generated on dev.to under Settings, then Extensions, in the DEV Community API Keys section: add a description and click Generate API Key. Accounts and API keys are free. The key is unscoped and acts as the user it belongs to, so articles the automation creates appear in that account's dashboard and follows it makes come from that account.
Sign in at dev.to, open Settings from your profile menu, and select Extensions.
Scroll to the DEV Community API Keys section, enter a description such as Mattering Automations, and click Generate API Key. Copy the key.
In Mattering Automations, open Connectors, click Add Connector, choose DEV Community, and create a credential with the API key.
Click Test Connection. Mattering calls DEV's own-profile endpoint: a good key returns your profile, a bad key returns 401 unauthorized, and no secret material is echoed either way.
All 25 DEV Community nodes appear in the canvas palette. Run DEV Community: List My Articles (All) first for the article IDs the update node takes, and DEV Community: List Tags for tag names to filter and tag with.
Common uses for the DEV Community MCP
Cross-posting with the canonical URL set correctly
The create node takes a canonical_url field alongside the title, Markdown body, and tags, so a post that first went live on your own site can be mirrored to DEV while search engines keep crediting the original. DEV Community: Create Article makes the DEV copy as a draft by default, a review step checks it, and DEV Community: Update Article with published set to true takes it live. The whole flow starts from a webhook your CMS already sends.
A draft queue that publishes on a schedule
DEV Community: List My Unpublished Articles is the queue: it returns your drafts in reverse creation order. A scheduled trigger picks the next draft and DEV Community: Update Article flips its published flag to true. Because the update node sends only the fields you fill, nothing else about the article changes. The same automation can log each publish into a Mattering database so the cadence is visible next to the rest of your work.
Tag and keyword monitoring that lands in your workspace
DEV Community: List Articles filters the feed by tag with a top-N-days popularity window, DEV Community: List Latest Articles reads the platform chronologically for latest-post monitoring, and DEV Community: Search Articles matches a query against titles, tags, and body content. A scheduled sweep can write new matches into a Mattering database and open a task when something worth responding to appears, which turns DEV reading into a workflow instead of a browser habit.
Comment digests for your own posts
DEV Community: List My Published Articles lists your live posts, and DEV Community: List Comments returns each article's threads with replies nested recursively in children, so a scheduled workflow can collect what changed and produce a daily digest task. The connector reads comments and does not write them, which is the honest shape for this job: the digest tells you where the conversation is, and the replying stays yours.
Follower growth snapshots
DEV Community: List My Followers returns the users who follow the authenticated account with their names and profile paths, and DEV Community: List Followed Tags shows what the account itself follows. A weekly snapshot into a Mattering database gives you a follower count over time without a third-party analytics tool, and a comparison against the previous snapshot can surface new followers worth a hello.
An organization blog mirrored into the rest of your work
DEV Community: List Organization Articles reads a company organization's published posts in reverse chronological order, DEV Community: Get Article fetches any post's full body as both HTML and Markdown, and DEV Community: Get Article by Path resolves a dev.to URL straight into its API object. Together they feed newsletter digests, changelog roundups, and a content inventory that lives beside your tasks instead of in a bookmarks folder.
Example: A post goes live on your site: draft the DEV copy, get a human check, publish
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: an inbound webhook from your CMS fires when a post publishes, carrying the title, Markdown body, tags, and the post's URL.
DEV Community: Create Article creates the DEV copy as a draft, with canonical_url set to the original post so search engines credit your site.
The workflow opens a review task in Mattering Productivity with the draft's title and dev.to dashboard location, so a person reads the rendered draft before anything goes public.
On approval, DEV Community: Update Article sets published to true and the article goes live on DEV. If it ever needs to come down, the same node with published set to false reverts it to draft.
The workflow writes the article's ID and URL into a Mattering database.
A separate scheduled automation reads that database, runs DEV Community: List Comments per article, and files new threads into a daily digest task.
DEV Community MCP questions, answered
Is there an official Dev.to MCP server?
No. Forem, the organization behind dev.to, does not publish an official MCP server; the Dev.to MCP servers you find are community projects on GitHub that you install and run yourself. This connector is the no-hosting alternative: Mattering exposes the same DEV Community API surface over MCP, the credential is stored once, the nodes are maintained with the platform, and the same 25 nodes also work as steps in visual automations.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
What Dev.to operations are supported?
25 nodes on the Forem API v1: 22 query nodes and 3 action nodes covering the public article feed with tag, author, freshness, and top-N-days filters, chronological latest articles, full-text search, single articles by ID or by URL path, your published and draft articles, article create and update with publish and unpublish riding the published flag, threaded comments, single comments by id_code, your followers and followed tags, your reading list, the platform's tags, organizations with their members and articles, podcast episodes, and video articles. Deliberately not shipped: admin and moderator endpoints such as user lookup by email, organization create and update, user moderation, the dedicated unpublish route, and the reactions toggle.
Can an automation delete an article?
No, and that is the API, not the connector: the public DEV Community API has no article delete endpoint. What it does support is reversal: DEV Community: Update Article with published set to false reverts a live article to draft, which is the documented author-side unpublish. The practical consequence is that a draft an automation creates stays in the account's dashboard until a person removes it there, so test against a dedicated account rather than your main profile.
Can an agent unfollow users or organizations?
No. The public API has a follow endpoint but no unfollow, which is why DEV Community: Follow Users or Organizations is the connector's one destructive-flagged node even though it deletes nothing: every follow an automation makes persists until undone by hand in the DEV interface. Treat it as irreversible and keep it behind a condition or an approval step rather than a bare trigger.
What are Dev.to's API rate limits?
Forem does not publish rate-limit numbers for the API, so this page will not invent any. When the API throttles a caller it answers with HTTP 429 and an error message, and the nodes report that on their output rather than silently retrying. The practical guidance is to space scheduled sweeps apart and prefer one filtered list call over many single-article gets.
What credential does it need, and does it cost anything?
One API key, sent as the api-key header. DEV accounts and API keys are free: the key is generated on dev.to under Settings, then Extensions, in the DEV Community API Keys section. The key is unscoped and acts as the user it belongs to, so an automation publishes, saves, and follows as that account, which is worth choosing deliberately.
Does this work with Forem communities other than dev.to?
No. The API is the Forem platform API, but this connector targets dev.to, the flagship hosted instance, and sends every request to its host. Other Forem communities run on their own hosts and are out of this connector's scope.
Put DEV Community to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. DEV Community is a product of its respective owner; Mattering is an independent platform.