Loading...
JetBrains Junie/TarenoJetBrains developers learn their lessons in refactorings, plugin releases and small language tricks.
JetBrains Junie / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
JetBrains JunieIllustrated demo · no live account
In the IDE open Tools, then Junie, then MCP Settings, and choose Add. Junie opens an mcp.json with an mcpServers section; add an entry named tareno with the hosted endpoint. After saving, Junie lists the server with its connection state and tools. Ask for your connected accounts to test. Tareno has not completed a client test with Junie.
The path is Tools, Junie, MCP Settings and then Add. JetBrains' documentation says the fields inside the file come from each server's own documentation, so Tareno's setup page is the reference rather than Junie's.
Call the entry tareno and use the address from the example on the right. Once the file is saved, Junie lists the server, its connection state and the tools it found, which is the first place to look if something is wrong.
The hosted endpoint supports OAuth, so you sign in with your Tareno account in the browser. Keep any API key in an environment variable and out of the mcp.json that you might commit.
Ask Junie for your connected accounts before it drafts anything. If the account you want comes back, the connection holds; if not, connect the account in Tareno first.
{
"mcpServers": {
"tareno": {
"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.
Junie can compile, run and read the code a post is about, which is the difference between a tip and a rumour. Three jobs use that, each with its own workflow page.
After replacing callbacks with coroutines or splitting a module, the lesson is worth sharing with teams facing the same migration. Junie summarizes the change from the diff and the tests, lists every identifier it took from the code, and rewrites the draft without table names, service names or hostnames before you read it.
Plugin authors announce versions to people who install on sight. Junie reads the change notes and the plugin descriptor, quotes the compatible IDE range exactly, finds your demo GIF in the Tareno library and fits the post into 280 characters, since X allows one animated GIF in place of photos.
A three-slide tip fits the carousel format. Junie compiles both versions of the snippet in a scratch file, confirms they behave as the tip claims, and writes alt text that states the code in words for each screenshot, because code inside an image is invisible to a screen reader.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Cursor, GitHub Copilot and Antigravity also reach Tareno from an editor, each through its own configuration. Junie's distinction is that it works inside the JetBrains IDEs, with their compilers, inspections and test runners, which suits verified tips and plugin posts. If your day is in VS Code or Cursor, those agents are the closer fit.
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_accountsJetBrains documents adding MCP servers under the Junie settings, so the route exists. Tareno itself has no completed client test with Junie, which is why the first step is to confirm the server state and make a read-only call.
From the MCP server's own documentation, according to JetBrains. For Tareno that is the Remote MCP setup page, which gives the hosted endpoint and the OAuth sign-in. Junie lists the server and its tools once the file is saved.
Ask Junie to list every identifier it took from the code and to rewrite the draft without them, then read the result in Tareno. Tareno only receives what Junie sends, so the check is a human reading of the text.
One. X's API documentation allows up to four photos, one animated GIF or one video per post, and the GIF replaces the photos. Tareno's configuration accepts gif files up to 5 MB for X, so trim long recordings.
Because a screenshot makes code look authoritative. Junie compiles and runs both versions in a scratch file and reports where they differ, so the tip states what actually happens rather than what was remembered.
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. Junie can only report that the action is pending.
Through Tareno, yes: replies on Threads can be read and grouped, for example into corrections and alternatives. Junie cannot post replies, so you answer in the app and decide what to change.
Usually `list_accounts` to confirm the destination, `list_media` to find screenshots or the demo GIF and `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.