# What can Goose do on LinkedIn with Finchreach?

Source: https://finchreach.com/integrations/goose
Third-party facts checked on 2026-10-28.

Goose can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations through Finchreach, with one condition: header support comes from Goose’s code and partner guides; the official docs only describe OAuth so far. Reads run right away; every write waits in your approval queue until you approve it.

## What can Goose do on your LinkedIn?

Goose works through multi-step jobs on its own. LinkedIn becomes one step of them: research a list, read a profile, draft the note. The approval queue is the checkpoint where a person decides what goes out in your name.

> Ask your assistant: “Summarize my LinkedIn notifications and messages from the past week.”

> Ask your assistant: “Draft a LinkedIn post from my notes in this folder.”

> Ask your assistant: “Send connection invitations with a short note to the people at companies on this list.”

| Reads (run right away) | Writes (wait for your approval) |
| --- | --- |
| `linkedin_list_accounts`: The LinkedIn accounts connected to your workspace | `linkedin_create_post`: A text post |
| `linkedin_get_profile`: A LinkedIn profile | `linkedin_send_dm`: A direct message |
| `linkedin_get_feed`: Your home feed | `linkedin_send_invitation`: A connection invitation, with an optional note |
| `linkedin_get_notifications`: Your notifications | `linkedin_react_to_post`: A reaction on a post (like by default) |
| `linkedin_get_conversations`: Your message threads | `linkedin_unreact`: Removes your reaction from a post |
| `linkedin_get_messages`: The messages in a thread | `linkedin_comment_on_post`: A comment on a post |
| `linkedin_search`: Search everything, posts, people or companies | `linkedin_delete_comment`: Deletes one of your comments |
| `linkedin_get_received_invitations`: Coming soon: the connection invitations waiting for your answer | `linkedin_accept_invitation`: Coming soon: accepts a received invitation |
| `linkedin_get_action`: The status of a write: waiting for approval, approved, rejected or done |  |

## What happens when Goose drafts something?

1. Goose calls a write tool, for example `linkedin_create_post` with the text it wrote.
2. Finchreach doesn’t post it. It stores a pending action and tells the assistant it is waiting for approval.
3. You open [Approvals](https://finchreach.com/approvals), read the exact text and the account it would go out from, and approve or reject it.
4. Approved actions run on LinkedIn; rejected ones never do. Goose can check the outcome with `linkedin_get_action`.

> Approval mode is on by default for every workspace. It is what makes it reasonable to let an assistant draft in your name.

## Does Goose work with Finchreach today?

|  | Goose |
| --- | --- |
| Remote MCP servers | Built in |
| Finchreach (OAuth or API key) | Connects, with conditions |
| How sure we are | Medium: official docs incomplete, partly third-party sources |
| Checked on | 2026-10-28 |

Goose documents OAuth for remote extensions. Bearer header support comes from goose PR #3986 and a partner guide (Apify); the `headers` key in `config.yaml` isn’t in the official docs yet.

Finchreach’s server, `https://mcp.finchreach.com/mcp`, uses Streamable HTTP (pasting the bare `https://mcp.finchreach.com` works too). It signs in with OAuth 2.1, where you log in to Finchreach and approve a LinkedIn account and scopes, or with an API key sent as `Authorization: Bearer lk_…` or `X-API-Key`.

## How do I connect Goose?

1. Create an API key under [API keys](https://finchreach.com/api-keys) and connect your LinkedIn account under [Accounts](https://finchreach.com/accounts).
2. Desktop: Extensions → Add custom extension → type Streamable HTTP → URL `https://mcp.finchreach.com/mcp` → add a request header `Authorization` with the value `Bearer lk_YOUR_KEY`.
3. CLI: `goose configure` → Add Extension → Remote Extension (Streamable HTTP). Or edit `~/.config/goose/config.yaml` as below.
4. Ask Goose to list your LinkedIn accounts to check the connection.

~/.config/goose/config.yaml:
```yaml
extensions:
  finchreach:
    name: finchreach
    type: streamable_http
    uri: https://mcp.finchreach.com/mcp
    headers:
      Authorization: Bearer lk_YOUR_KEY
    enabled: true
    timeout: 300
```

Replace `lk_YOUR_KEY` with your key. The [step-by-step Goose guide](https://finchreach.com/guides/goose) has every step, a test prompt and troubleshooting.

## Questions

### Can Goose post on LinkedIn without me?

No. With approval mode on, the default, every write Goose makes through Finchreach (posts, comments, reactions, messages, invitations) becomes a pending action. You approve or reject it under [Approvals](https://finchreach.com/approvals) before anything happens on LinkedIn.

### Can Goose post images, schedule posts or manage a company page?

Not through Finchreach today: posts are text only, there is no scheduling, and company pages and analytics aren’t supported. Writes happen when you approve them.

### Is it safe for my LinkedIn account?

Any automation of a personal LinkedIn account carries some risk under LinkedIn’s User Agreement, and no tool can promise otherwise. Finchreach lowers it by keeping a person in the loop: nothing goes out until you approve it, and actions happen at your pace, not in bulk.

## Sources

- [Goose docs](https://block.github.io/goose/docs/getting-started/using-extensions)

## Related

- [Step-by-step: connect Goose](https://finchreach.com/guides/goose)
- [Follow up on LinkedIn after an event with Goose](https://finchreach.com/blog/goose-linkedin-event-follow-up)
- [All integrations](https://finchreach.com/integrations)