Enable MCP in four steps
1
Create an access token
An administrator creates a bearer token and stores it as a server secret.
An administrator creates a bearer token and stores it as a server secret.
2
Connect your MCP client
Use the remote endpoint below in Codex, OpenCode, or another MCP client.
Use the remote endpoint below in Codex, OpenCode, or another MCP client.
3
Choose a site scope
Site-scoped tools require a site ID for reviews, activity, conversations, and Zernio operations.
Site-scoped tools require a site ID for reviews, activity, conversations, and Zernio operations.
4
Connect Google and Zernio
Connect a verified Google Business Profile through Social API Setup before requesting reviews.
Connect a verified Google Business Profile through Social API Setup before requesting reviews.
Remote MCP connection
Endpoint
POST https://commander.stouterenterprises.com/mcp
Authentication header
Authorization: Bearer YOUR_TOKEN
OpenCode-style configuration
{"mcp":{"sitecommander":{"type":"remote","url":"https://commander.stouterenterprises.com/mcp","headers":{"Authorization":"Bearer YOUR_TOKEN"}}}}
What you can connect
Use the read tools to inspect status, sites, tasks, activity, conversations, reviews, and Zernio accounts. Site-scoped tools always require the site ID permitted by the token.
See the complete discovery and endpoint reference →
Keep the token private
Never expose bearer tokens. Use MCP and the API from your server or AI-client configuration. Do not put a token in public HTML, browser JavaScript, or a client-side app bundle.