The Twosplit MCP Server leverages multiple Claude AI instances to generate optimized responses:
Sends the same prompt to two separate instances of a specified Claude model
Uses a third instance to analyze and either select the best response or combine elements from both
Returns the final optimized response along with the original responses and source attribution
Supports multiple Claude models including claude-3-opus-latest, claude-3-5-sonnet-latest, claude-3-5-haiku-latest, and claude-3-haiku-20240307
Requires Anthropic API key configuration
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Twosplit MCP Server write a product description for a smart coffee mug"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that leverages multiple Claude instances to provide enhanced responses. It sends the same prompt to two separate instances of Claude and uses a third instance to combine or select the best elements from both responses.
Supports multiple Claude models:
claude-3-opus-latest
claude-3-5-sonnet-latest
claude-3-5-haiku-latest
claude-3-haiku-20240307
Gets single, direct responses from each AI
Shows original responses and source attribution
Returns optimized final response
Related MCP server: prompte-mcp
Clone the repository
Install dependencies:
npm installBuild the server:
npm run buildThe server requires an Anthropic API key to function. Set it as an environment variable:
export ANTHROPIC_API_KEY=your-api-key-hereThe server provides a single tool called twosplit with the following parameters:
prompt (required): The prompt to send to Claude
model (required): The Claude model to use (must be one of the supported models listed above)
Example tool usage in Claude:
<use_mcp_tool>
<server_name>twosplit</server_name>
<tool_name>twosplit</tool_name>
<arguments>
{
"prompt": "Write a short story about a robot learning to paint",
"model": "claude-3-5-sonnet-latest"
}
</arguments>
</use_mcp_tool>The response will include:
The final optimized response
Original responses from both AIs
Source attribution showing which parts came from which AI
The server sends the same prompt to two separate instances of the specified Claude model, requesting a single direct response
A third instance analyzes both responses and either:
Selects the single best response if one is clearly superior
Creates a new response that combines the best elements from both responses
The final response, original responses, and source attribution are all included in the output
To run the server in watch mode during development:
npm run watchTo inspect the server's capabilities:
npm run inspectorGet multiple AI perspectives and combine them into the best response
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | The Claude model to use (claude-3-opus-latest, claude-3-5-sonnet-latest, claude-3-5-haiku-latest, claude-3-haiku-20240307) | |
| prompt | Yes | The prompt to send to the AI |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions getting 'multiple AI perspectives' and combining them, but doesn't specify how many perspectives, what 'combine' entails (e.g., voting, averaging, synthesis), latency, rate limits, or error handling. For a tool that interacts with AI models, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence: 'Get multiple AI perspectives and combine them into the best response.' It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity. Every part of the sentence contributes to understanding the tool's function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (involving multiple AI calls and combination logic), lack of annotations, and no output schema, the description is insufficient. It doesn't explain the output format, error conditions, or behavioral details like how perspectives are generated or combined. For a tool with no structured support, the description should provide more context to be complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with clear documentation for both parameters ('model' and 'prompt'). The description doesn't add any meaning beyond what the schema provides—it doesn't explain parameter interactions or usage nuances. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get multiple AI perspectives and combine them into the best response.' It specifies the action ('get' and 'combine') and the resource ('AI perspectives'), making it easy to understand what the tool does. However, since there are no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or specific contexts. It simply states what the tool does without indicating scenarios where it's most appropriate or any limitations. This lack of usage context leaves the agent without direction on optimal application.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0twosplitWith only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as getting multiple AI perspectives and combining them, which is distinct and unambiguous in this single-tool context.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'twosplit' follows a single pattern with no deviations or mixing of conventions to evaluate.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a server named 'Twosplit MCP Server' that aims to provide multiple AI perspectives, one tool feels thin and under-scoped, potentially leaving gaps in operations like configuration or result refinement.
The tool surface is severely incomplete for the implied domain of handling AI perspectives. While the 'twosplit' tool covers the core action, there are obvious gaps such as no tools for managing perspectives, adjusting combination parameters, or retrieving historical results, which could lead to agent failures in more complex workflows.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
MCP server giving Claude AI access to 22+ NYC public-record databases for real estate due diligence
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LazerThings/twosplit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
