# Connect Hermes to SocialCannon Public setup instructions, not an MCP endpoint. Pasting a prompt does not complete the connection. ## 1. Human account Create a free account at https://socialcannon.app/sign-in using Google or GitHub. No card is required. Credentials are at https://socialcannon.app/dashboard/settings?tab=api-keys . The Client Secret is shown once. If it is missing, explain that generating a replacement invalidates the old secret; obtain permission before rotating it. Have the human supply SOCIALCANNON_CLIENT_ID and SOCIALCANNON_CLIENT_SECRET privately through the environment or the host's secret configuration. Never ask for secrets in chat, URLs, source control or logs. Preserve existing configuration and permissions. ## 2. Connect Hermes via stdio MCP Requires Node.js 18+ and npx available to the process running Hermes. Merge the following into ~/.hermes/config.yaml. If mcp_servers already exists, add socialcannon beneath it; do not create a second key or overwrite other servers. Read existing configuration privately and do not echo secrets. mcp_servers: socialcannon: command: "npx" args: ["-y", "@socialcannon/mcp@1.0.2"] env: SOCIALCANNON_CLIENT_ID: "${SOCIALCANNON_CLIENT_ID}" SOCIALCANNON_CLIENT_SECRET: "${SOCIALCANNON_CLIENT_SECRET}" The variables must be available in the environment that starts Hermes. Hermes resolves the references; never replace them with secrets in chat. Use /reload-mcp in Hermes or restart the session after saving. If credentials were added to a parent shell after Hermes started, restart Hermes from that environment. Use the host's current documentation if its configuration differs: https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp This is an independent SocialCannon integration, not an official Nous catalog listing. ## 3. Verify and try a practice post Discover the MCP tools, then call list_accounts to verify authenticated access. Tool discovery alone is not proof of a working account connection. With the human's agreement, call create_post with accountId="sandbox" and content="My first SocialCannon sandbox post". Do not set scheduledAt. This simulates publishing; report it as a sandbox test only after the tool confirms success. Stop and explain errors without exposing credentials. For a real destination, have the human authorize their social account at https://socialcannon.app/dashboard/accounts . Call list_accounts again and verify the intended destination exists. Connecting does not authorize posting. Prepare drafts with the human; obtain explicit approval before real publishing, scheduling, replies, retries, deletion, disconnection or credential changes. create_post without scheduledAt publishes immediately; it does not save a draft. Platform capabilities: https://socialcannon.app/api/v1/platforms . Media requirements, quotas and feature availability vary by platform and plan: https://socialcannon.app/pricing . SocialCannon does not read or reply to private social DMs. Support: support@socialcannon.app REST reference: https://socialcannon.app/docs