Loading...
×Use Manus with Tareno to read a conference's public agenda, plan before, during and after posts for your talk on X within 280 characters, and approve each draft in Tareno.
Yes, over the tested custom MCP connection. Manus reads the public agenda, speaker list and your slot, drafts posts for before, during and after the event within 280 characters and saves them through Tareno. Every request waits for your approval in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
A conference appearance is a few days of attention. Posts before the event bring people to your session, posts during it get lost in the noise unless they are specific, and posts after it decide whether the talk lives on. Preparing all three means reading the organizer's pages, which change, and tagging the right handles, which are easy to get wrong. Manus is made for this kind of research-first task, and Tareno turns the plan into drafts. This page follows a developer relations lead preparing for a talk, with the boundaries around handles and times, and with a plain statement of how Manus connects today.
Imagine a developer advocate with a Thursday 11:30 talk. She gives Manus the conference's agenda page, the speaker list and her abstract. Manus reads them, notes that the agenda lists the room as Hall B while an older page says Hall C, and asks which is current. It plans nine posts: three before the event, three for the day and three for the week after, each within 280 characters. It marks every post that tags someone and shows the handle it found. She corrects one handle, Manus saves the nine drafts through create_drafts for her X account, and she requests the first three slots in the dashboard.
Add the Tareno endpoint as a custom MCP connection with OAuth.
Provide the agenda, the speaker list and your abstract. Ask Manus to record the date it read each page, because conference pages change in the weeks before the event.
Where two pages disagree, such as a room or a start time, Manus asks. Fix the detail before any post uses it; a wrong room in a post sends people to the wrong hall.
Ask for posts before, during and after, each with a purpose: invite, point to a specific slide or moment, share the materials. A schedule of nine posts is only useful if each does a different job.
Have Manus show each handle next to the name it belongs to and the page where it found it. Tagging the wrong account is a common and visible mistake.
Manus confirms the account with list_accounts and saves the drafts through create_drafts. Give times and an IANA time zone for each phase; you approve the requests in the Tareno dashboard.
Read the conference agenda [URL] as groundwork for Tareno drafts,, the speaker list [URL] and my abstract below. Record the date you read each page, list my session's time, room and format, and tell me every place where two pages disagree. Do not write posts yet.Plan nine X posts for Tareno drafts around my talk: three before the event, three on the day and three in the week after. For each give the purpose, the draft text within 280 characters and any account it tags. Use only confirmed details from the organizer's pages.List every account that appears in the plan next to the person it belongs to and the page where you found the handle. Remove any tag you could not source, and mark anything that depends on the organizer's hashtag so I can confirm it.Use Tareno to confirm my X account [handle] and save the nine approved posts as drafts, numbered in the order they should appear. Return a table with draft ID and phase, and request no time before I confirm the room and the start time.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: X API documentation: create a post, read on 2026-10-24. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
Use the tested custom MCP connection in Manus with OAuth and your own Tareno account. Availability depends on your Manus plan and workspace permissions. After connecting your own Tareno account, run list_accounts and check the returned profiles before creating a draft or requesting a publishing time.
It reads the speaker and organizer pages and shows each handle with the person and the source page. Handles it cannot source should be removed, and you confirm the rest before any draft is requested for a time.
No. Tareno does not read posts or replies on X, so Manus cannot see the hashtag live. It prepares the posts beforehand, and you handle live conversation on X yourself.
Give Manus the new details and ask it to list every draft that mentions the old ones. Update those drafts in Tareno, and cancel any pending request that still carries the outdated time.
No. The custom connection uses OAuth with your Tareno account, and Manus stores the authorization. Do not paste a key or token into a task, because it would remain in the conversation.
No. Each request is a pending action in Tareno, and X receives a post only after you approve it in the dashboard. `get_action_status` shows what happened to each one afterwards.