# Create social media posts with Devin

> Source: https://tareno.co/agents/devin
> Language: en
> Connect Devin to Tareno to create social media posts, reuse your content and prepare posting times. Review drafts and approve publication in Tareno.

Use Devin with Tareno to write social media posts, adapt existing content and prepare posting times. Review your drafts in Tareno and approve every publication yourself. Setup follows the product documentation; a Tareno client test is still pending.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Devin Desktop (devin) |
| Available connection | Custom MCP connection |
| Connection evidence | documented |
| Methods | mcp |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/mcp) |
| Install or connect | [Open setup](https://tareno.co/docs/mcp) |
| Evidence observed | No dated observation recorded |
| Facts reviewed | 2026-10-27 |

Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface.

## How do I connect Tareno to Devin?

In Devin Desktop, first check which agent you use. The default Devin Local agent uses Devin CLI MCP configuration; legacy Cascade uses its own mcp_config.json. Add https://tareno.co/api/mcp as a remote HTTP server, complete the supported OAuth flow and ask for `list_accounts`. Tareno has not completed a Devin Desktop client test.

## Connect Devin Desktop in four steps

1. **Choose the route in.** Devin Desktop has two agents with different settings. Devin Local uses the Devin CLI configuration files. Legacy Cascade uses mcp_config.json, opened from its Actions menu; Cascade has no MCP marketplace or one-click install. The example below is a Cascade configuration.
2. **Decide who owns the connection.** Use the Tareno account that owns the intended social profiles and review the permissions before authorizing. Follow the OAuth controls for the selected Desktop agent. Cloud organization settings are a separate product surface.
3. **Confirm the endpoint.** The hosted address appears in the entry on the right. If you manage servers through a configuration file, it is the same address that other clients use; no key needs to appear in it when you sign in with OAuth.
4. **Prove the link with a read.** Ask Devin for `list_accounts` before it drafts anything. The account you want in the answer confirms the connection; an empty answer means the account still has to be connected inside Tareno.

Legacy Cascade: remote MCP entry:

```json
{
  "mcpServers": {
    "tareno": {
      "url": "https://tareno.co/api/mcp"
    }
  }
}
```

## Where Devin helps with Tareno

Devin's record of completed work is the asset. These three jobs turn it into public writing without inflating it, and each has a workflow page with its own checks.

### Finished sessions become a client-safe delivery brief

A consultancy that delegates work to Devin can summarize what was delivered, the test results the client has seen and the limits of the work, without naming the client. The brief goes to LinkedIn only after the client has seen the wording and agreed, which is a step Devin can prompt for but cannot perform.

### A week of tickets becomes a shipped-this-week post

Devin lists the tickets that finished and separates changes a customer can use from internal work. It reports which changes sit behind a flag or reach only some accounts, so the Friday post on X says what is live rather than what is closed, and fits in 280 characters.

### A release becomes an upgrade warning on Mastodon

Self-hosting administrators read release posts for what they must do. Devin finds the sessions that changed schemas, configuration keys or minimum versions and puts those actions first in the post, leaving you to test the upgrade steps on a copy before approving anything.

## Prompts to copy

### Check the connection

```text
Use Tareno to list my connected social accounts with platform and account name. Read only: do not create, schedule or publish anything. Tell me which account you would use for a client delivery brief and which for the weekly shipped post.
```

### Delivery brief without the client

```text
List the sessions finished for [project] and what each delivered, with the test results the client has seen and the modules not covered. Write a LinkedIn brief of about 210 words that omits the client's name, state the evidence behind each statement and save it as a draft through Tareno only after I have shown it to the client.
```

### Shipped versus finished

```text
List this week's finished tickets with one sentence each on what changed for a user. For every user-visible change say whether it is behind a flag, limited to some accounts or still in review, and write the X post for Tareno within 280 characters from the changes that are live.
```

### Upgrade actions first

```text
From the sessions behind release [4.2], find every change that needs administrator action: schemas, configuration keys, environment variables and minimum versions. Write a Mastodon post for Tareno that opens with those actions in order, and do not save it until I have tested the steps.
```

### Request the slots

```text
Take the approved drafts [draft IDs] and ask Tareno to schedule them for [Friday 16:00] in [Europe/Berlin]. Return the action IDs and remind me that each request still waits for my approval in the Tareno dashboard.
```

## Guides by network

- X: [Can Devin turn a week of finished tickets into a shipped-this-week post on X?](https://tareno.co/agents/devin/x) ([Markdown](https://tareno.co/agents/devin/x.md))
- LinkedIn: [Can Devin help write a LinkedIn delivery-impact brief?](https://tareno.co/agents/devin/linkedin) ([Markdown](https://tareno.co/agents/devin/linkedin.md))
- Mastodon: [Can Devin write release notes for a self-hosted app and post the upgrade warning to Mastodon?](https://tareno.co/agents/devin/mastodon) ([Markdown](https://tareno.co/agents/devin/mastodon.md))

## Good to know before you start

- Tareno has not completed a client test with Devin. The setup follows Cognition's documentation for remote MCP servers, so verify the connection with a read-only call.
- A shared organization connection lets any Devin user in the organization draft for the connected accounts. Prefer personal access for accounts that have one owner.
- Devin can only tell whether a change is live from evidence in the work it can see, such as merged changes and flags. The product manager confirms before a post is approved.
- Scheduling, publishing, edits to scheduled posts and deletions create approval actions. Devin can request them but cannot approve them.
- Client work is confidential by default. Show the client the wording and record their agreement before a delivery brief is published.

## Devin compared with other coding agents

Codex and Claude Code run in a terminal, Cursor and Copilot in an editor. Devin works as a delegated engineer with its own sessions, which is why its record is useful for delivery updates: the sessions already describe what was done and what was tested. If your content comes from commits in an editor, those other agents sit closer to the code.

## Frequently asked questions

### Is Tareno tested with Devin?

Not yet; no client test has been completed on our side. Devin can use remote MCP servers according to Cognition's documentation, so expect an OAuth sign-in in the first session and confirm the connection with a read-only call.

### Should the connection be shared or personal?

For an account with one owner, personal access. A shared connection would let anyone using Devin in the organization draft for that account. Approval still happens in Tareno either way, but the drafts should come from the person who owns the account.

### How does Devin know what is live?

Only from what it can see: merged changes, deployment records and flags in the work it handled. When it cannot tell, it should say so, and the product manager confirms before the post is approved.

### Can Devin write about client work?

It can draft a brief that omits the client and lists the evidence behind each statement. Whether it may be published is the client's decision, so show them the wording and record their agreement first.

### Can a weekly post include a recording?

Yes, on networks that take video. X allows one video per post and Tareno's configuration limits it to 140 seconds. Upload the clip to the library first, and Devin can find it by name.

### Will Devin publish a post without my approval?

No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches LinkedIn, X or Mastodon until you approve it in the dashboard. Devin can only report that the action is pending.

### How do I keep internal ticket details out of posts?

Tell Devin to describe changes as a customer would see them and to leave out ticket numbers, service names and internal tooling. Then read each draft in Tareno, because the check for what is sensitive is still a human one.

### Which Tareno tools will Devin call first?

Usually `list_accounts` to confirm the destination and `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, and `get_action_status` tells you what became of the request.

## Tareno tools used

- `list_accounts`
- `create_drafts`
- `schedule_posts`
- `get_action_status`

Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them.

## Related

- [A delivery-impact brief for LinkedIn](https://tareno.co/agents/devin/linkedin)
- [A shipped-this-week post on X](https://tareno.co/agents/devin/x)
- [Self-hosted release notes on Mastodon](https://tareno.co/agents/devin/mastodon)
- [Remote MCP setup](https://tareno.co/docs/mcp)
- [Codex × Tareno](https://tareno.co/agents/codex)
- [Approval workflows](https://tareno.co/features/approval-workflows)