Work with an agent
Connect an external agent, inspect its proposals and keep a visible record of its actions.
1. Connect your MCP client
Create an API key in Settings. Enable distribution:read to inspect your workspace and distribution:write to prepare content and plans. Configure your client for Streamable HTTP and send the key in the Authorization header. Configuration field names depend on the client.
Endpoint: https://kitmo.app/api/mcp
Transport: Streamable HTTP
Authorization: Bearer <KITMO_API_KEY>2. Ask for a proposal
Ask the agent to list your accounts, create draft content and propose a distribution plan. Have it omit scheduledAt when creating content if you want a draft for review. The content creation tools also accept scheduling directly; plan approval is not a universal publishing permission boundary.
List my connected accounts. Prepare a draft for the accounts I select,
then create a distribution plan with proposed times.
Do not schedule the source content. I will review it in Kitmo.3. Review the recorded work
Open Agent work to see recent plans, destination captions, proposed times and review history. Approve a proposal or request changes. Approval records a decision; it does not submit publishing jobs. Use the source content in the composer to publish or schedule, then check the queue.
New recorded actions identify MCP, API or the Kitmo app as their source. Older plans may not have an origin recorded. Kitmo does not receive the external agent’s live reasoning, progress or failed tool calls.
Current limits
There is no built-in agent chat yet. A write-enabled REST key can approve plans, so give write access only to integrations you trust. The MCP schedule_content tool currently updates the plan record and its proposed times; it does not enqueue the content for delivery.