LLM Responses MCP Server
Used for running the server with commands like 'bun install', 'bun run build', and 'bun run dev'
Provides containerization and simplified deployment to EC2 or other server environments with included Docker configuration
Used for cloning the repository during deployment to EC2
Used for type-safe implementation of the MCP server, with build step to compile TypeScript code
Mentioned as a potential OS for EC2 deployment alongside Amazon Linux 2
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., "@LLM Responses MCP Serverget responses for 'What are the ethical implications of AI?'"
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.
LLM Responses MCP Server
A Model Context Protocol (MCP) server that allows multiple AI agents to share and read each other's responses to the same prompt.
Overview
This project implements an MCP server with two main tool calls:
submit-response: Allows an LLM to submit its response to a promptget-responses: Allows an LLM to retrieve all responses from other LLMs for a specific prompt
This enables a scenario where multiple AI agents can be asked the same question by a user, and then using these tools, the agents can read and reflect on what other LLMs said to the same question.
Related MCP server: brainstorm-mcp
Installation
# Install dependencies
bun installDevelopment
# Build the TypeScript code
bun run build
# Start the server in development mode
bun run devTesting with MCP Inspector
The project includes support for the MCP Inspector, which is a tool for testing and debugging MCP servers.
# Run the server with MCP Inspector
bun run inspectThe inspect script uses npx to run the MCP Inspector, which will launch a web interface in your browser for interacting with your MCP server.
This will allow you to:
Explore available tools and resources
Test tool calls with different parameters
View the server's responses
Debug your MCP server implementation
Usage
The server exposes two endpoints:
/sse- Server-Sent Events endpoint for MCP clients to connect/messages- HTTP endpoint for MCP clients to send messages
MCP Tools
submit-response
Submit an LLM's response to a prompt:
// Example tool call
const result = await client.callTool({
name: 'submit-response',
arguments: {
llmId: 'claude-3-opus',
prompt: 'What is the meaning of life?',
response: 'The meaning of life is...'
}
});get-responses
Retrieve all LLM responses, optionally filtered by prompt:
// Example tool call
const result = await client.callTool({
name: 'get-responses',
arguments: {
prompt: 'What is the meaning of life?' // Optional
}
});License
MIT
Deployment to EC2
This project includes Docker configuration for easy deployment to EC2 or any other server environment.
Prerequisites
An EC2 instance running Amazon Linux 2 or Ubuntu
Security group configured to allow inbound traffic on port 62886
SSH access to the instance
Deployment Steps
Clone the repository to your EC2 instance:
git clone <your-repository-url> cd <repository-directory>Make the deployment script executable:
chmod +x deploy.shRun the deployment script:
./deploy.sh
The script will:
Install Docker and Docker Compose if they're not already installed
Build the Docker image
Start the container in detached mode
Display the public URL where your MCP server is accessible
Manual Deployment
If you prefer to deploy manually:
Build the Docker image:
docker-compose buildStart the container:
docker-compose up -dVerify the container is running:
docker-compose ps
Accessing the Server
Once deployed, your MCP server will be accessible at:
http://<ec2-public-ip>:62886/sse- SSE endpointhttp://<ec2-public-ip>:62886/messages- Messages endpoint
Make sure port 62886 is open in your EC2 security group!
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceA structured tool that enables multiple AI agents to simulate reflective debate, where LLMs critique and refine each other's ideas to produce higher-quality solutions.Last updated1
- AlicenseBqualityCmaintenanceEnables multi-round brainstorming debates between multiple AI models like GPT, DeepSeek, and Ollama to produce synthesized final outputs. Users can orchestrate parallel model interactions where AI agents critique and refine each other's ideas to reach a consolidated conclusion.Last updated38367MIT
- Alicense-qualityDmaintenanceThe simplest way to bridge and collaborate across AI Agent sessions like Claude Code, Codex, Gemini, or Cursor. It allows your agents to combine their strengths to solve your most difficult tasks without leaving their current context.Last updated4362MIT
- AlicenseAqualityAmaintenanceEnables Claude to chat with various AI models and obtain multi-model consensus for complex decisions.Last updated31,0772MIT
Related MCP Connectors
Collective memory for AI agents. One agent solves a bug — every agent gets the fix instantly.
A second opinion for AI agents: one prompt across several live Gonka models + roles, one call.
Shared knowledge base for AI agents. Semantic search across agents, no setup required — just a URL.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kstrikis/ephor-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server