MCP Servers

Using Lite Suite's MCP server integrations

MCP Servers

Lite Suite includes four MCP (Model Context Protocol) servers that connect AI agents like Claude to your local tools, files, and workflows.

What Is MCP?

MCP is an open protocol that lets AI assistants use external tools. Instead of the AI being limited to generating text, MCP gives it the ability to read files, search databases, run commands, and interact with applications -- all through a standardized interface.

When you configure an MCP server in Claude Code (or another MCP-compatible client), the AI gains access to the tools that server provides. Lite Suite ships four MCP servers, each serving a different purpose.

The Four MCP Servers

LiteTerminal

LiteTerminal exposes terminal sessions to AI agents for reading, writing, and multi-agent orchestration.

What it provides:

terminal -- a single action-routed tool with multiple operations:
- register -- Bind an agent to a PTY session (creates a discoverable agent registry at ~/.liteterminal/agents/)
- read -- Read another agent's terminal output (~32KB rolling buffer)
- write -- Send text to another agent's terminal (appears as user input)
- submit -- Write text + press Enter
- ctrl -- Send control characters (Ctrl+C, Ctrl+D, etc.)
- list -- List all active PTY sessions
- create / destroy -- Create or destroy terminal sessions
- notify -- Speak a TTS notification aloud

Use case: Multi-agent orchestration. Run multiple Claude Code instances in LiteTerminal, each registered to its own PTY session. Agents can read each other's terminals to see what work is happening, write messages to coordinate, and a coordinator agent can dispatch tasks, relay bug reports, and review code across the fleet. Tested in production with 4 simultaneous agents working on different projects.

LiteMemory

LiteMemory connects your Obsidian vault to AI agents.

What it provides:

vault_read -- Read a specific note by path
vault_write -- Create or update notes
vault_search -- Full-text search across the vault
vault_list -- List notes in a directory
vault_daily -- Access and append to daily notes
vault_recent -- Find recently modified notes
vault_tags -- Search by tags
vault_link -- Follow and discover note links

Use case: Give Claude access to your second brain. It can look up project notes before starting work, record decisions as you make them, and search your knowledge base for relevant context.

LiteMCP

A consolidated MCP server that bundles 16 tool domains into a single process.

Domains included:

Filesystem -- Read, write, list, and search files on your machine
Process -- Launch, monitor, and manage system processes
Clipboard -- Read from and write to the system clipboard
Screen -- Capture screenshots and analyze screen content
Window -- List, focus, resize, and manage application windows
System -- Get system information (CPU, RAM, disk, network)
Notification -- Send desktop notifications
Network -- HTTP requests, port scanning, connectivity checks
Audio -- Audio playback, recording, and device management
Registry -- Windows registry read/write operations
Shell -- Shell command execution and scripting
Git -- Git repository operations and status
Docker -- Container management and orchestration
Database -- SQLite and local database operations
Schedule -- Task scheduling and cron management
Secrets -- Encrypted credential storage and retrieval

Use case: A single server that gives Claude broad access to your local machine. Instead of configuring 16 separate MCP servers, LiteMCP provides all of these capabilities through one connection.

lite_mux

An MCP gateway that multiplexes multiple MCP backends through a single endpoint.

How it works:

Instead of configuring many individual MCP servers in your client, you point your client at lite_mux. It acts as a reverse proxy: it connects to multiple backend MCP servers on your behalf and exposes all their tools through one unified interface.

Key features:

Single connection -- your MCP client only needs one server entry
Backend management -- add, remove, and configure backends from a central config
Tool namespacing -- prevents tool name collisions between backends
Health monitoring -- tracks which backends are online and routes accordingly

Use case: When you run multiple MCP servers (LiteMemory, LiteMCP, and any third-party servers), lite_mux lets you consolidate them into a single endpoint.

Configuring MCP Servers in Claude Code

To use these servers with Claude Code, add them to your Claude Code MCP configuration.

LiteMemory

Add to your Claude Code settings (.claude/settings.json or via the Claude Code CLI):

{
  "mcpServers": {
    "LiteMemory": {
      "command": "node",
      "args": ["C:/LiteSuite/apps/LiteMemory/dist/index.js"],
      "env": {
        "VAULT_PATH": "C:/Users/YourName/Documents/Obsidian Vault"
      }
    }
  }
}

Replace VAULT_PATH with the actual path to your Obsidian vault.

LiteMCP

{
  "mcpServers": {
    "LiteMCP": {
      "command": "C:/LiteSuite/.venv/Scripts/python.exe",
      "args": ["C:/LiteSuite/apps/LiteMCP/server.py"]
    }
  }
}

lite_mux

{
  "mcpServers": {
    "lite_mux": {
      "command": "C:/LiteSuite/.venv/Scripts/python.exe",
      "args": ["C:/LiteSuite/apps/lite_mux/gateway.py"],
      "env": {
        "MCP0NE_CONFIG": "C:/LiteSuite/apps/lite_mux/config.json"
      }
    }
  }
}

When using lite_mux, you typically do not need to add LiteMemory or LiteMCP separately -- configure them as backends in the lite_mux config instead, and access everything through the single gateway.

LiteCLI: CLI Access to Any MCP Server

LiteCLI is not itself an MCP server -- it is an MCP client that gives you CLI and TUI access to any MCP server. Register LiteMemory, LiteMCP, lite_mux, or any third-party MCP server as a backend, and LiteCLI auto-generates CLI commands from the tool schemas.

# Register LiteMemory as a backend
litecli admin add --id litememory --type stdio --prefix mem \
  --command node --args "C:/LiteSuite/apps/LiteMemory/dist/index.js"

# Now use vault tools from the terminal
litecli mem vault-search --query "project architecture"
litecli mem vault-daily --entry "Finished auth refactor"
litecli --json mem vault-list --folder "Projects"

LiteCLI also includes a Skill Compiler that generates standalone CLIs from AI agent skill definitions. See LiteCLI docs for details.

Choosing a Setup

| Setup | When to use | |-------|------------| | LiteTerminal | You want AI agents to read/write terminal sessions or orchestrate multiple agents | | LiteMemory only | You just want Obsidian vault access for Claude | | LiteMCP only | You want broad local machine access (files, processes, clipboard, etc.) | | LiteMemory + LiteMCP | You want both vault access and machine access as separate servers | | lite_mux | You run 3+ MCP servers and want to consolidate them into one connection | | LiteCLI | You want to call any MCP server's tools from the terminal, scripts, or CI |

For most users, starting with LiteMemory + LiteMCP configured individually is the simplest approach. Add LiteCLI when you want terminal access to those same tools. Move to lite_mux when your server count grows.