Use Manus to prep for meetings with LinkedIn research

The short answer

Yes, Manus can prep you for a meeting using LinkedIn. Connect Finchreach to Manus as a custom MCP server, then hand Manus the names on your calendar invite. It finds each person and their company on LinkedIn, reads what they have posted lately, writes a one-page brief, and can draft a short connection invitation for each attendee. The research is read-only. The invitations wait in your Finchreach approval queue until you approve them, so nothing goes out in your name without you seeing it first.

MCP (Model Context Protocol) is a standard plug that lets AI apps use outside tools. Finchreach is a remote MCP server for LinkedIn at https://mcp.finchreach.com/mcp. Manus supports custom MCP servers with a header, which is what Finchreach needs, so this is a direct connection with no bridge in between.

Why use Manus for meeting prep instead of a chat assistant?

Meeting prep is a multi-step errand: find the right profile among people with the same name, check the company, skim recent posts, look for shared connections or topics, then condense it all into something you can read in two minutes. Manus is built to work through tasks like that on its own and hand back a finished result. You give it the goal once instead of steering it through every lookup.

With Finchreach connected, Manus can use these LinkedIn tools during the task:

• linkedin_search with the people vertical to find each attendee by name and company: headline, location, connection degree and mutual connections, optionally filtered to 1st, 2nd or 3rd+ degree.
• linkedin_search with the companies vertical for the company’s industry, location and follower count.
• linkedin_search with the content vertical to find recent posts by or about the person or company.
• linkedin_send_invitation to draft a connection request with an optional note (up to 300 characters), which goes to your approval queue.

Everything except the invitation is a read. Manus can do as much research as the task needs without touching anything visible on LinkedIn.

What should I ask Manus?

Be specific about the meeting, the people and what you want back. A prompt like this works well:

Ask your assistant“I have a call on Thursday with Dana Ortiz (VP Operations) and Sam Lee (Head of Procurement) at Northwind Logistics. Use Finchreach to find both of them on LinkedIn and confirm they work at Northwind. For each person, summarize their headline, location, how we are connected (degree and any mutual connections) and anything they posted or were mentioned in over the last few months. Then give me a one-page brief: three things to ask, one topic to avoid, and any overlap with my own work (I lead partnerships at a freight software company). Don’t send anything.”

Once you have read the brief, you can follow up in the same task:

Ask your assistant“Draft a connection invitation for each of them with a note under 300 characters. Mention Thursday’s call and one specific point from their recent posts. Queue them for my approval.”

If the names are common, add details Manus can match against, such as city or job title. Ask it to tell you when it is not sure it has the right profile rather than guess. That matters more than any formatting detail in the brief.

Ask your assistant“Before the brief, list the LinkedIn profiles you matched and how confident you are in each match. If two profiles could fit, stop and ask me.”

How do I connect Finchreach to Manus?

Setup takes a few minutes. The full walkthrough is in the Manus guide; the short version:

1. Create a Finchreach account and connect your LinkedIn account on the Accounts page.
2. Create an API key on the API keys page. It starts with lk_. Copy it somewhere safe.
3. In Manus, open Settings → Connectors → Add connectors → Custom MCP → Add custom MCP server, and choose direct configuration.
4. Set the transport to HTTP, the URL to https://mcp.finchreach.com/mcp, and add a header named Authorization with the value Bearer lk_... (your key).
5. Save, start a new task, and ask Manus to list your Finchreach LinkedIn accounts to check the connection.

Manus has renamed these menus before (older docs say Settings → Integrations → Custom MCP Servers), and it also offers Import by JSON. If the labels differ, look for the custom MCP option with a custom header field. Manus doesn’t document plan requirements for custom MCP, as of October 2026. See Manus’s custom MCP docs and our quickstart.

What does a good LinkedIn meeting brief include?

Ask for the same structure every time so briefs are quick to scan. A format that works for most sales, partnership and hiring calls:

• Who: name, headline, location and connection degree.
• Company: industry, location and follower count from LinkedIn, plus anything notable it posted recently.
• Recent activity: two or three posts or comments, with a one-line takeaway each.
• Common ground: mutual connections LinkedIn shows, and topics you both post about.
• Questions: three openers grounded in what you found, not generic small talk.

Treat the brief as a starting point. LinkedIn headlines are self-reported and sometimes out of date, and an agent can misread a post. A quick check of anything you plan to mention out loud is worth the minute it takes.

Can Manus send messages or invitations without me?

Not with approval mode on, which is the default for every Finchreach account. Every write, whether a post, direct message, invitation, comment or reaction, becomes a pending action. Manus gets back a status of pending_approval and can check on it later with linkedin_get_action. You open the approvals page, read the exact text, and approve or reject it. Only approved actions run.

This matters for an autonomous agent. Manus may run for a while without you watching, and it reads a lot of text written by other people along the way, some of which could try to steer it. The queue keeps a person between the draft and LinkedIn, and it keeps the pace of your account under your control.

Automating a personal LinkedIn account carries risk under LinkedIn’s User Agreement. The approval queue lowers that risk because a person reviews and paces every action, but it doesn’t remove it. Keep volumes human and only approve what you would have sent yourself.

Manus and LinkedIn: common questions

Does Manus need my LinkedIn password? No. You connect LinkedIn once in the Finchreach dashboard. Manus only holds a Finchreach API key, which you can revoke at any time from the API keys page.

Can Manus post to my company page? No. Finchreach works with personal LinkedIn accounts and text posts today. Company pages, images, video, scheduling and analytics are not supported.

Can I use the same setup in other agents? Yes. The same server and key work in any MCP client that can send a header. See the Claude Code integration or read what a LinkedIn MCP server is.

What if Manus picks the wrong person? Nothing is sent from research alone, and invitations wait for your approval, so a wrong match costs you a rejected draft. Asking Manus to list its matches first, as in the prompt above, catches most mix-ups early.

Ready to try it? Sign up for Finchreach, then follow the Manus guide.