Start the app
For normal use, open File > AI / LLM Control in SSApp and enable the API. SSApp creates and stores a random token; use Copy Control Connection to obtain the local connection details.
For unattended use, store a random token in a user-protected file. Headless mode keeps Electron windows hidden, but Chromium still runs so capture pages continue working.
SocialStream.exe --ssapp-headless-control --ssapp-control-port=17777 --ssapp-control-token-file=C:\secure\ssapp-token.txt
Use --ssapp-control-api instead to keep the normal app window visible. Environment variables are supported too. Avoid putting tokens directly on command lines.
Connect an AI or script
The server listens only on 127.0.0.1. Send the token in X-SSAPP-Token and discover the available controls first.
GET http://127.0.0.1:17777/api/v1/capabilities
GET http://127.0.0.1:17777/api/v1/status
GET http://127.0.0.1:17777/api/v1/events
Capabilities and responses report both the running SSApp version and control API version. Use the advertised command list instead of assuming every app version has the same controls.
Commands use POST /api/v1/command. For example, list sources or reload one:
{"action":"getSources","value":{}}
{"action":"restartSource","value":{"sourceId":"SOURCE_ID","confirm":true}}
What can be controlled
- List, inspect, add, update, and remove sources.
- Start, stop, or reload one source or a filtered set.
- Change source visibility, mute state, and connection mode.
- Read and update the supported global settings returned by capability discovery.
- Read app, session, source, and local-media server status.
- Follow resumable status and operation events for long-running automation.
- Reload or gracefully shut down the app with explicit confirmation.
Install the AI skill
Download the Control Social Stream skill with its API reference, version log, and Python client. Add the skill folder to the skills directory used by your AI tool.
SSApp also ships a stdio MCP adapter at resources/ssapp-mcp.js. Configure an MCP client to run it with Node and provide SSAPP_CONTROL_URL plus SSAPP_CONTROL_TOKEN_FILE. The MCP server filters its tools using the running app's capabilities and reports the SSApp/API version in every result.
Security
Never expose the control port to the Internet, publish the token, or place it behind a public proxy. The public API does not provide arbitrary JavaScript execution, cookies, sign-in secrets, unrestricted settings, or raw filesystem access.