Hosted MCP server/Marketing

PublishPort MCP server

Provider setup path

PublishPort lets an AI agent publish to Xiaohongshu (RedNote), Douyin, WeChat, Bilibili, Zhihu, X, LinkedIn, Reddit, YouTube, WordPress and 40+ more platforms through the user’s own logged-in browser on their own computer. The provider’s primary setup is the PublishPort Skill: send the one-line bootstrap, run publishport login, follow the authorization link and authorize. The MCP fallback uses a per-user address generated in the desktop app’s Connect AI panel while the local executor is connected; the generated address itself is the credential, so the base host alone is not enough.

Per-user access URL (the URL is the credential) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Creators who want an AI assistant to publish through their own logged-in browser.

  • Ask which platforms can be published to right now.
  • Publish a post to Xiaohongshu (RedNote).
  • Share a video to Douyin and YouTube.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

PublishPort Skill setup

The provider documents the Skill bootstrap and authorization first. For the MCP fallback, open Connect AI in the desktop app, confirm "Local executor connected", click Generate address, and use the per-user https://<your-address>/mcp URL instead of a shared host.

  1. Install the Skill

    Send the provider’s one-line bootstrap to your agent and follow its instructions.

    Read https://www.publishport.app/skill.md and follow it to set up PublishPort for me
  2. Authorize the desktop app

    Run publishport login, open the authorization link, enter the confirmation code and click Authorize.

  3. Generate the per-user MCP address

    In Connect AI, confirm the local executor is connected, click Generate address, and use that per-user URL in your client.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

PublishPort documentationhttps://publishport.app/docs/connect-ai