ElizaOS Agents▌
by wearesociety
Integrate ElizaOS agents into your IDE environment for seamless development—list, select, and chat with agents right ins
Connects Cursor IDE to ElizaOS agents through a local server, enabling developers to list, select, and chat with agents without leaving their coding environment.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Developers using ElizaOS for AI agent development
- / Teams wanting AI assistance within Cursor IDE
- / Building and testing conversational AI workflows
capabilities
- / List available ElizaOS agents from local server
- / Select specific agents to interact with
- / Send messages and receive responses from agents
- / Check connection status and agent configuration
what it does
Connects Cursor IDE to local ElizaOS agents, allowing developers to list, select, and chat with AI agents directly from their code editor.
about
ElizaOS Agents is a community-built MCP server published by wearesociety that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate ElizaOS agents into your IDE environment for seamless development—list, select, and chat with agents right ins It is categorized under ai ml, developer tools.
how to install
You can install ElizaOS Agents in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
ElizaOS Agents is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme

Society ElizaOS Connector MCP
The Society ElizaOS Connector MCP (Model Context Protocol) allows you to seamlessly integrate your ElizaOS agents with Cursor. This enables you to list available agents, select a specific agent to interact with, and chat directly with your ElizaOS agents from within the Cursor IDE.
This MCP server runs locally on your machine and is managed by Cursor using the stdio transport, meaning Cursor automatically starts and communicates with it.
Features
- List Agents: Retrieve a list of available agents from your ElizaOS instance.
- Select Agent: Choose a specific agent to interact with. The
Room IDwill be automatically set to match theAgent ID. - Chat with Agent: Send messages to the selected ElizaOS agent and receive responses.
- Check Status: Verify the MCP server's connection state and current agent configuration.
Prerequisites
- Node.js and npm (v14 or higher).
- An ElizaOS server instance running and accessible (e.g., locally on
http://localhost:3000). - Cursor IDE with MCP support.
Installation & Usage with Cursor
Quick Setup (Recommended)
The easiest way to use this MCP is directly with Cursor using npx. Cursor will automatically handle running the package.
- Configure Cursor:
Create or open the
.cursor/mcp.jsonfile in your project folder (or the global~/.cursor/mcp.jsonfile) and add:
{
"mcpServers": {
"society-elizaos-mcp-npx": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"ELIZAOS_SERVER_URL": "http://localhost:3000",
"ELIZAOS_USER_ID": "000000000000000000000000000000000000", example ad64a76a-0e09-0899-b8f8-492d6aea4118
"ELIZAOS_WORLD_ID": "000000000000000000000000000000000000", example c930b151-dcfb-41c5-96af-550ffea7023c
"ELIZAOS_AGENT_ID": "000000000000000000000000000000000000", example 85e9fa66-6f8c-0f18-922c-d6c962e21e18
"ELIZAOS_ROOM_ID": "000000000000000000000000000000000000", Need to be equal to the ELIZAOS_AGENT_ID
"ELIZAOS_CONNECTION_TIMEOUT": "120000",
"ELIZAOS_RESPONSE_TIMEOUT": "90000",
"PORT": "3099",
"DEBUG": "true",
"NODE_ENV": "production",
"MCP_DISABLE_PINGS": "true"
}
}
}
-
Replace all placeholder UUIDs with your actual ElizaOS IDs.
-
Restart Cursor to apply the configuration changes.
-
Start using the tools in the Cursor interface - they'll appear as:
get_statuslist_agentschat_with_agentset_agent
Local Development Setup
If you want to run a local development version of the connector, follow these steps:
-
Clone and install dependencies:
git clone https://github.com/your-username/society-elizaos-mcp.git cd society-elizaos-mcp npm install -
Build the package:
npm run build -
Run locally:
# Set required environment variables export ELIZAOS_SERVER_URL="http://localhost:3000" export ELIZAOS_USER_ID="your-elizaos-user-uuid" export ELIZAOS_WORLD_ID="your-elizaos-world-uuid" export ELIZAOS_AGENT_ID="your-initial-agent-uuid" export ELIZAOS_ROOM_ID="your-initial-agent-uuid" # Run the server node dist/index.js -
Or use the convenience script:
# The script sets default environment variables and runs the server ./scripts/mcp_run.sh -
Configure Cursor for local version: If you want Cursor to use your local version instead of the npm package, update your
.cursor/mcp.json:{ "mcpServers": { "society-elizaos-mcp-local": { "command": "node", "args": [ "/path/to/your/society-elizaos-mcp/dist/index.js" ], "env": { "ELIZAOS_SERVER_URL": "http://localhost:3000", "ELIZAOS_USER_ID": "your-elizaos-user-uuid", "ELIZAOS_WORLD_ID": "your-elizaos-world-uuid", "ELIZAOS_AGENT_ID": "your-initial-agent-uuid", "ELIZAOS_ROOM_ID": "your-initial-agent-uuid", "ELIZAOS_CONNECTION_TIMEOUT": "120000", "ELIZAOS_RESPONSE_TIMEOUT": "90000", "PORT": "3069", "DEBUG": "true", "NODE_ENV": "production", "MCP_DISABLE_PINGS": "true" } } } }
Configuration Options
All configuration is done through environment variables, which you set in the env section of your .cursor/mcp.json file:
| Environment Variable | Required | Description |
|---|---|---|
ELIZAOS_SERVER_URL | Yes | URL of your ElizaOS server (e.g., http://localhost:3000) |
ELIZAOS_USER_ID | Yes | Your ElizaOS user UUID |
ELIZAOS_WORLD_ID | Yes | Your ElizaOS world UUID |
ELIZAOS_AGENT_ID | No | Initial agent UUID to connect to (optional but recommended) |
ELIZAOS_ROOM_ID | No | Must match ELIZAOS_AGENT_ID if provided |
ELIZAOS_CONNECTION_TIMEOUT | No | Socket connection timeout in ms (default: 120000) |
ELIZAOS_RESPONSE_TIMEOUT | No | Agent response timeout in ms (default: 90000) |
Security Notice
⚠️ Important: Never include any API keys or secrets in your .cursor/mcp.json file or in any code you publish. The MCP does not require any external API keys to function.
MCP Tool Reference
Once configured, Cursor can communicate with your ElizaOS agents through these four tools:
1. get_status
Gets the current connection status and configuration of the ElizaOS MCP.
Arguments: None required (pass an empty object {} or {"random_string": "any"})
Returns:
{
"connectionState": "connected",
"currentAgent": "agent-uuid",
"currentRoom": "room-uuid",
"serverUrl": "http://localhost:3000",
"userId": "user-uuid",
"worldId": "world-uuid",
"connectionTimeout": 120000,
"responseTimeout": 90000
}
2. list_agents
Lists all available agents from your ElizaOS server.
Arguments: None required (pass an empty object {} or {"random_string": "any"})
Returns:
[
{
"id": "agent-uuid-1",
"name": "Agent Name 1"
},
{
"id": "agent-uuid-2",
"name": "Agent Name 2"
}
]
3. chat_with_agent
Sends a message to the currently selected agent and returns the response.
Arguments:
{
"message": "Your message to the agent goes here"
}
Returns:
{
"messageText": "Your message to the agent goes here",
"senderId": "your-user-id",
"response": {
"senderId": "agent-id",
"senderName": "Agent Name",
"text": "The agent's response text",
"roomId": "room-id",
"createdAt": 1747632281772,
"source": "mcp_client_chat",
"thought": "Optional agent thought process if available",
"actions": ["REPLY"]
}
}
4. set_agent
Switches to a different agent. Note that agent_id and room_id must be identical in ElizaOS.
Arguments:
{
"agent_id": "the-agent-uuid-to-use",
"room_id": "the-agent-uuid-to-use"
}
Returns:
{
"success": true,
"oldConfig": {
"agentId": "previous-agent-uuid",
"roomId": "previous-room-uuid"
},
"newConfig": {
"agentId": "new-agent-uuid",
"roomId": "new-agent-uuid"
}
}
Troubleshooting
Common Issues
-
"Missing required ElizaOS environment variables":
- Ensure
ELIZAOS_USER_ID,ELIZAOS_WORLD_ID, andELIZAOS_SERVER_URLare set in your MCP config.
- Ensure
-
"Failed to connect to ElizaOS for chat":
- Confirm your ElizaOS server is running at the specified URL.
- Verify the agent and room IDs match and are valid.
-
No agent responses:
- Check that the agent is active in your ElizaOS environment.
- Increase
ELIZAOS_RESPONSE_TIMEOUTif your agent takes longer to respond.
-
"For ElizaOS, agent_id and room_id must be identical":
- When using
set_agent, ensure both IDs are the same value.
- When using
License
MIT
This README provides a comprehensive guide for setting up and using the Society ElizaOS Connector MCP with Cursor. For additional assistance, please open an issue on the GitHub repository.
FAQ
- What is the ElizaOS Agents MCP server?
- ElizaOS Agents is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for ElizaOS Agents?
- This profile displays 66 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★66 reviews- ★★★★★Kiara Flores· Dec 24, 2024
ElizaOS Agents is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Camila Chawla· Dec 24, 2024
ElizaOS Agents reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Min Gupta· Dec 20, 2024
ElizaOS Agents has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Aisha Shah· Dec 12, 2024
We wired ElizaOS Agents into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Hiroshi Agarwal· Dec 8, 2024
ElizaOS Agents reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Zara Chen· Nov 27, 2024
ElizaOS Agents has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Nov 15, 2024
Strong directory entry: ElizaOS Agents surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Chinedu Desai· Nov 15, 2024
We wired ElizaOS Agents into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Diego Kapoor· Nov 15, 2024
ElizaOS Agents has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Diego Shah· Nov 11, 2024
ElizaOS Agents reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 66