Current state
- Build in Public MCP 0.5.0 is installed and is the latest published package.
- The MCP reports
Not authenticated because TWITTER_API_KEY and TWITTER_API_SECRET are not configured.
- Its current
tweet schema accepts only message; it does not accept an image path or upload media.
- The 267-character post is prepared in
docs/submission-draft.md.
- The metadata-stripped launch visual is prepared at
docs/evidence/social/recallops-launch-light.png.
Smallest human-controlled action
- Create or select an X developer app.
- Enable OAuth 1.0a with Read and Write permission.
- Set the API key and secret in the local MCP environment without pasting them into chat or Git.
- Restart Codex so the MCP receives the environment variables.
Then run the MCP PIN authorization flow and publish the approved first post. Attach the prepared image manually unless the MCP gains media upload support. Record the real X status URL before marking this issue complete.
No post is currently claimed as published.
Current state
Not authenticatedbecauseTWITTER_API_KEYandTWITTER_API_SECRETare not configured.tweetschema accepts onlymessage; it does not accept an image path or upload media.docs/submission-draft.md.docs/evidence/social/recallops-launch-light.png.Smallest human-controlled action
Then run the MCP PIN authorization flow and publish the approved first post. Attach the prepared image manually unless the MCP gains media upload support. Record the real X status URL before marking this issue complete.
No post is currently claimed as published.