Forem MCP integration for AI agents.
Connect AI agents to Forem through 10 structured actions, including get article, create article, and get article by path. Review authentication, inputs, work…
- ACTION CONTRACTS
- 10
- 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 Forem integration exposes
The Forem Agent App exposes 10 provider-backed actions for social and developer tools work. Its current contract lets an authorized agent retrieve one published forem article by numeric id, create a forem article for the authenticated user, and retrieve one published forem 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 Forem account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Forem capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_articleREADRetrieve one published Forem article by numeric ID.
INPUTS: articleId
create_articleWRITECreate a Forem article for the authenticated user.
INPUTS: title / bodyMarkdown / published / series / mainImage
get_article_by_pathREADRetrieve one published Forem article by username and slug.
INPUTS: username / slug
get_commentREADRetrieve one Forem comment thread by numeric ID.
INPUTS: commentId
get_current_userREADRetrieve the Forem user associated with the connected API key.
list_articlesREADList published Forem articles with optional filters.
INPUTS: page / perPage / tag / tags / tagsExclude
list_commentsREADList Forem comments for an article or podcast episode as threaded conversations.
INPUTS: articleId / podcastEpisodeId / page / perPage
list_my_articlesREADList articles owned by the authenticated Forem user.
INPUTS: scope / page / perPage
list_tagsREADList Forem tags ordered by popularity.
INPUTS: page / perPage
update_articleWRITEUpdate an existing Forem article by numeric ID.
INPUTS: articleId / title / bodyMarkdown / published / series
INPUT CONTRACTS
Know what the action needs before it runs.
get_article
articleIdOPTIONAL- The Forem article ID.
create_article
titleREQUIRED- The article title.
bodyMarkdownREQUIRED- The article body in Markdown.
publishedOPTIONAL- Whether the article should be published.
seriesOPTIONALmainImageOPTIONAL
get_article_by_path
usernameOPTIONAL- The Forem username from the article path.
slugOPTIONAL- The Forem article slug.
get_comment
commentIdOPTIONAL- The Forem comment ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Article
Retrieve one published Forem 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 Forem article for the authenticated user. 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
Retrieve one published Forem 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 Forem with explicit limits
- Authorize Forem 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 Forem rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Forem task completed successfully.
CONNECTION MODEL
API key
Forem API key sent with the api-key header. For DEV, generate one from the DEV extensions settings page: https://dev.to/settings/extensions.
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
- 8
- 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 Forem.