xqboost MCP Server
MCP server that gives Claude direct read/write access to xqboost's tweet queue, session notes, and project sources
a bridge between the AI and its own tweet queue.
during conversations, interesting things happen — funny moments, failures, breakthroughs. this tool lets the AI write those moments down immediately, straight into xqboost's database.
why it exists
• the tweet bot was making things up — right voice, no real stories
• session notes had to be manually batched and deployed
• no way to manage the tweet queue from inside a conversation
what it does
• logs real moments as they happen during sessions
• reads and writes to the tweet queue directly
• checks which projects still need coverage
• manages topics, sources, and draft status
how it works
• something notable happens in a conversation
• the AI calls add_note immediately — tagged, timestamped, linked to a project
• the draft generator picks up real notes instead of inventing stories
• once a note is used in a tweet, it's marked so it never repeats
the tools (11 total)
• add_note — saves a real moment from a session. includes tags like "funny" or "milestone" and links to the relevant project
• list_notes — shows all saved notes. can filter to only show ones not yet used in a tweet
• add_tweet — creates a new draft and drops it into the queue
• list_tweets — shows what's in the queue. filter by draft, approved, or posted
• update_tweet / delete_tweet — edit or remove tweets
• list_sources / update_source — manage tracked projects and their priority
• list_topics / add_topic — manage standalone tweet topics
• get_coverage — quick summary of what needs attention
under the hood
• MCP (model context protocol) — an open standard that lets AI talk to external tools during a conversation. like giving the AI a phone line to its own systems
• Firestore — the cloud database where xqboost stores tweets, notes, and project data. real-time sync, hosted by Google
• service account — a secure key file that lets the server access the database without needing a login. stored locally, never exposed
11 tools. runs locally. no hosting costs. built in 30 minutes because the artlu-tracker MCP already existed as a template.
stack
← select a file to view