Mocha Passport Developer Center

Passport Home

Member Services

Site Directory

Developers

Privacy

Mocha Messenger Add-ins

Developers

Overview Add-ins Activities Tabs Manifest Submission Security

Add-ins should extend Mocha safely

The first add-in platform is designed around reviewed packages, declared permissions, and classic Messenger-friendly UI entry points.

Available today

Mocha Emoticon Pack files (*.mep) are the first asset-only add-ins. They let users install extra emoticon sets without modifying the Messenger executable.

Planned package type

The generic package format is planned as Mocha Add-in Package (*.mca). A package is a ZIP archive with a root mocha-addin.json manifest, optional icons, and any supported asset files.

ExampleAddIn.mca mocha-addin.json icon.png assets/ toolbar-icon.png

First safe entry points

Entry point	Purpose
emoticonPack	Provide an emoticon pack or reference an included .mep file.
actionPaneLink	Add a declared HTTPS link to the Messenger action pane.
helpLink	Add documentation or support links.
profileLink	Open a publisher profile or service page.
conversationTemplate	Insert user-selected canned text without reading message history.
tabPage	Add a reviewed service or packaged HTML tab to the Messenger tab area.
gameActivity	Launch a reviewed side-by-side Activity Channel experience from a conversation.
statusProvider	Update the user's personal message from a user-approved now-playing source such as Spotify, Apple Music, or Windows Media Player.
companionBridge	Reserve a small local command bridge for a reviewed Mocha Plus!-style companion program.

Music and status integrations

A status provider can request presence.nowPlaying and presence.statusWrite. Messenger should show the user which provider owns the personal message and let the user turn it off at any time.

Messenger tabs

Tabs are planned for Mocha-owned services, reviewed community pages, partner offerings, and small packaged HTML tools. See the tab page for the webview rules and manifest shape.

Read tab documentation

Game Activities are documented separately because they need conversation pairing, packet-rate limits, and a shared channel API. See Game Activities for the developer-preview model.

Executable add-ins are not part of the first public model. Native code, scripts, and background services need a stronger sandbox and signing story before they can be considered. A future Mocha Plus! companion should communicate through the reviewed companion bridge instead of loading code into Messenger.