Voxta MCP

🚀 Voxta MCP Communication Bridge Provider

A provider that enables Voxta to communicate with Model Context Protocol (MCP) servers, allowing Voxta to leverage external tools and resources through the MCP protocol.

🚀 Quick Start

✨ Prerequisites

• .NET 8.0 SDK
• Python 3.10 or higher
• Git

📦 Installation

Windows

1. Clone the repository:

git clone https://github.com/voxta/voxta-mcp.git
cd voxta-mcp

2. Create a Python virtual environment:

python -m venv venv
.\venv\Scripts\activate
pip install mcp-agent

3. Build and run the project:

dotnet build
dotnet run

Linux

1. Clone the repository:

git clone https://github.com/voxta/voxta-mcp.git
cd voxta-mcp

2. Create a Python virtual environment:

python3 -m venv venv
source venv/bin/activate
pip install mcp-agent

3. Build and run the project:

dotnet build
dotnet run

💻 Usage Examples

Basic Usage

1. Ensure your MCP server is running and can be configured to the specified address.

2. Configure the appsettings.json settings:

{
  "MCPBridge": {
    "PythonExePath": "venv/bin/python",  // Path to the Python executable in the virtual environment
    "MCPClientScriptPath": "mcp_client.py",  // Path to the MCP client script
    "MCPServerAddress": "localhost:50051"  // Your MCP server address
  }
}

3. Run the provider:

dotnet run

4. The provider will perform the following actions:

   • Start the Python MCP client process
   • Connect to your MCP server
   • Register in Voxta
   • Start processing action requests

5. Monitor the console output for:

   • Connection status
   • Action triggers
   • Error messages
   • MCP tool responses

Troubleshooting

Common issues and solutions:

1. "MCPClientScriptPath is not configured"

   • Ensure that appsettings.json exists and has the correct path for mcp_client.py

2. The Python process fails to start

   • Verify that the virtual environment is activated
   • Check the PythonExePath configuration
   • Ensure that mcp-agent is installed in the virtual environment

3. Unable to connect to the MCP server

   • Verify that the server is running
   • Check the MCPServerAddress configuration
   • Ensure that there is no firewall blocking the connection

Configuration

The provider is configured through appsettings.json:

{
  "MCPBridge": {
    "PythonExePath": "venv/bin/python",  // On Linux: "venv/bin/python"
    "MCPClientScriptPath": "mcp_client.py",  // Required: Path to the Python MCP client script
    "MCPServerAddress": "localhost:50051"  // Your MCP server address
  }
}

Usage Instructions

1. The provider will automatically register available MCP tools with Voxta.

2. When Voxta triggers an action, the provider will:

   • Convert the Voxta action into an MCP tool call
   • Send a request to the MCP server via the Python client
   • Receive the response and return it to Voxta

🔧 Technical Details

• The C# code handles Voxta integration and process management.
• The Python script (mcp_client.py) handles MCP protocol communication.
• The two components communicate using JSON messages over standard input/output.

📄 License

[License information is provided here]