linkedin-cowork-plugin MCP工具

Setup

Step 3 — Deploy the MCP connector server

The MCP connector must be publicly accessible over HTTPS. Azure App Service is recommended.

Prerequisites: - Azure CLI installed - Logged in: run az login and complete the browser sign-in

Option A — Azure App Service (recommended)

Choose a unique app name: Azure App Service names are globally unique across all Azure customers. Replace YOUR-APP-NAME throughout all commands below with a name of your choosing (e.g. contoso-linkedin-mcp). If the name is already taken, the az webapp create command will fail — just pick a different name and rerun from that step.

```bash

6. Package and deploy the connector code

Deploy only index.js and package.json — Azure runs npm install automatically.

cd connector powershell Compress-Archive -Path index.js, package.json -DestinationPath ..\connector-deploy.zip -Force cd .. az webapp deploy \ --name YOUR-APP-NAME \ --resource-group linkedin-cowork-rg \ --src-path connector-deploy.zip \ --type zip

Your connector will be live at:
`https://YOUR-APP-NAME.azurewebsites.net`

**Verify the deployment:**

Step 7 — Upload and install via M365 Admin Center

1. Go to https://admin.microsoft.com
2. Navigate to Settings → Integrated Apps
3. Click Upload custom apps
4. Select Teams app as the app type
5. Upload your linkedin-cowork-plugin.zip
6. Complete the wizard — when prompted for deployment scope, choose Specific users/groups and add yourself first for testing
7. Click Deploy

Important: Use Integrated Apps (under Settings), not "Manage Apps" under Teams. Integrated Apps is the correct location for Cowork plugins and is what triggers the deployment flow that makes the plugin appear in Cowork.

Once deployed, open a Copilot Cowork conversation. The plugin activates automatically when your prompt matches a trigger phrase — no manual enabling required.

---

Usage

Once deployed, start a Cowork conversation and use any of these phrases:

• "Post to LinkedIn about our Q2 results"
• "Write a LinkedIn update saying we just launched our new product"
• "Share on LinkedIn that I'm speaking at [conference name] next month"
• "Post this to my LinkedIn: [paste your content]"

Cowork will:

1. Retrieve your LinkedIn profile to get your author identifier
2. Draft a professional post based on your request
3. Show you the full draft and ask for approval
4. Publish it to LinkedIn once you confirm — and return a direct link to the post

---

4. Set environment variables

Health check — confirms server is running and token is configured

curl https://YOUR-APP-NAME.azurewebsites.net/health

{"status":"ok","service":"YOUR-APP-NAME","version":"1.0.0","linkedinToken":"configured"}

If linkedinToken shows "MISSING", the env var didn't apply — re-run step 4 above.

**Test the MCP tools directly:**

Step 4 — Configure the manifest

Open manifest.json and update these fields before packaging:

Required changes:

Generate a GUID:

PowerShell:

[guid]::NewGuid()

Node.js:

crypto.randomUUID()

Online: https://www.uuidgenerator.net

Important: The developer.websiteUrl, privacyUrl, and termsOfUseUrl must be real, reachable URLs. M365 Admin Center validates them on upload and will reject the package if they contain placeholder values like yourorganization.com.

---

MCP tools reference

Reference links

LinkedIn: - Developer Portal - OAuth Token Generator - Posts API documentation - OAuth 2.0 scopes

Microsoft: - Copilot Cowork plugin development - Integrated Apps in M365 Admin Center - Frontier program - Azure CLI install

LinkedIn Post Plugin for Microsoft Copilot Cowork

A Microsoft 365 Copilot Cowork plugin that lets Cowork draft and publish LinkedIn posts on your behalf, using a Node.js MCP (Model Context Protocol) server as the backend connector.

Requires: Microsoft 365 Copilot with Cowork (currently available via the Microsoft Copilot Frontier program)

---

Step 6 — Package the plugin

Windows (PowerShell):

Compress-Archive -Path manifest.json, color.png, outline.png, skills `
  -DestinationPath linkedin-cowork-plugin.zip -Force

macOS / Linux:

zip -r linkedin-cowork-plugin.zip manifest.json color.png outline.png skills/

Do not include the connector/ folder in the plugin zip — the MCP server is deployed separately to Azure. The zip only needs the manifest, icons, and skills folder.

---

Troubleshooting

Plugin doesn't appear in Cowork after deployment - Confirm you deployed via Settings → Integrated Apps, not Teams admin center - Allow up to 15 minutes for the deployment to propagate - Try starting a fresh Cowork conversation

"Unable to connect" or connector not found errors - Run the health check: curl https://your-server.azurewebsites.net/health - Confirm linkedinToken shows "configured" not "MISSING" - Confirm the mcpServerUrl in your manifest ends with /mcp and matches your deployed server exactly

Post publishes but only shows partial content - Confirm your MCP server is running the latest index.js - Check Azure logs: az webapp log tail --name YOUR-APP-NAME --resource-group linkedin-cowork-rg - The full post text is passed as a single string — truncation usually indicates a cold-start timeout; upgrade from F1 to B1 tier if on free plan

Token expired - Follow the Refreshing an expired token steps above - Symptoms: get_linkedin_profile returns a 401 error in the Azure logs

Deployment zip rejected by M365 Admin Center - Confirm id is a real GUID (not the placeholder a1b2c3d4-...) - Confirm developer.websiteUrl, privacyUrl, and termsOfUseUrl are real reachable URLs - Confirm color.png and outline.png are included in the zip at the root level

---