TweetAPI MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWEETAPI_API_KEY | No | Your TweetAPI API key from the dashboard. Required for live data tools when running locally with --live; not needed for docs-only mode or the hosted OAuth server. | |
| MCP_ALLOWED_HOSTS | No | Comma-separated allowed hosts for HTTP mode, for example localhost,127.0.0.1 when running via Docker. |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tweetapi_docs_searchA | Search current TweetAPI public docs from llms.txt and ai-docs-v2.txt. |
| tweetapi_endpoint_lookupA | Find likely TweetAPI endpoint docs by path or keyword. |
| tweetapi_docs_get_pageB | Return a full endpoint documentation section from ai-docs-v2.txt. |
| tweetapi_sdk_guidanceB | Return concise SDK setup and usage guidance for a language/task. |
| tweetapi_tool_catalogB | Return a machine-readable catalog of current TweetAPI MCP tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| integrate_tweetapi | Guide an agent to integrate TweetAPI safely into a customer project. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tweetapi_llms | Current TweetAPI public LLM summary from tweetapi.com. |
| tweetapi_ai_docs_v2 | Current AI-ready TweetAPI endpoint documentation from tweetapi.com. |
TDQS
Scored across 5 tools
The SDK guidance and tool catalog tools are clearly distinct, but docs_search, endpoint_lookup, and docs_get_page all retrieve documentation and have overlapping boundaries. An agent may struggle to choose between search-by-keyword and endpoint lookup, or between lookup and fetching a full page.
All tools use a consistent tweetapi_ prefix and snake_case, which makes the set readable and grouped. However, patterns vary between resource_action (docs_search), resource_verb_noun (docs_get_page), and noun_noun (sdk_guidance, tool_catalog).
Five tools is well-scoped for a documentation and SDK guidance server. Each tool has a plausible role: search, lookup, full-page retrieval, SDK help, and tool discovery.
The surface covers documentation search, endpoint discovery, full endpoint sections, SDK guidance, and a machine-readable catalog. A minor gap is the lack of an explicit list-all-endpoints or browse operation, though endpoint_lookup partially covers discovery.