Enables the agent to connect to and orchestrate tasks through an Airbnb MCP server, allowing for automated interaction with the platform.
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., "@MCP Agent & Server EcosystemSearch for the best-rated Airbnbs in Austin for next month and summarize the reviews."
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.
π MCP Agent & Server Ecosystem
A state-of-the-art demonstration of the Model Context Protocol (MCP), featuring autonomous agents, browser automation, and multi-server orchestration. This ecosystem leverage's Groq's high-performance inference to provide a seamless agentic experience.
ποΈ Architecture Overview
The system operates in two modes: an interactive CLI Agent and a standalone MCP Server. Both modes utilize the same core logic but differ in their entry points and orchestration.
1. CLI Agent Flow (app.py)
In this mode, the user interacts directly with a terminal-based agent.
graph TD
subgraph "MCP Host Region (Application Space)"
User["π€ User"] -->|Inputs| App["π₯οΈ app.py / CLI"]
App -->|Initializes| Agent["π€ MCPAgent"]
Agent -->|Reasons with| LLM["π§ Groq LLM"]
Agent -->|Instantiates| Client["π MCP Client"]
end
subgraph "Registry Region"
Client -.->|Reads Registry Config| Config["π browser_mcp.json"]
end
subgraph "MCP Server Region (Child Processes)"
Client -->|Connects To| PW["π Playwright"]
Client -->|Connects To| AB["π Airbnb"]
Client -->|Connects To| GA["βοΈ server.py (FastMCP)"]
end2. Prompting/Server Flow (server.py)
In this mode, the project acts as an MCP server itself, exposing a run_task tool to external clients.
graph TD
subgraph "External Region"
Ext["π External MCP Client"] -->|Calls 'run_task'| GA["βοΈ server.py (FastMCP)"]
end
subgraph "MCP Host Region"
GA -->|Initializes| Agent["π€ MCPAgent"]
Agent -->|Instantiates| Client["π MCP Client"]
end
subgraph "Registry Region"
Client -.->|Reads Config| Config["π browser_mcp.json"]
end
subgraph "Secondary MCP Server Region"
Client -->|Delegates To| PW["π Playwright"]
Client -->|Delegates To| AB["π Airbnb"]
end⨠Key Features
β‘ High-Performance Inference: Powered by Groq's
llama-3.3-70b-versatilefor near-instantaneous reasoning.π Autonomous Browser Control: Deep integration with Playwright for navigating and interacting with the web.
π Flexible Server Protocol: Connects to any standard MCP server for extensible tool capabilities.
π State-Aware Memory: (In
app.py) Maintains conversation state to handle complex, iterative requests.π οΈ Custom Server Extension: Includes its own
FastMCPserver for wrapping agentic workflows as reusable tools.
π Project Structure
Component | Responsibility |
| The flagship CLI chat interface and agent controller. |
| A |
| The core registry for all connected MCP services. |
| Project dependencies managed via Python's |
| Secure storage for sensitive API keys. |
π οΈ Getting Started
1. Environment Setup
Ensure you have uv installed and a valid Groq API key.
# Clone the environment variables
echo "GROQ_API_KEY=your_key_here" > .env2. Launch the Ecosystem
You can interact with the agent directly or run the custom server.
Start the Interactive Agent:
python app.pyExpose the Custom MCP Server:
python server.pyπ Implementation Notes
The ecosystem is built on the mcp_use library, bridging LangChain components with the Model Context Protocol. The MCPAgent is configured with safety rails like max_steps to prevent infinite loops during autonomous execution.
Note: The previous mcp.json was detected as missing or redundant; all core configuration is now consolidated in browser_mcp.json.
Made with β€οΈ for the MCP Community
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.