Dev.to MCP integration for AI agents.
Connect AI agents to Dev.to through 12 structured actions, including get article, create article, and get article by path. Review authentication, inputs, wor…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Dev.to integration exposes
The Dev.to Agent App exposes 12 provider-backed actions for social work. Its current contract lets an authorized agent get a dev.to article by numeric id, create a new dev.to article, and get a dev.to article by username and slug. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Dev.to account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Dev.to capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_articleREADGet a Dev.to article by numeric id.
INPUTS: articleId
create_articleWRITECreate a new Dev.to article.
INPUTS: title / bodyMarkdown / published / series / mainImage
get_article_by_pathREADGet a Dev.to article by username and slug.
INPUTS: username / slug
get_current_userREADGet the current authenticated Dev.to user profile.
get_organizationREADGet Dev.to organization profile.
INPUTS: organizationUsername
list_articlesREADList published Dev.to articles with query filters.
INPUTS: page / perPage / tag / tags / tagsExclude
list_latest_articlesREADList latest Dev.to articles.
INPUTS: page / perPage
list_my_articlesREADList current user's own Dev.to articles by status.
INPUTS: page / perPage / status
list_organization_articlesREADList articles under a Dev.to organization.
INPUTS: organizationUsername / page / perPage
list_tagsREADList Dev.to tags.
INPUTS: page / perPage
list_videosREADList Dev.to videos.
INPUTS: page / perPage
update_articleWRITEUpdate an existing Dev.to article.
INPUTS: articleId / title / bodyMarkdown / published / series
INPUT CONTRACTS
Know what the action needs before it runs.
get_article
articleIdOPTIONAL- An article identifier accepted by the Dev.to API.
create_article
titleREQUIRED- The article title.
bodyMarkdownREQUIRED- The article body in markdown.
publishedOPTIONAL- Whether the article is published.
seriesOPTIONALmainImageOPTIONAL
get_article_by_path
usernameOPTIONAL- The article author username.
slugOPTIONAL- The article slug.
get_organization
organizationUsernameOPTIONAL- The organization username.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Article
Get a Dev.to article by numeric id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_articleControl Create Article
Create a new Dev.to article. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_articleVerify with Get Article By Path
Get a Dev.to article by username and slug. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_article_by_pathSAFETY BOUNDARY
Operate Dev.to with explicit limits
- Authorize Dev.to with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Dev.to rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Dev.to task completed successfully.
CONNECTION MODEL
API key
DEV API key sent with the api-key header. Generate one from your DEV settings page: https://developers.forem.com/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Dev.to.