Add the connector
In settings, go to connectors and add a custom connector with the URL https://nilyo.com/mcp, choosing OAuth. Claude registers itself through dynamic client registration and opens a browser once so you authorize the accounts it may reach. The same connected accounts are then available on claude.ai, in the desktop app and in Claude Code.
Reading widely, writing narrowly
Ask for the outcome and leave the path open. Prepare my follow-up with Ada is enough: Claude opens the profile, reads the conversation, checks whether an invitation is pending, notices you answered last, and tells you there is nothing to send. That loop is worth more than any single tool, and reading costs nothing but a few actions.
“Prepare my follow-up with Ada: check what we already said before drafting.”
“Who am I meeting tomorrow, and what did we last say to them?”
Put your rules in a Project
A Claude Project keeps instructions across conversations: who you never contact cold, which account to use for what, when to ask before sending, the tone of your replies. The tools stay the same; the judgement around them becomes yours instead of being re-explained in every chat.
Claude Code counts too
The same connector works from the terminal, which is useful when the task is a script rather than a conversation: pull the week’s conversations into a file, cross a list of prospects with your network, generate a report. It is the same account and the same pacing.
What stays out of reach
Claude cannot exceed what your account can do: nothing private about people you are not connected to, no premium search without the seat. Writes are explicit, ambiguity blocks them, and a daily budget applies per account, reads included.
Common questions
Which Claude products support this?
Any that accept a custom MCP connector: claude.ai, the desktop app and Claude Code. It is the same server and the same connected accounts across all three.
Is a paid plan required?
You need a plan that allows custom connectors. The accounts themselves need nothing special.
Does Claude need my passwords?
No. You sign in through a hosted flow when connecting an account; Claude only ever receives tools, never a credential.
Why is Claude better at this than a fixed automation?
Because the useful work is deciding what to read next. It gathers context across several accounts before proposing, which is exactly what a single-step integration cannot do.
How LinkedIn works with Nilyo
Connection. Secure hosted sign-in (your LinkedIn credentials go to LinkedIn, never to the agent). Sales Navigator and Recruiter are detected automatically when your account has them.
What your agent can do. People and company search, profile lookup from a name or URL, your network and invitations, private conversations (classic, Sales Navigator, Recruiter inboxes), posts, comments and reactions, job postings and applicants, Recruiter projects.
Pacing and safety. About 100 actions per day per account, profile views and searches included; calls are serialized so an agent can never run LinkedIn requests in parallel.
- Profile URLs are resolved to stable profile IDs before any action.
- Invitations carry an optional note of up to 300 characters.
- Private or restricted profiles return an explicit “not accessible” result instead of a retry loop.
All LinkedIn guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.