Skip to content

AI assistants (MCP)

This content is not available in your language yet.

The Model Context Protocol (MCP) is an open standard that lets an AI assistant use tools from other services. Posty5 runs an MCP server, so an assistant you already use can work with your Posty5 account when you ask it to.


Posty5’s tools come in groups. You choose the groups each connection gets, and the access level decides whether the assistant may only read, also create and edit, or also delete.

Group What it covers On for a new connection
account Who the connection is, your credits, and what each action costs Always
short-links Create, find, edit and delete short links Yes
qr-codes QR codes of every type, and the templates that style them Yes
html-hosting Hosted pages, their variables and their form submissions Yes
social-publisher Workspaces, connected accounts, and posts to every platform Yes

Every tool, with its access level

  • Shorten example.com/spring-sale and make a QR code that opens it.
  • Schedule this caption to my Instagram account for Friday at 9 in the morning.

Hosted URL (recommended) Local package
What you add to the assistant https://mcp.posty5.com/t/YOUR-TOKEN/mcp npx -y @posty5/mcp
Where you get it Connect an AI assistant, on one of your API keys Any API key, set in the assistant’s configuration
Access level and groups Chosen in the dashboard Environment variables
How what it creates is marked Created via MCP, confirmed by Posty5’s MCP server Created via MCP, as declared by the package and not verified
Activity log Every call, kept for 90 days None

  • A Developer account and an API key. API keys and authentication
  • An assistant that can add a remote MCP server by URL — or, for the local package, one that can start a local server, with Node.js 20 or later installed.