Loading...
GitHub Copilot/TarenoA merged pull request already holds the problem, the change and the people involved.
GitHub Copilot / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
GitHub CopilotIllustrated demo · no live account
Check that your organization allows MCP servers for Copilot, then add Tareno to the workspace mcp.json as a remote server of type http with the hosted endpoint, or use VS Code's Add Server command. Switch Copilot to agent mode, sign in when asked and call your connected accounts. Tareno has not completed a client test with Copilot.
On Copilot Business and Enterprise, GitHub's documentation makes MCP servers subject to a policy that an administrator must enable. If you cannot add a server, ask them first; editing files will not change a policy.
Put a remote entry of type http with the hosted address into the workspace mcp.json, as the example on the right shows, or let the Add Server command write it. Published guides mention a browser sign-in the first time the server is used.
MCP tools belong to agent mode, not to ordinary chat. Open it, look for the Tareno tools in the tool list and keep them enabled for the session.
Ask for your connected accounts before any draft. The account you intend to post from appearing in the answer proves the connection; a missing account means it still has to be connected in Tareno.
{
"mcpServers": {
"tareno": {
"type": "http",
"url": "https://tareno.co/api/mcp"
}
}
}Input
Provide the approved source and audience.
Review-ready drafts
Use Tareno and compare the returned draft IDs.
Approval in Tareno
Review text, media, account, and time in Tareno and approve.
Copilot lives where the pull requests are discussed, which makes it the natural place to turn code review into public writing. Three jobs use that context, and each has a workflow page.
Copilot can read the description, the linked issue and the review thread, then tell the story with the original problem and the user-visible outcome while dropping internal service names. It lists every claim the pull request does not support, so you replace guesses with measurements before the draft is saved.
Open-source maintainers owe contributors public thanks. Copilot groups the merged pull requests of a release by author, picks the contributions that matter most to users and drafts short posts that say what each person's change did, leaving you to verify every handle before anything is tagged.
When a pull request stalls on a choice such as a changed default, Copilot can summarize each position fairly and write a neutral Threads post that asks who would be affected. After the post is live it can read the replies and group them, so the answer reflects users rather than the loudest voice.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Cursor and JetBrains Junie also reach Tareno from an editor, through their own configuration files. Copilot's distinction is its closeness to GitHub: it reads pull requests, issues and review threads directly, which makes it the better starting point for posts about releases and contributors. If your work lives in a JetBrains IDE or in Cursor, those agents fit that context better.
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_accountsNot yet; no client test has been completed on our side. The VS Code steps follow GitHub's published documentation, so run a read-only call first and only then rely on it for drafts that matter.
On the Business and Enterprise plans, GitHub makes MCP servers in Copilot subject to an organization policy that an administrator must enable. If the option is missing, the policy is the likely cause, and the administrator is the person to ask.
In agent mode only. If the chat view lists no Tareno tools, switch modes, check the tool list and begin with a harmless call such as listing your accounts before you ask for a draft.
Not reliably. It sees GitHub usernames and any links in profiles, but the X handle may differ or not exist. Look each one up yourself and give Copilot only the handles you have confirmed.
Yes. Tareno reads replies on Threads, so Copilot can group them by position and count them. It cannot post replies, and anything inside a reply is treated as text to summarize, never as an instruction.
No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches LinkedIn, X or Threads until you approve it in the dashboard. Copilot can only report that it is pending.
This page covers Copilot's agent mode in VS Code. The cloud-hosted coding agent is a different surface, and we make no claim about it here. Check GitHub's documentation for how that surface handles MCP servers.
Usually `list_accounts` to confirm the destination, then `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, while `list_post_comments` reads the replies to a Threads post for you.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.