What can GitHub Copilot do on LinkedIn with Finchreach?
GitHub Copilot can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations through Finchreach’s remote MCP server. Add the server to GitHub Copilot and sign in to Finchreach (OAuth) or use your Finchreach API key; every write waits in your approval queue until you approve it.
What can GitHub Copilot do on your LinkedIn?
GitHub Copilot sees the project you’re working on, so the LinkedIn post about a release or the reply to a technical question can come from the code itself instead of a blank page. You stay in the editor; the approval happens in Finchreach.
Ask your assistant“Summarize the release notes in this repo as a LinkedIn post draft for our engineering page readers.”
Ask your assistant“Find the LinkedIn profile of the maintainer of this library and draft a short thank-you message.”
Ask your assistant“Read my LinkedIn notifications and tell me who engaged with my last post.”
| 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 GitHub Copilot drafts something?
- GitHub Copilot calls a write tool, for example
linkedin_create_postwith the text it wrote. - Finchreach doesn’t post it. It stores a pending action and tells the assistant it is waiting for approval.
- You open Approvals, read the exact text and the account it would go out from, and approve or reject it.
- Approved actions run on LinkedIn; rejected ones never do. GitHub Copilot 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 GitHub Copilot work with Finchreach today?
| GitHub Copilot | |
|---|---|
| Remote MCP servers | Built in |
| Finchreach (OAuth or API key) | Connects directly |
| How sure we are | High: from the official docs |
| Checked on | 2026-10-28 |
Headers are supported, and ${input:…} prompts for the key so it is never written into the file.
Requirements: Copilot Business and Enterprise admins can restrict or turn off MCP; the chat.mcp.access setting controls which servers are allowed.
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 GitHub Copilot?
- Create an API key under API keys and connect your LinkedIn account under Accounts.
- Create
.vscode/mcp.jsonwith the entry below, or run “MCP: Add Server” from the command palette and pick HTTP. - Start the server from the file (or the MCP view). VS Code asks for the Finchreach key once, as a password, and stores it securely.
- Ask GitHub Copilot to list your LinkedIn accounts to check the connection.
{
"inputs": [
{
"type": "promptString",
"id": "finchreach-key",
"description": "Finchreach API key",
"password": true
}
],
"servers": {
"finchreach": {
"type": "http",
"url": "https://mcp.finchreach.com/mcp",
"headers": {
"Authorization": "Bearer ${input:finchreach-key}"
}
}
}
}Replace lk_YOUR_KEY with your key. The step-by-step GitHub Copilot guide has every step, a test prompt and troubleshooting.
Common questions
No. With approval mode on, the default, every write GitHub Copilot makes through Finchreach (posts, comments, reactions, messages, invitations) becomes a pending action. You approve or reject it under Approvals before anything happens on LinkedIn.
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.
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.
Third-party facts checked on against GitHub Copilot docs.
