draft_linkedin_pl — Content Ops PL MCP Tool
draft_linkedin_pl
(draft linkedin pl) is one of 4 tools on the
Content Ops PL
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call draft_linkedin_pl from your client
- Claude Code Content Ops PL draft_linkedin_pl run in your project directory
- Claude Desktop Content Ops PL draft_linkedin_pl ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Content Ops PL draft_linkedin_pl ~/.cursor/mcp.json
- VS Code Content Ops PL draft_linkedin_pl .vscode/mcp.json
- Zed Content Ops PL draft_linkedin_pl ~/.config/zed/settings.json
- Windsurf Content Ops PL draft_linkedin_pl ~/.codeium/windsurf/mcp_config.json
- Cline Content Ops PL draft_linkedin_pl ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Content Ops PL draft_linkedin_pl ~/.gemini/settings.json
- Grok Content Ops PL draft_linkedin_pl .mcp.json (in your project root)
- ChatGPT Content Ops PL draft_linkedin_pl Settings → Connectors → Advanced → Developer mode
- Claude.ai Content Ops PL draft_linkedin_pl Settings → Connectors → Add custom connector
- LangChain Content Ops PL draft_linkedin_pl pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http content-ops-pl https://x402-content-ops-pl.mint-silverfish.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 26 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.