# How to connect LinkedIn to Muse

> Connect LinkedIn to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

- Page: https://www.agent200.com/tools/linkedin/framework/muse/
- Connector: [LinkedIn](https://www.agent200.com/tools/linkedin.md)
- Framework: Muse
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect LinkedIn to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/linkedin/framework/muse/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Muse's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure LinkedIn is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Muse: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Muse's exact menus or commands.
4. The first LinkedIn request returns an authorization link if the user has not connected LinkedIn yet: show it to them and continue once they have approved access on LinkedIn's own page.
5. Check it works with this request: "Post this product update to my LinkedIn"
   What should come back:
   - An answer built from your own LinkedIn data.
   - Behind the scenes, Muse calls an Agent200 tool for LinkedIn, such as `linkedin_get_profile`.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in LinkedIn, then retry.

## Overview

This guide connects LinkedIn to Muse through Agent200's MCP server. When you finish, Muse can search, read and act in LinkedIn with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Muse with your Agent200 API key. Your LinkedIn account is connected through managed OAuth: you approve access once on LinkedIn's own page, and Agent200 keeps the connection working.

- **Connector:** [LinkedIn](https://www.agent200.com/tools/linkedin/)
- **Works with:** Muse · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/tools/linkedin/framework/muse/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **LinkedIn enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a LinkedIn account.** They approve access once, on LinkedIn's own page.
- **Muse, with custom MCP servers allowed.** Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

## Connect LinkedIn to Muse

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Muse in the next step, as "Authorization: Bearer <your key>". One key covers LinkedIn and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Ask Muse to create a custom connector

Start a new Muse chat and send this message. Muse builds the connector and shows a button to add your API key.

File `Muse chat`:

```text
Create a Custom Connector for the Agent200 remote MCP server and connect to it:
Name: Agent200
Transport: remote streamable HTTP
URL: https://api.agent200.com/mcp/
Auth: API key sent in the Authorization header as "Bearer <key>"
Open the secure credentials store so I can enter the API key there, not in this chat.
Then list its tools to confirm the connection works.
```

### Step 3: Add your key in the secure sheet

Tap the button Muse shows to open **Add custom connector**, paste your Agent200 API key and tap **Add**. Muse keeps it in its Secure Credentials Store and lists the Agent200 tools once the connection works.

### Step 4: Using Muse Code? Add the server to its settings

In the terminal version, declare the server in `~/.config/muse/settings.json` and export `AGENT200_API_KEY` in your shell instead of writing the key in the file. Run `/mcp` in a session to see it.

File `~/.config/muse/settings.json`:

```json
{
  "schema_version": 1,
  "mcp_servers": {
    "agent200": {
      "transport": "streamable_http",
      "url": "https://api.agent200.com/mcp/",
      "headers": { "Authorization": "Bearer ${AGENT200_API_KEY}" },
      "enabled": true,
      "mode": "optional"
    }
  }
}
```

### Step 5: Connect your LinkedIn account

The first time you ask Muse for something in LinkedIn, Agent200 returns an authorization link. Open it and approve access on LinkedIn's own page. Agent200 stores the connection and keeps it working; your password never reaches Muse or Agent200.

## Test your connection

Ask: "Post this product update to my LinkedIn"

What should come back:

- An answer built from your own LinkedIn data.
- Behind the scenes, Muse calls an Agent200 tool for LinkedIn, such as `linkedin_get_profile`.

If Muse shows an authorization link instead, you have not connected LinkedIn yet: open it, approve access, then ask again.

## LinkedIn tools Muse can call

- **Get the profile** (`linkedin_get_profile`, read): Read the signed-in member's name, photo and email address.
- **Create a post** (`linkedin_create_post`, write): Publish a text, link or image post as the member.
- **Upload an image** (`linkedin_upload_image`, write): Upload an image to attach to a post.
- **Comment on a post** (`linkedin_create_comment`, write): Add a comment to a post as the member.
- **Delete a post** (`linkedin_delete_post`, write): Remove a post the member published.
- **Post as a page** (`linkedin_create_page_post`, write): Publish a post for a LinkedIn Page the member administers, where page permissions are available.

## How it works

1. **You ask Muse.** In your own words, for something in LinkedIn.
2. **Muse picks a tool.** It sees the LinkedIn tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own LinkedIn connection, within the tools and scopes your project allows.
4. **Muse answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's LinkedIn account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and LinkedIn enforces what its API grants.

## Troubleshooting

### You pasted the API key into the chat

Create a new key on the API keys page, stop using the old one, and enter the new one only through the secure Add custom connector sheet. Keys typed in a chat stay in its history.

### Muse returns unauthorized when it lists the tools

Ask Muse to update the Agent200 connector’s credential and enter the key again in the secure sheet. Say that it goes in the Authorization header with the Bearer prefix.

### Muse asks for a local command or a package

Answer that Agent200 is a hosted server over remote streamable HTTP, with API key sign-in. Nothing has to be installed.

### Muse does not use Agent200 in a later chat

Start a new chat after connecting, and name Agent200 and LinkedIn in the request.

### Muse shows a LinkedIn authorization link

You have not connected LinkedIn yet, or the connection needs to be approved again. Open the link, approve access on LinkedIn's own page, then ask Muse again.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that LinkedIn and the tools you need are enabled in the dashboard's Connectors settings, and that you granted LinkedIn the access the task needs.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), replace it in Muse's MCP settings, and stop using the old one. Paste the key only into Muse's settings, never into a chat.

## Use LinkedIn with another framework

- [LinkedIn + Claude](https://www.agent200.com/tools/linkedin/framework/claude.md)
- [LinkedIn + ChatGPT](https://www.agent200.com/tools/linkedin/framework/chatgpt.md)
- [LinkedIn + Claude Code](https://www.agent200.com/tools/linkedin/framework/claude-code.md)
- [LinkedIn + Grok Bot](https://www.agent200.com/tools/linkedin/framework/grok-bot.md)
- [LinkedIn + OpenAI Dots](https://www.agent200.com/tools/linkedin/framework/openai-dots.md)
- [LinkedIn + Claude Duet](https://www.agent200.com/tools/linkedin/framework/claude-duet.md)
- [LinkedIn + Hermes Agent](https://www.agent200.com/tools/linkedin/framework/hermes-agent.md)
- [LinkedIn + OpenClaw](https://www.agent200.com/tools/linkedin/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
