Chirio is built to be worked by agents as much as by code. Its MCP server gives an agent such as Claude the same abilities as the REST API: publish, take screenshots, work the inbox and boards, answer comments pinned on pages, write changelog entries, answer messages and read analytics.
Connect
The server runs at https://chirio.dev/api/mcp over Streamable HTTP. The API key goes in a header, exactly as for the REST API:
For connector settings that take only a URL, the server also answers at https://chirio.dev/api/mcp/chirio_sk_.... The URL is then the secret, so treat it like the key.
create_board_post posts on a board as the team, with a status, which is how an agent puts planned and running work on the roadmap.
A day's work for an agent
Answer what is waiting.list_inbox with needsReply: true, then list_page_comments with needsReply: true, then list_conversations with needsReply: true. Paying reporters come first in the inbox.
Do what the team asked.list_page_comments with visibility: "claude" lists notes the team pinned on pages for the agent alone. Do the work, answer on the pin, then resolve it with update_page_comment.
Keep the roadmap honest. Move board posts with update_inbox_item as work is planned, started and done.
Tell people it shipped.create_changelog_entry names the board posts it delivers, so their voters hear about it. Entries stay drafts unless you publish them.
Answering as the owner
Answers to board posts, page comments and messages go out on the workspace's behalf. Page comment answers carry the owner's own name and photo with a via Claude mark. Have your agent write as the owner would, plainly, and never promise what the owner has not.
Same rules as the API
Each tool calls the REST route of the same name inside Chirio, with your key. Validation, quota and billing are identical: create_post is metered in network writes, a finished screenshot costs 3 units, and reads, the inbox, boards, page comments, the changelog, messages and analytics cost nothing. A tool for a product your workspace does not have switched on answers with the same error as the REST route.
A post goes live when the tool returns
create_post publishes at once unless it carries publishAt. Have your agent confirm the content with a person before it posts on their behalf.