Publora MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3100 |
| PUBLORA_API_URL | No | Backend API URL | https://api.publora.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsA | List all connected social media accounts (Twitter, LinkedIn, TikTok, etc.) |
| create_postB | Create and schedule a post to one or more social media platforms |
| get_postB | Get details of a scheduled post group and its platform-specific posts |
| update_postA | Update a post's status (draft/scheduled) or scheduled time |
| delete_postA | Delete a scheduled post group and all its platform-specific posts |
| get_upload_urlA | Get a presigned S3 URL to upload media (image/video) for a post |
| list_workspace_usersA | List all managed users in the workspace |
| create_workspace_userB | Create a new managed user in the workspace |
| linkedin_post_statsB | Get engagement statistics for a specific LinkedIn post |
| linkedin_account_statsC | Get aggregated engagement statistics for a LinkedIn account |
| list_postsB | List scheduled/published posts with filtering by status, platform, date range |
| linkedin_followersB | Get LinkedIn followers count or daily growth over a date range |
| linkedin_profile_summaryB | Get combined LinkedIn profile overview: followers + post statistics |
| linkedin_create_reactionC | React to a LinkedIn post (like, praise, etc.) |
| linkedin_delete_reactionB | Remove your reaction from a LinkedIn post |
| workspace_detach_userC | Remove a managed user from workspace |
| linkedin_create_commentC | Post a comment on a LinkedIn post |
| linkedin_delete_commentB | Delete a comment from a LinkedIn post |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action. The LinkedIn tools are clearly grouped, workspace user tools are separate, and post tools handle different CRUD operations without overlap.
Mixed conventions: post tools use verb_noun (create_post), workspace tools mix verb_noun and noun_verb (create_workspace_user vs workspace_detach_user), while LinkedIn tools consistently use linkedin_ prefix followed by action_object. This inconsistency may confuse.
With 18 tools, the server covers workspace management, posting, and LinkedIn analytics. Slightly above the typical 3-15 range, but still reasonable given the scope. Not excessive.
Covers core workflows: post CRUD with scheduling, LinkedIn engagement and stats, workspace user lifecycle (except update/delete user). Minor gaps like missing user update and lack of platform-specific tools for non-LinkedIn accounts, but overall sufficient.