Publish Content to LinkedIn

LinkedIn Post via Publora creates and schedules LinkedIn content through the Publora MCP server. It supports text, single images, multiple images presented as a grid, videos, and PDF documents. Tools also list, update, and delete scheduled or draft posts, allowing the workflow to include management after initial creation.

Setup requires a Publora account, a LinkedIn connection authorized through OAuth, an API key, and MCP configuration. The guide lists LinkedIn access across Starter, Pro, and Premium plans, with different monthly posting allowances. It describes Starter at 15 posts, Pro at 100 per account, and Premium at 500 per account per month.

Use it for scheduling a text announcement, sharing product images, publishing a video, or posting a multi-page PDF with a caption. Multi-image organic posts are grids rather than swipeable carousels. A PDF is the described alternative for multi-page swipeable content.

Do not combine images with video or documents in one post. LinkedIn API text does not provide bold or italic formatting. The guide highlights the first 210 characters before the see-more break and suggests a concise opening, relevant hashtags, and an engagement question. Its audience-time recommendations are posting guidance rather than a guaranteed outcome.

create_post receives a platforms array containing the connected LinkedIn identifier, content up to 3,000 characters, and a required ISO 8601 scheduledTime. For immediate publication, the described convention is the current time plus one minute. Connection identifiers come from the platform-connections response and use the LinkedIn-prefixed format.

get_upload_url receives the postGroupId, file name, MIME type, and media type to obtain a presigned upload URL. The listed image limits are ten images and 5 MB per image, with JPEG, PNG, GIF, and automatically converted WebP. Video is MP4, up to 30 minutes and 500 MB.

Mentions use URN syntax and require a display name matching the profile exactly, including case and company suffixes. Company mentions use an organization URN rather than a person URN. The person-mention example is:

@{urn:li:person:MEMBER_ID|Display Name}       # Mention a person

MCP authentication uses a bearer header, while the REST fallback uses x-publora-key instead. The REST workflow can retrieve connections and create posts when MCP is unavailable. Troubleshooting covers reconnecting expired OAuth, correcting media size or format, retrying rate limits with backoff, and separating mixed media into compatible posts. These checks help distinguish account, upload, request-rate, and service-availability failures.