company_audit_log — Publora MCP Tool
company_audit_log
(company audit log) is one of 30 tools on the
Publora
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call company_audit_log from your client
- Claude Code Publora company_audit_log run in your project directory
- Claude Desktop Publora company_audit_log ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Publora company_audit_log ~/.cursor/mcp.json
- VS Code Publora company_audit_log .vscode/mcp.json
- Zed Publora company_audit_log ~/.config/zed/settings.json
- Windsurf Publora company_audit_log ~/.codeium/windsurf/mcp_config.json
- Cline Publora company_audit_log ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Publora company_audit_log ~/.gemini/settings.json
- Grok Publora company_audit_log .mcp.json (in your project root)
- ChatGPT Publora company_audit_log Settings → Connectors → Advanced → Developer mode
- Claude.ai Publora company_audit_log Settings → Connectors → Add custom connector
- LangChain Publora company_audit_log pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-server https://mcp.publora.com/mcp
Other tools on this server
- company_context
- company_workspaces
- company_team
- company_manage_team
- company_channels
- company_manage_channels
- company_posts
- company_post_approval
- company_save_post
- company_post_action
- company_media
- list_connections
- create_post
- get_post
- update_post
- delete_post
- get_upload_url
- complete_media
- delete_media
- prune_media_reference
- post_stats
- profile_stats
- list_posts
- linkedin_create_reaction
- linkedin_delete_reaction
- linkedin_create_comment
- linkedin_delete_comment
- linkedin_create_reshare
- linkedin_list_mentionables
This list was read from the server itself, by connecting to it and calling tools/list on 24 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.