Where Can You Connect SindByte?

SindByte is a local Windows MCP endpoint, not a single chat client. You can plug it into local-model desktops, coding agents, editor extensions, and custom MCP-compatible apps.

LM Studio

Roo Code / Cline

Codex-style agent flows

VS Code MCP add-ons

Custom MCP clients

localhost default

Short / Full registration

Endpoint: http://127.0.0.1:5555/mcp
Transport: streamable HTTP JSON-RPC
Practical note: the visible tool set depends on registration filters, credentials, and whether the build publishes compact or full registrations.

Connection Checklist

1. Start SindByte 01.exe on the Windows machine that should expose tools.

2. Confirm the MCP endpoint is reachable at 127.0.0.1:5555/mcp.

3. Open the Registration Filters dialog if you want a smaller or safer published tool surface.

4. Reload the MCP client after config or schema changes because many clients cache tool schemas.

5. Start with spr_server_assistant or ToolCatalog.ListCategories to inspect the current runtime surface.

Live Runtime Surfaces

Main MCP server shell with endpoint and runtime status

Config, registration, filter, and credential surface

Connection-Relevant Live Forms

Provider + Models

Choose the provider stack and model routing before IQ or timer jobs are handed to a host workflow.

Registration Filters

Shrink the published surface when a client should only see a safer or narrower tool subset.

Timer + IQ

Real scheduled prompt surface for repeatable analysis, monitoring, and follow-up runs.

Trading Console

Credential-aware trading forms stay visible proof that the endpoint can serve more than file and shell routes.

First Technical Validation

PS C:\SindByte> .\SindByte 01.exe Endpoint: http://127.0.0.1:5555/mcp Transport: streamable HTTP JSON-RPC Default posture: localhost only Config: mcp_config.json

What to check: if the endpoint is local, the shell is visible, and your host can reach /mcp, the runtime is ready. If a host still shows too few tools, the next suspects are registration mode, filters, credentials, and host cache.

MCP Lifecycle in 3 Calls

1. initialize establishes the session and capabilities.

2. tools/list shows the currently published catalog.

3. tools/call executes one route inside the local runtime.

initialize tools/list tools/call

FTPTools Skill: Remote Web File Workflows

Use this sequence when you want SindByte to read/edit remote web files (such as this site’s /spr or /aispr content).

1. Verify active FTP profile:

tools.call { "name": "FTPTools::ListProfiles", "arguments": {} }

2. List remote directory entries:

tools.call { "name": "FTPTools::List", "arguments": { "profile": "1", "path": "/spr/en" } }

3. Download, edit, and upload a page:

tools.call { "name": "FTPTools::DownloadFile", "arguments": { "profile": "1", "remote_path": "/spr/en/download.html", "local_path": "C:\\Temp\\spr_download.html" } } tools.call { "name": "FTPTools::UploadFile", "arguments": { "profile": "1", "local_path": "C:\\Temp\\spr_download.html", "remote_path": "/spr/en/download.html" } }

If multiple profiles exist, pin the site-specific one by name with FTPTools::SelectProfile and use the same call shape above.

Supported Client Patterns

Client	Best fit	What it gets from SindByte	Operational note
LM Studio	Local private workflows and model experiments	Full local MCP bridge, Dialog-LAB companion flows, desktop and file automation	Strong fit when you want local inference plus local tool execution on the same PC
Roo Code / Cline	Coding, repo maintenance, ops workflows	FileTools, DataTools, SystemTools, CUTools, IQTools, image tools, timers	Reload after schema changes; use ask-first flags for destructive tools
Codex / agent CLI	Structured agent runs and multi-step automation	Consistent MCP endpoint for tool calling, image generation, file and system actions	Best when the agent already manages plans, diffs, and verification loops
Custom MCP clients	Internal apps, dashboards, orchestration layers	Standard MCP JSON-RPC `initialize`, `tools/list`, `tools/call`	Client-visible tool count will vary with credentials and registration mode

LM Studio Example

Use the local MCP URL and reload LM Studio after changes.

"mcpServers": { "sindbyte-mcp": { "url": "http://127.0.0.1:5555/mcp" } }

Roo Code / Streamable HTTP Example

Use streamable HTTP in clients that differentiate transport types.

"mcpServers": { "sindbyte-mcp": { "type": "streamable-http", "url": "http://127.0.0.1:5555/mcp" } }

What Changes by Client?

Published tools

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, but any given client still sees only the currently registered subset.

Credential-gated routes

Families such as M365, Teams, Gmail, cloud image flows, and trading venues require valid keys before they become practically usable.

Safety posture

Use ask-first flags and essential-only publication when you want a coding agent or office assistant to stay inside a narrow tool perimeter.

Next Step

After the client is connected, move to the manual for provider selection, registration filtering, timers, image tools, Dialog-LAB, and Trading Hub.

Open Manual