Context API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT_API_KEY | Yes | Your Context API key | |
| CONTEXT_API_URL | No | API base URL (optional) | https://dev.doppelgangers.ai:3003 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_relevant_postsA | Semantic search of contextualized post renderings of a certain Twitter/X user, based on a natural language query. Twitter/X username and platform (= X) must be provided. Use this tool to find specific posts, relevant to the query. |
| get_all_user_postsA | Retrieve all contextualized post renderings of a specific Twitter/X user. This tool is useful when you need to analyse posts for insights, trends and topics over all posts. For instance, to answer queries such as:
|
| check_creditsA | Check your Context API credit balance and usage statistics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: credits check, full post retrieval, and semantic search. No ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (check_credits, get_all_user_posts, search_relevant_posts).
Three tools is slightly minimal but well-scoped for the server's focused purpose of analyzing Twitter/X user posts. The count is not excessive or too thin.
Covers the core operations for the domain: account status, exhaustive post retrieval, and semantic search. Minor gaps like single post or user profile are not critical for the intended analysis tasks.