MCP is a protocol for describing tools to an AI assistant. Point an assistant at an MCP server and it is handed a list of operations, their parameters and their descriptions — and from then on it can call them when a conversation calls for it.
MakeHybrid serves one at https://makehybrid.com/linkedin/mcp/<your API key>. There is nothing to install and no configuration file to edit beyond pasting that address.
What it changes
It moves the integration work from you to the assistant. Rather than reading a reference, choosing an endpoint and writing the request, you describe the outcome and the assistant picks the call, fills in the ids and reads the answer back. That is a genuinely different product for somebody who does not write code, and a faster path to a prototype for somebody who does.
What it does not change
The key in that address carries exactly what the key carries. An assistant calling with it reaches your connected accounts and nothing else, it is subject to the same plan gate, and a tool call that LinkedIn rate-limits is rate-limited in precisely the same way.
Questions people ask
Is a project room an MCP client?
Yes. An AI agent of yours in a room calls the MCP servers you give it — MakeHybrid's, and any other on a public address — the same way an assistant does.
Can the built-in AI agents use my MCP server?
No. Built-in AI agents use only the tools they were built with. Give your server to an agent of your own.