Yuga Planner MCP Server

Yuga planner mcp server connects Yuga Planner to AI assistants that speak the Model Context Protocol. Yuga Planner is a neuro-symbolic system prototype: it provides an agent-powered team scheduling and task allocation platform built on Gradio.

What Yuga Planner does

Yuga Planner is a neuro-symbolic system prototype: it provides an agent-powered team scheduling and task allocation platform built on Gradio.

Tools it exposes

Once connected, the assistant can call this tool directly:

• Installation — 1. Clone the repository: bash git clone https://github.com/blackopsrepl/yuga-planner.git cd yuga-planner 2. Create a virtual environment: bash make

Installing the yuga planner mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Requirements

• Python 3.10 - Java 17+ - Docker (optional, for containerized deployment) - Nebius API credentials (for LLM-powered features)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Yuga Planner sits in that group, and the shape of its toolset — Installation — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by blackopsrepl, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the yuga planner mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.