'%3e%3crect%20width='12'%20height='26'%20rx='4'%20fill='%23ff5a59'%20/%3e%3crect%20x='14'%20width='12'%20height='12'%20rx='4'%20fill='%237137ff'%20/%3e%3crect%20x='14'%20y='14'%20width='12'%20height='12'%20rx='4'%20fill='%23d8ff52'%20/%3e%3c/g%3e%3c/svg%3e)
01
Connect
Add the Streamable HTTP endpoint to your MCP client and complete browser-based sign-in.
MCP server
Your agents.
Your control room.
Connect an MCP-compatible client to the same publishing system as the DevPost web app. Agents can prepare and operate the workflow while account identity, approvals, schedules and delivery status stay visible to you.
One operating loop
Connect. Inspect. Operate.
02
Inspect
Let the client discover the current tools, schemas, platform constraints and connected accounts.
03
Operate
Create drafts, review copy, schedule or publish, then inspect status and performance in the same workspace.
Human control is part of the contract.
- Drafts and scheduled posts remain editable in the web app.
- The destination account and platform-native fields stay explicit.
- Growth actions can wait for review instead of publishing invisibly.
- Failures and asynchronous delivery states are inspectable.
Canonical tool reference
Discover, don’t memorize.
After connection, use the MCP client’s tool discovery. The live tool names, descriptions, input schemas and platform descriptors are the source of truth. This page intentionally describes the workflow without copying a tool list that could drift.
Suggested first request: “List my connected accounts, inspect the platform constraints, and
prepare a draft for review.”
Bring your agent. Keep the final say.
Create your account, connect your channels in the web app, then add the MCP endpoint to your client.
Create your account