Can Microsoft Copilot connect to LinkedIn?
It depends which Copilot. Copilot Studio and GitHub Copilot in VS Code can add Kiin as a remote MCP server. Microsoft 365 Copilot can, through an admin-built connector. The consumer Microsoft Copilot app (copilot.microsoft.com) cannot: it only offers Microsoft's own connectors.
| Copilot surface | Remote MCP with OAuth? | Source |
|---|---|---|
| Copilot Studio (agents for Microsoft 365 and Teams) | Yes | Microsoft Learn |
| GitHub Copilot in VS Code | Yes | VS Code docs |
| Microsoft 365 Copilot (federated connector) | Admin only | Microsoft Learn |
| Consumer Copilot app | No | Microsoft Support |
How to connect LinkedIn Ads to Copilot Studio
Open your agent, go to Tools → Add a tool → New tool → Model Context Protocol, enter https://mcp.kiin.co/mcp, choose OAuth 2.0 with Dynamic discovery, and create it. Copilot Studio supports streamable HTTP only, so use the /mcp path rather than /sse.
- Sign up for Kiin with LinkedIn and connect your ad account.
- In Copilot Studio, open the agent and select Tools → Add a tool → New tool → Model Context Protocol.
- Server name:
Kiin. Description: LinkedIn Ads reporting, audits, benchmarks and campaign changes. Server URL:https://mcp.kiin.co/mcp. - Authentication: OAuth 2.0 → Dynamic discovery. Create, then sign in with your Kiin (LinkedIn) login when prompted.
- Test the agent with “What did we spend on LinkedIn last month?”
How to connect LinkedIn Ads to GitHub Copilot in VS Code
Run MCP: Add Server from the Command Palette, choose HTTP, paste https://mcp.kiin.co/mcp and name it kiin, or add the JSON below to .vscode/mcp.json. VS Code opens the OAuth sign-in when Copilot first uses the server.
{
"servers": {
"kiin": {
"type": "http",
"url": "https://mcp.kiin.co/mcp"
}
}
}
Can Microsoft 365 Copilot use Kiin?
Only through an admin-built federated connector, and we have not confirmed it with Kiin. Microsoft's docs have a Global or AI Administrator create it in the Microsoft 365 admin center (Copilot → Connectors → Gallery → Create a new connector → Connect to MCP server) with an OAuth client pre-registered in Teams Developer Portal. Kiin uses dynamic client registration, so ask us before you try this route.
Why can't the Copilot app connect to LinkedIn Ads?
Because consumer Copilot has no custom connector option. Under Profile → Connectors it offers OneDrive, Outlook.com, Google Drive and Gmail only. If you want LinkedIn Ads in a Microsoft assistant, use Copilot Studio, or use Claude, ChatGPT or Grok, which all accept Kiin.
First prompts to try in Copilot
In Copilot Studio, tell the agent when to use Kiin; in VS Code, ask for files.
- “(Agent instructions) Use the Kiin tools for any LinkedIn Ads question, and say which ad account and date range you used.”
- “(In Teams) What did we spend on LinkedIn last month, and what did a lead cost?”
- “(VS Code) Use kiin to pull last month's campaign metrics and write them to linkedin-report.csv.”
- “(VS Code) Compare cost per lead across our campaigns with similar advertisers and write the three worst to a markdown table.”
If it does not work in Copilot
Most Copilot problems are the wrong URL or the wrong Copilot.
- Copilot Studio will not connect. It supports streamable HTTP only. Use
https://mcp.kiin.co/mcp, not/sse. - No sign-in appears. Set Authentication to OAuth 2.0 with Dynamic discovery, not API key, then create the tool again.
- You are in the Copilot app. copilot.microsoft.com has no custom connectors. Use Copilot Studio, or Claude, ChatGPT or Grok.
- You want Microsoft 365 Copilot. That route needs an admin-built federated connector with a pre-registered OAuth client. Kiin uses dynamic registration, so talk to us first.
Other assistants
Setup guides for Claude · ChatGPT · Claude Duet · Cursor and Claude Code · Gemini · Grok · OpenAI dots · Perplexity. Every client and the full comparison: LinkedIn Ads MCP server.
Stuck, or setting this up for a team? Book a call →