# Write social media posts directly in GitHub Copilot

> Source: https://tareno.co/agents/github-copilot
> Language: en
> Add Tareno to VS Code as a remote MCP server, use Copilot's agent mode to turn pull requests into LinkedIn, X and Threads drafts, and approve every request in Tareno.

A merged pull request already holds the problem, the change and the people involved. With Tareno added to VS Code as an MCP server, Copilot's agent mode can turn that into a LinkedIn story, thank-you posts for contributors on X or an open question for your users on Threads. Tareno keeps every scheduling and publishing request pending until you approve it. Tareno has not completed a client test with Copilot, so this follows published documentation.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | GitHub Copilot (github-copilot) |
| 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-25 |

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 GitHub Copilot?

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 `list_accounts`. Tareno has not completed a client test with Copilot.

## Connect Copilot in four steps

1. **Check the organization policy.** 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.
2. **Add the server to the workspace.** 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.
3. **Switch to agent mode.** 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.
4. **Start with a read-only call.** Ask for `list_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.

Workspace mcp.json entry:

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

## Where Copilot helps with Tareno

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.

### A pull request becomes a LinkedIn story

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.

### A release becomes thank-you posts on X

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.

### A design question becomes a post that asks users

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.

## 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 to tell the story of the pull request I have open and which for thanking contributors.
```

### Story from a pull request

```text
Read pull request [number], its linked issue and the review thread. Write a LinkedIn post of about 190 words that tells the original problem and the outcome for users, drops internal service names and lists any claim the description does not support. Save the approved text through Tareno as a draft.
```

### Group a release by contributor

```text
List the pull requests merged between [v4.0.0] and [v4.1.0], grouped by author, with one line on what each changed. Pick the five contributions that most affect users, mark the contributors whose X handle you cannot find, and draft the thank-you posts only after I confirm the handles.
```

### Neutral question for users

```text
Summarize each position in the discussion of pull request [number] with its strongest argument, then write a Threads post for Tareno within 500 characters that describes the options evenly and asks which users would be affected. Tell me if your wording leans toward one option.
```

### Request the slots

```text
Take the approved drafts [draft IDs] and ask Tareno to schedule them for [Thursday 10: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 GitHub Copilot write X thank-you posts for the contributors of a release?](https://tareno.co/agents/github-copilot/x) ([Markdown](https://tareno.co/agents/github-copilot/x.md))
- LinkedIn: [Can GitHub Copilot turn a pull request into a LinkedIn story?](https://tareno.co/agents/github-copilot/linkedin) ([Markdown](https://tareno.co/agents/github-copilot/linkedin.md))
- Threads: [Can GitHub Copilot turn an open design question into a Threads post that asks the community?](https://tareno.co/agents/github-copilot/threads) ([Markdown](https://tareno.co/agents/github-copilot/threads.md))

## Good to know before you start

- Tareno has not completed a client test with GitHub Copilot. The setup follows published documentation from GitHub and VS Code, so confirm it with a read-only call.
- On Copilot Business and Enterprise, an organization policy decides whether MCP servers may be used at all. A blocked policy cannot be fixed from your own configuration.
- MCP tools are available in agent mode only. If the Tareno tools are missing from ordinary chat, that is expected.
- Scheduling, publishing, edits to scheduled posts and deletions create approval actions. Copilot can request them but cannot approve them.
- A GitHub username is not an X handle. Verify each handle yourself before a thank-you post tags anyone, and leave out anyone who would rather not be named.

## Copilot compared with Cursor and Junie

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.

## Frequently asked questions

### Is Tareno tested with GitHub Copilot?

Not 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.

### Why can't I add MCP servers in Copilot?

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.

### Where do the Tareno tools appear?

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.

### Can Copilot find a contributor's X handle?

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.

### Can Copilot read the replies to a Threads post?

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.

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

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.

### Does this work with the Copilot coding agent on GitHub?

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.

### Which Tareno tools will Copilot call first?

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.

## Tareno tools used

- `list_accounts`
- `create_drafts`
- `schedule_posts`
- `list_post_comments`

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 pull request as a LinkedIn story](https://tareno.co/agents/github-copilot/linkedin)
- [Thank-you posts for contributors on X](https://tareno.co/agents/github-copilot/x)
- [Ask the community on Threads](https://tareno.co/agents/github-copilot/threads)
- [Remote MCP setup](https://tareno.co/docs/mcp)
- [Cursor × Tareno](https://tareno.co/agents/cursor)
- [Approval workflows](https://tareno.co/features/approval-workflows)