How to Connect COSMO to LinkedIn (2026 Guide)

You ask Google COSMO to research a list of target accounts. It reads their sites, drafts a summary, and even suggests a calendar slot to follow up. Then you ask it to send the connection requests on LinkedIn. Nothing happens. This is the moment most people start searching how to connect COSMO to LinkedIn, and the honest answer surprises them.

COSMO is an experimental, Android-only agentic assistant that leaked in May 2026. It can act on the open web through a browser agent. It cannot log into LinkedIn and run real prospecting.

That channel gap is fixable. The path runs through MCP, not through a browser tab.

Key Takeaways

• COSMO can browse and act on the public web, but it has no native LinkedIn outreach or B2B messaging channel.
• Browser automation against LinkedIn is fragile and risky; an MCP server with LinkedIn capabilities is the stable route.
• Once connected, COSMO can send connection requests, write messages, search leads, and pull high-intent signals.

What Is Google COSMO?

COSMO is Google's experimental agentic assistant for Android, leaked in May 2026. It does more than answer questions. It thinks and acts, running deep research, document and browser tasks, and calendar suggestions through an agent layer. Treat it as early and forward-looking, not a shipped product you can rely on today.

Under the hood, COSMO runs Gemini Nano on-device. It offers Nano-only, cloud, and hybrid modes, so light tasks stay local and heavier reasoning can reach the cloud. The agentic actions flow through a browser-automation agent called Mariner.

What Mariner actually does

Mariner drives a browser the way a person would. It clicks, reads pages, fills forms, and chains steps toward a goal. That works well for booking, comparison shopping, and pulling data off public sites.

Why Can't COSMO Reach LinkedIn on Its Own?

COSMO cannot run LinkedIn outreach on its own because Mariner is a general web agent, not a B2B channel. It can open linkedin.com, but it has no reliable, account-safe way to send invites, manage threads, or search leads at the depth real prospecting needs. The gap is structural, not a missing setting.

LinkedIn is a logged-in, defended environment. A general browser agent poking at it looks like exactly the kind of activity LinkedIn tries to block. The mistake most teams make is assuming any agent that can browse can therefore prospect. Browsing a public page and operating a private account are different problems.

Browser agents versus a real channel

Tools like Phantombuster and Dripify already automate LinkedIn through the browser, and they break when the interface shifts. Pointing COSMO's Mariner agent at the same surface inherits the same fragility. You want a connection that talks to a stable interface instead.

Want the stable route now? Get your API key and skip the browser entirely.

How Do You Connect COSMO to LinkedIn?

You connect COSMO to LinkedIn by giving it an MCP server that exposes LinkedIn actions as tools. Instead of asking Mariner to click around the site, COSMO calls clean functions like send-invite or search-leads. The agent keeps its reasoning, and the channel work happens through a defined interface built for outreach.

The setup mirrors how you would wire any agent to an outreach layer. The pattern is the same one we cover in our guide on how to connect Claude to LinkedIn, and the steps carry over cleanly.

The basic flow

1. Get an API key for an MCP server with LinkedIn capabilities.
2. Register that server as a tool source COSMO's agent can call.
3. Authenticate your LinkedIn account once through the API.
4. Let COSMO invoke outreach actions by name instead of by clicking.

Because COSMO runs Gemini Nano, the same approach we describe for how to connect Gemini to LinkedIn applies almost word for word. The model family is shared, so the tool-calling shape lines up.

What Can COSMO Do Once It Has LinkedIn Access?

Once connected, COSMO can run a full outreach loop. It can send connection requests, write and send messages, comment, and like. It can search leads by title, company, location, industry, and seniority. It can pull high-intent signals, such as people reacting to a competitor's post, and enrich verified professional emails from a profile.

This is where COSMO's research strength pays off. It already reads accounts well. Now it can act on what it found.

A concrete scenario

Say COSMO finds twenty people who reacted to a rival's launch post. In our experience, that reaction list is some of the warmest signal on LinkedIn. COSMO can score those profiles, draft a tailored note for each, and queue connection requests, then follow up by email and WhatsApp in one sequence.

The research and the action stop being separate tools. COSMO reads a prospect's recent posts, notes what they care about, and writes a first line that proves it actually looked. A rep doing this by hand manages maybe thirty a day. The same loop, run through an API, handles that volume before lunch and keeps the personalization the rep would have added.

Why this beats a browser script

A browser script handles one click path and falls over on the next layout change. When we tested the difference, the API route kept running while the agent focused on judgment, like who to contact and what to say, rather than on finding the right button.

Ready to give COSMO a real channel? Grab your API key and connect it once.

Is This Safe for Your LinkedIn Account?

It is safer than pointing a raw browser agent at LinkedIn, but no automation is zero risk. An MCP server with LinkedIn capabilities respects sane action limits and behaves predictably, which matters far more than raw speed. The fastest way to trouble is blasting hundreds of invites in an hour.

Keep volumes human. Space actions out. We learned that steady, modest daily activity reads as normal far better than a single large burst, regardless of which agent triggers it.

Honest limits to remember

COSMO itself is experimental and Android-only right now, so treat any setup as forward-looking. Test on a small audience first. Keep a human reviewing the messages COSMO drafts before they go out, at least early on.

One more habit worth keeping. Watch the acceptance and reply rates, not just the send count. A drop in either is the early sign that your volume is reading as automated, well before LinkedIn does anything about it. Pull back, and the account stays healthy. The agent gives you reach, but the judgment about pace stays yours.

How Do You Keep COSMO Running the Workflow?

You keep the workflow running by scheduling it, not by babysitting COSMO. For recurring outreach, Claude Cowork and Claude Code routines are clean native options for triggering the same sequence on a cadence. They call the same MCP tools COSMO uses, so the outreach logic stays in one place.

A daily routine might pull fresh high-intent signals each morning, enrich the new profiles, and queue a small batch of invites. COSMO handles the reasoning when you are in the loop; a routine handles the repetition when you are not.

Where LinkupAPI fits

The channel layer in all of this is LinkupAPI, the API that connects AI agents to LinkedIn, email, and WhatsApp through MCP. It gives COSMO the outreach actions Mariner cannot safely perform on its own, which is the whole point of this connection.

That split is the takeaway. Let COSMO do what it is good at, reading, reasoning, and deciding. Let a dedicated channel handle the part a browser agent cannot do safely. Connect the two once, and the assistant that could only suggest outreach can finally run it.

FAQ

Is Google COSMO publicly available?

No. COSMO is an experimental, Android-only assistant that leaked in May 2026. It is not a public, shipped product yet. Treat any integration as forward-looking and expect behavior, names, and capabilities to change before any wider release.

Does COSMO support MCP?

COSMO is built around an agentic, tool-calling design, which is the model that MCP serves. Connecting it to an MCP server with LinkedIn capabilities lets COSMO call outreach actions as named tools instead of driving the LinkedIn site through its Mariner browser agent.

Can COSMO send LinkedIn messages by itself?

Not reliably. COSMO's Mariner agent can open LinkedIn in a browser, but it has no safe, native channel for sending invites or messages at scale. Real outreach needs an API layer that exposes those actions through a stable interface built for prospecting.

What is the Mariner agent?

Mariner is COSMO's browser-automation agent. It drives a web browser like a person, clicking, reading, and filling forms to complete tasks. It is strong on the open web but fragile against defended, logged-in sites such as LinkedIn, which is why an API route works better.

Does COSMO run on-device?

Partly. COSMO runs Gemini Nano on-device and offers Nano-only, cloud, and hybrid modes. Light tasks can stay local for speed and privacy, while heavier reasoning reaches the cloud. The outreach channel itself runs through an external API regardless of which mode is active.