# How to connect Manus to LinkedIn, step by step

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

Create an API key at finchreach.com/api-keys, connect LinkedIn at finchreach.com/accounts, then add `https://mcp.finchreach.com/mcp` to Manus with the header `Authorization: Bearer lk_…`. Test with a read, and approve the first draft under Approvals. One caveat: Manus’s own docs don’t list the header fields; partner guides show API-key headers working.

## What you need

- A Finchreach account (sign in at [finchreach.com](https://finchreach.com/sign-in)) and the LinkedIn account you want Manus to work on.
- Manus (plan requirements aren’t documented).
- About five minutes.

## Step 1: Create a Finchreach API key

1. Sign in at finchreach.com and open [API keys](https://finchreach.com/api-keys).
2. Create a key and name it after the tool, for example “Manus”.
3. Copy it right away: it starts with `lk_` and is shown only once.

## Step 2: Connect your LinkedIn account

1. Open [Accounts](https://finchreach.com/accounts) and click to connect LinkedIn.
2. Follow the steps until the account shows as connected.

Approval mode is on by default: nothing the assistant drafts reaches LinkedIn until you approve it.

## Step 3: Add Finchreach to Manus

1. Settings → Connectors → Add connectors → Custom MCP → Add custom MCP server → Direct configuration. (Older docs: Settings → Integrations → Custom MCP Servers → Add Server.)
2. Transport HTTP, URL `https://mcp.finchreach.com/mcp`, and a custom header `Authorization` = `Bearer lk_YOUR_KEY`. “Import by JSON” takes the same values.
3. Save, then ask Manus to list your LinkedIn accounts.

Import by JSON:
```json
{
  "mcpServers": {
    "finchreach": {
      "url": "https://mcp.finchreach.com/mcp",
      "headers": {
        "Authorization": "Bearer lk_YOUR_KEY"
      }
    }
  }
}
```

> Replace `lk_YOUR_KEY` with your key. Keep the key out of shared files and repos; where Manus can read it from an environment variable, prefer that.

Partner docs (Apify, Ahrefs, Polar) show Manus sending API-key headers; Manus’s own page doesn’t list the fields.

Requirements: Plan requirements aren’t documented.

## Step 4: Test the connection

In Manus, start with a read. It runs right away and proves the key and the account work:

> Ask your assistant: “List my connected LinkedIn accounts, then summarize my five latest notifications.”

You should see calls to `linkedin_list_accounts` and `linkedin_get_notifications`. Then try a write, which goes to your approval queue instead of LinkedIn:

> Ask your assistant: “Draft a short LinkedIn post saying I’m trying a new AI assistant workflow. Submit it for my approval.”

## Step 5: Approve or reject it in Finchreach

1. Open [Approvals](https://finchreach.com/approvals). The draft is there with its exact text and the account it would go out from.
2. Approve it to publish, or reject it (reject the test post if you don’t want it live).
3. Manus can check the result with `linkedin_get_action`: pending, approved, rejected, executed, failed or expired.

## Troubleshooting

- If your Manus UI has no header field, try the JSON import, or use `X-API-Key: lk_YOUR_KEY` if only a single key field is offered.
- 401 or “unauthorized”: the key is wrong, revoked or missing its prefix. Finchreach accepts `Authorization: Bearer lk_…` or `X-API-Key: lk_…`; check for a missing `Bearer `, quotes or a trailing space.
- A tool is missing: the key’s permissions don’t include it. Create a key with the permissions you need under [API keys](https://finchreach.com/api-keys).
- “No LinkedIn account”: connect one under [Accounts](https://finchreach.com/accounts), or reconnect it if its session expired.
- A post or message “didn’t go out”: it is probably still waiting under [Approvals](https://finchreach.com/approvals). Writes run only after you approve them.

Still stuck? Compare your setup with [Manus’s documentation](https://manus.im/docs/integrations/custom-mcp), checked on 2026-10-28; client screens change often.

## What to ask Manus next

> Ask your assistant: “Research these ten companies, find a relevant person at each on LinkedIn, and draft a connection note.”

> Ask your assistant: “Write a LinkedIn post summarizing the market report you just built.”

> Ask your assistant: “Go through my LinkedIn messages and make a table of open questions.”

More ideas on the [Manus integration page](https://finchreach.com/integrations/manus).

## Questions

### I lost my API key. Can I see it again?

No, a key is shown only once. Create a new one under [API keys](https://finchreach.com/api-keys), put it in your config, and revoke the old one.

### Does Manus see my LinkedIn password?

No. Manus only gets your Finchreach API key. Your LinkedIn connection stays in Finchreach, and you can revoke the key at any time without touching LinkedIn.

### Can I use the same key in several tools?

Yes, but one key per tool (for example one named “Manus”) lets you revoke one without breaking the others.

### How do I disconnect Manus?

Revoke its key under [API keys](https://finchreach.com/api-keys); Manus gets a 401 from then on. Then remove the server from its config.

## Sources

- [Manus docs](https://manus.im/docs/integrations/custom-mcp)

## Related

- [What Manus can do on LinkedIn](https://finchreach.com/integrations/manus)
- [Use Manus to prep for meetings with LinkedIn research](https://finchreach.com/blog/manus-linkedin-meeting-prep)
- [Connect Claude Code](https://finchreach.com/guides/claude-code)
- [Quickstart and tools](https://finchreach.com/docs)
- [All setup guides](https://finchreach.com/guides)