MCP (Model Context Protocol) Frontend

by shaharia-lab

MCP Client 13 stars
  • other

Frontend for MCP (Model Context Protocol) Kit for Go - A Complete MCP solutions for ready to use

About

What is MCP (Model Context Protocol) Frontend?

MCP Frontend is a single-page application that provides a real-time chat interface for interacting with large language models through tool-based capabilities. It is part of the MCP Kit ecosystem and runs in modern browsers, built with React, TypeScript, Vite, and Tailwind CSS.

How to use MCP (Model Context Protocol) Frontend?

Install by cloning the repository and running npm install, or use the official Docker image from ghcr.io/shaharia-lab/mcp-frontend. Set the environment variable VITE_MCP_BACKEND_API_ENDPOINT to the MCP backend server URL, then start the development server with npm run dev or deploy the production build created with npm run build.

Key features of MCP (Model Context Protocol) Frontend

- Single Page Application architecture
- Real-time chat interface with large language models
- Tool-based interaction capabilities
- Integration with MCP backend server
- Modern, responsive UI with React and TypeScript

Use cases of MCP (Model Context Protocol) Frontend

- Interacting with LLMs through a web-based chat interface
- Augmenting LLM conversations with tool-based capabilities from MCP servers
- Developing and testing MCP-enabled applications in a browser environment
- Prototyping LLM interactions with a real-time frontend

FAQ from MCP (Model Context Protocol) Frontend

What is MCP Frontend and how does it differ from alternatives?

MCP Frontend is a user interface layer for the MCP Kit, providing a chat interface with tool-based interactions for large language models. It is not yet production-ready and is under active development.

Which platforms and models does it support?

It runs on any modern web browser as a single-page application. The actual LLM models used depend on the MCP backend server; the frontend communicates with that server via the configured API endpoint.

How do I connect MCP Frontend to an MCP server?

Set the environment variable VITE_MCP_BACKEND_API_ENDPOINT to the base URL of your MCP backend server before starting the application. For Docker, use the -e flag to pass this variable.

What are the licensing and pricing terms?

MCP Frontend is open-source under the MIT License. There is no pricing information in the README; it is free to use under that license.

What are the known limitations or current status?

The project is under active development and not recommended for production use. Known work in progress includes enhanced error handling, improved performance, additional tool integrations, and a comprehensive testing suite.

Details

Author
shaharia-lab
GitHub stars
13
Category
other
Repository
shaharia-lab/mcp-frontend

MCP (Model Context Protocol) Frontend

License: MIT

A frontend application for the Model Context Protocol (MCP) Kit that enables enhanced interactions with Large Language Models through tool-based capabilities.

This repository is part of mcp-kit and serves as the user interface layer built with modern web technologies.

🚀 Features

- Single Page Application architecture
- Real-time chat interface with LLMs
- Tool-based interaction capabilities
- Integration with MCP backend server
- Modern, responsive UI built with React and TypeScript

🎥 Demo

Experience MCP Kit in action - chat with LLMs while leveraging additional capabilities provided by the MCP server:

<video src="https://github.com/user-attachments/assets/bb650e68-825c-4d5e-a032-1ea757bbb930" controls title="MCP Kit in action"></video>

🛠️ Prerequisites

- Node.js 20.x
- NPM 7.x

📦 Installation

Standard Installation

1. Clone the repository:

git clone https://github.com/shaharia-lab/mcp-frontend.git
cd mcp-frontend

[Rest of standard installation steps...]

🐳 Docker Installation

You can run MCP Frontend using our official Docker image:

docker pull ghcr.io/shaharia-lab/mcp-frontend:<version>

Replace <version> with the specific version you want to use (e.g., latest, 1.0.0).

Running with Docker

docker run \
-p 3000:3000 \
-e VITE_MCP_BACKEND_API_ENDPOINT=http://localhost:8081 \
ghcr.io/shaharia-lab/mcp-frontend:<version>

Environment Variables

The following environment variables are required to run MCP Frontend:

| env_key | Default | Required | Description |
|---------------------------------|---------|----------|---------------------------------------|
| VITE_MCP_BACKEND_API_ENDPOINT | - | Yes | The base URL for the MCP backend API. |

Simply copy the .env.example file to .env and update the values as needed to run the application locally.
And for Docker, you can pass the environment variables using the -e flag.

🚀 Usage

Development

Run the development server:

npm run dev

Production

Build for production:

npm run build

For detailed configuration options, refer to the Vite documentation.

🏗️ Architecture

MCP Frontend is built with:
- Vite - Build tool and development server
- React - UI framework
- TypeScript - Type-safe JavaScript
- Tailwind CSS - Utility-first CSS framework

🤝 Contributing

We welcome contributions! Here's how you can help:

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

Please ensure your PRs follow our coding standards and include appropriate tests.

🔍 Related Projects

- MCP-Kit Backend - The main backend server
- Documentation - Full project documentation

⚠️ Current Status

This project is under active development. While functional, it's not yet recommended for production use. We're working on:
- Enhanced error handling
- Improved performance
- Additional tool integrations
- Comprehensive testing suite

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

🤔 Support

- 📧 Email: hello@shaharialab.com
- 🐛 Issue Tracker
- 💬 Discord invite: Community Chat

🙏 Acknowledgments

- The MCP Kit community
- All our contributors and supporters