About this integration
MCP server for MAX Messenger by VK. 21 tools: messages, media, buttons, members, events.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.2.2
- Package
- @woyax/mcp-max-messenger
- Last compatibility test
- Not independently tested
Connect your agent
@woyax/mcp-max-messengerPublisher documentation was reviewed only. Messaging and administration tools can mutate chats; host permissions and a least-privilege bot remain necessary. No package or MAX API endpoint was executed or security-audited.
Capabilities: read and send messages, media delivery, chat administration, member administration, incoming updates and callbacks
Connected profiles
Additional details
io.github.woyaxnini/max-messenger
Source ↗ · Checked 2026-09-171.2.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17MAX_TOKEN
Source ↗ · Checked 2026-09-17@woyax/mcp-max-messenger
Source ↗ · Checked 2026-09-201.2.2
Source ↗ · Checked 2026-09-20After a bot token is provisioned, the MCP client launches the documented stdio server and exposes its tools without a recurring interactive authorization step.
Source ↗ · Checked 2026-09-20A MAX bot token is required and is passed through MAX_TOKEN; the publisher says the upstream API receives it directly in the Authorization header without a Bearer prefix.
Source ↗ · Checked 2026-09-20Configure npx -y @woyax/mcp-max-messenger and MAX_TOKEN in an MCP client's stdio server configuration. The optional hosted HTTP mode is not projected over the existing stdio identity.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20