AI That Can Operate a Real Windows System, Not Just Chat About One
SindByte is a portable local MCP runtime for Windows. Point LM Studio, Roo Code, VS Code add-ons, or custom MCP clients at one local endpoint and let them work with files, desktop automation, timers, reasoning workflows, and credential-aware service routes.
Free for private use. If you want SindByte for business or commercial operation, use the Smart Package Robot license path.
The current config audit shows 237 feature-flag entries across 19 MCP families. Add the two core/runtime routes and the host-callable surface becomes 239 tools. What a connected host actually sees still depends on registration mode, category filters, credentials, and build profile.
Clear Offer
Private users can download SindByte directly. Business and commercial rollouts belong on the Smart Package Robot licensing path, not on the private-use ZIP.
Controlled Publication
Tool visibility is shaped by feature flags, category filters, ask-first states, credentials, and registration mode. Smaller live catalogs are expected behavior, not broken installs.
Standard MCP, Local First
Hosts connect over streamable HTTP JSON-RPC to http://127.0.0.1:5555/mcp. Start locally, publish the surface you need, and expand only when credentials are in place.
How the Runtime Actually Works
LM Studio, Roo Code, Cline-style agents, VS Code MCP add-ons, or custom clients talk to SindByte over one local MCP endpoint.
The default runtime listens on port 5555 and publishes streamable HTTP JSON-RPC at /mcp. Localhost is the default posture.
Full and Short registration, category filters, credentials, and ask-first rules decide which tool routes appear to a given host.
The published surface can drive files, windows, screenshots, timers, reasoning helpers, generated assets, and credential-backed connectors such as trading or cloud image routes.
mcp_config.json the runtime reads. If you change filters, credentials, or registration mode, reload the client because many hosts cache the published schema.
Start and Connect in Minutes
Host Patterns That Fit
LM Studio
Strong fit when you want local inference plus local tool execution on the same PC with no external dependency for core automation.
Roo Code / Cline
Good for repo work, file changes, data cleanup, screenshots, and bounded system actions with ask-first protection.
Custom MCP Clients
Use the standard MCP lifecycle with initialize, tools/list, and tools/call against one local endpoint.
Short Registration Clients
If a host struggles with a wide tool list, publish a tighter surface and inspect it with ToolCatalog.ListCategories or spr_server_assistant.
What Ships With the Runtime
Where SindByte Earns Its Keep
Local Repo and File Operations
Publish a narrow surface for file, text, and data work when you want an AI host to inspect, transform, summarize, or reorganize local project material with less risk.
Desktop and UI Automation
Use screenshots, window control, input simulation, and image routes when the task crosses from text into real Windows UI state.
Scheduled Reviews and Monitoring
Timer workflows make repeated summaries, report generation, and provider-backed checks practical without building a separate scheduler stack.
Credential-aware Connectors
Trading, cloud image, email, and enterprise connectors are published only when keys and filters allow them, so each runtime can stay intentionally small.
Proof Beyond Copy
This site now mixes real runtime screenshots with explainers for host connectivity, registration behavior, and runtime surfaces instead of leaning on generic concept art.
That matters because SindByte is easiest to trust when the endpoint, the catalog logic, and the surrounding operator surfaces are visible at a glance.
Choose Your Next Step
Private-use evaluation starts with the SindByte ZIP. Business and commercial deployment should continue through Smart Package Robot licensing.