AI Models for Download
Download PowerBASIC- and SPR-focused GGUF models for local runtimes. Compare quantizations and choose the file that fits your RAM, VRAM, and quality target.
Browse Models
Deep technology, ready for productive use
SindByte turns MCP into a real Windows workspace
Local AI hosts can reason deeply. SindByte enables them to act under control through a local MCP endpoint, real operator interfaces, and a runtime whose visible catalog is deliberately configurable.
Free for private use. For business or commercial use, the right path is the Smart Package Robot license.
Port 5555
localhost by default
239 host-callable tools
19 MCP families + core
Short + Full registration
LM Studio / Roo / Codex / VS Code
Dialog-LAB / LMChat
Filters + credentials shape the catalog
A real screenshot from the current build. The page demonstrates the runtime with genuine interfaces instead of fictional visuals.
Product System
Three areas: Compiler Workshop, AI Workshop, and Services
1. Compiler Workshop
PBXB64 V14 is the primary download product. Scharffbasic V1 Beta adds a mostly PowerBASIC-compatible 32-bit alternative; PBXC64, PBXA, and CompilerX remain the additional development and preview lines.
Open Compiler Workshop
2. AI Workshop
SindByte MCP Server is the local runtime. WorkJinn handles project execution. PlanJinn adds a planning workspace. This area brings the AI tools together.
MCP Server WorkJinn PlanJinn coming soon
3. Services
Practical support for businesses: AI revenue audits, automation sprints, team training, an AI freelancer/instructor, and custom development for real-world processes.
Explore Services AI Revenue Audit AI InstructorMore from SindByte
Models and browser games
These additional offers complement our three main areas. They have their own collections, so new models and several games can be added without making the home page crowded.
SindByte Web Games
A growing collection of games that run directly in the browser. Each title will receive its own launch card, description, controls, and version information.
Open Game CollectionEcosystem Overview
Compiler Workshop, AI Workshop, and Services under one brand
Compiler Workshop, AI Workshop, and Services share the same local-first philosophy: native Windows tools under operator control.
Positioning for private users and business teams
A clear offering
Private users download SindByte directly. Business rollouts, teams, and commercial use follow the Smart Package Robot licensing path.
Publish the catalog deliberately
The visible MCP catalog can start small and grow later. Registration, category filters, and credentials provide deliberate control.
Local first
The default is 127.0.0.1:5555. Cloud, Office, and trading routes remain optional and become relevant only with real credentials.
MCP-capable hosts
LM Studio, Roo Code, Codex workflows, and VS Code add-ons can use the same runtime without tying the product to a single chat interface.
Architecture and runtime in four clear layers
1. Host
An MCP-capable client sends requests to the local endpoint. The product remains host-agnostic.
2. Endpoint
The default endpoint is http://127.0.0.1:5555/mcp. This keeps the runtime local and technically transparent.
3. Registration
Short or Full registration, plus category filters and feature flags. As a result, not every host sees the same set of tools.
4. Execution
Files, windows, timers, image workflows, and credential-dependent families come together in a controlled Windows runtime.
The runtime is not inferred behind the scenes. It is actively shaped in the Config Editor through port, registration, filters, providers, and features.
Launch and connection examples
Start on Windows
cd "<extracted-folder>" .\SindByte 01.exe
The local client endpoint is then http://127.0.0.1:5555/mcp.
Host configuration
"mcpServers": {
"sindbyte": {
"type": "streamable-http",
"url": "http://127.0.0.1:5555/mcp"
}
}
A safe first step
ToolCatalog.ListCategories ToolCatalog.ListTools spr_server_assistant
This lets you inspect the currently published runtime first instead of assuming the entire default configuration is exposed.
Suitable host patterns
LM Studio
Ideal when local inference and local tool execution should run on the same PC without external dependencies for core automation.
Roo Code / Cline
Suitable for repository work, file changes, data cleanup, screenshots, and bounded system actions with ask-first protection.
Custom MCP clients
Internal tools can use the same streamable HTTP endpoint and limit the visible catalog through the runtime configuration.
Clients using Short Registration
A compact ToolCatalog entry point suits hosts that should not load hundreds of direct tool schemas at once.
Visual guides to connection and runtime behavior
One endpoint for multiple host types
The runtime remains MCP-centered rather than tied to a single chat client. This helps with adoption, testing, and internal standardization.
Short and Full at a glance
The diagram shows the difference between broad direct publication and a more compact ToolCatalog-oriented approach.
Product surfaces, not just an endpoint
The runtime includes server shell, configuration, chat, and timer surfaces. That is what makes SindByte tangible as a product.
What ships with the runtime
Main server shell
Starts the local endpoint, displays status and logs, and provides the operational entry point to the product surfaces.
Config Editor
Controls the port, local-only behavior, registration, categories, feature flags, provider access, timeouts, and logging.
Timer + IQ
Schedules recurring tasks and connects them with the runtime's reasoning and execution helpers.
Where SindByte delivers practical value
Local repository and file operations
Inspect files, organize content, and perform bounded changes directly on the Windows workstation.
Desktop and UI automation
Windows, screenshots, and controlled interaction flows with ask-first rules instead of uncontrolled remote operation.
Scheduled checks and monitoring
Timers connect recurring reviews, observations, and local execution through traceable workflows.
Credential-aware connectors
Cloud images, trading, and other services become active only when real credentials and the appropriate categories are enabled.
Proof: real product screenshots
Server Shell
The technical anchor for local startup, status, and the MCP endpoint.
Config Editor
This is where runtime policy determines which families and credentials actually apply.
Timer + IQ
Recurring executions show that SindByte is built for ongoing workflows, not just one-off prompts.
Verifiable facts instead of marketing claims
Port and host
Default ist 127.0.0.1:5555. This makes the local host a clear, testable setup characteristic.
Registration modes
Short and Full determine whether many routes are published directly or through a more compact ToolCatalog approach.
Filters and credentials
The visible catalog intentionally varies according to category filters, security flags, and configured credentials.
Product surfaces
Config, Dialog-LAB, LMChat, Timer, and Trading are real product screens, not retrospective concept graphics.
Next step: start locally, then expand deliberately
Private users start with the download. Business customers continue through Smart Package Robot for properly licensed production use.
Download free for private use Business License MCP Architecture