Build in Public MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWITTER_API_KEY | Yes | Twitter API Key (Consumer Key) | |
| TWITTER_API_SECRET | Yes | Twitter API Secret (Consumer Secret) | |
| TWITTER_ACCESS_TOKEN | No | Skip OAuth - use access token directly | |
| TWITTER_ACCESS_SECRET | No | Skip OAuth - use access secret directly |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tweetC | Post a tweet immediately for build in public. Requires authentication. |
| threadA | Create a Twitter thread from multiple messages. Posts tweets in reply chain. |
| setup_authA | Setup Twitter authentication via OAuth 1.0a (PIN-based flow). Call without PIN to get authorization URL, then call again with PIN to complete. |
| statusB | Check authentication status and storage location |
| suggestC | Generate intelligent tweet suggestions based on session context |
| save_contextB | Save session context for later analysis and suggestions |
| get_contextC | Retrieve current session context |
| mcp__bip__configureB | Configure user preferences for Build in Public (language and features) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| retro | Analyze your entire coding session and generate tweet suggestions about what you accomplished |
| quick | Post a quick tweet with a custom message |
| suggest | Get AI-powered tweet suggestions based on current session context |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a distinct purpose: authentication, context management, tweeting, threads, suggestions, and configuration. There is no overlap or ambiguity.
Naming patterns are inconsistent: some use verb_noun (get_context, save_context, setup_auth), others are single verbs (suggest, thread, tweet) or nouns (status), and one has a non-standard prefix (mcp__bip__configure).
8 tools is well-scoped for a build-in-public Twitter client, covering authentication, context, posting single tweets, threads, and suggestions without being excessive.
Core posting workflow is covered (tweet, thread, auth, context), but lacks tools for deleting tweets, viewing history, or scheduling, which are minor gaps.