runtime · today · How do I use MCP locally without sending private context to the cloud?
MCP on the computer you already own.
Local MCP on TARX_OS is the default for private context: Spaces, files, Memory, tool calls that need local approval. Remote MCP is public-safe tools only. Status: pilot-ready. Compatible clients discover approved TARX tools through a boundary. Private context stays on this computer unless you approve a route.
Compatible clients discover approved TARX tools through a boundary. Private context stays on this computer unless you approve a route.
TARX works privately on your computer. Connections stay off until you allow them.
Product proof. Not atmosphere. TARX_OS on silicon you own.
HOW TARX WORKS
How TARX works with MCP
MCP is a boundary, not a personality. Local: run on the same computer as TARX_OS. Remote: public-safe tools only. The mistake is stuffing private files into a remote server and calling it local-first.
Skills package reusable behavior for TARX-compatible tools and clients. Status skills are available now. Memory, Spaces, and Delegation are pilot-ready. They are gated. A Skill cannot browse the web silently.
Developers Join on Apple silicon. T-1 is the bench Supercomputer to prove I/O before T-4, T-7, or T-70. Same approval. Same Evidence.
THE STACK
Join the Supercomputer. Or own Private Hardware.
TARX_OS on computers you already own. Supercomputer hardware when the site needs dedicated NVIDIA.
Placeholder
TARX_OS · Conversation into the runtime · free software
Spaces and Memory stay on this computer. Remote MCP does not get them.
A client that should only see approved tools
Discovery through the boundary. Not an invisible plugin bag.
A bench before a sealed box
T-1 Orin 64GB to shape the deployment. Not a production enclosure.
KEY FEATURES
Dialed to this question.
Local MCPnpx @tarx/mcp on the same computer as TARX_OS
Remote MCPmcp.tarx.com · public-safe tools only
StatusPilot-ready
BenchT-1 · Orin 64GB · from $3,499
DeskT-4 when the experiment becomes a team box
HOW TO START
Four steps. Same contract.
01
Run TARX_OS locally
Join on Apple silicon. First-run stays local.
02
Use local MCP for private context
Do not send Spaces to a remote server.
03
Keep remote MCP public-safe
The boundary is the product.
04
Prove I/O on T-1 if needed
Then get a T-4, T-7, or T-70.
FAQ
Questions this page owns.
Local or remote MCP?
Local: npx @tarx/mcp on the same computer as TARX_OS. Remote: mcp.tarx.com for public-safe tools only.
Can a Skill browse the web silently?
No. Web lookup is labeled, Evidence-backed, and off until you opt in.
Is T-1 a finished Supercomputer?
No. T-1 is the bench kit to shape T-4, T-7, or T-70.
Is MCP the product?
No. TARX_OS is the runtime. MCP is how compatible clients meet approved tools.
TWO EQUAL PATHS
JOIN THE SUPERCOMPUTER. OR OWN PRIVATE HARDWARE.
Join the Supercomputer. Or own Private Hardware.
JOIN · TARX_OS
Join the Supercomputer
Give TARX superpowers.
TARX works privately on your computer. Connect to the Supercomputer when you want TARX to research the web, use more skills, and take on bigger jobs with deeper models. Supercomputer connection is in beta, and capacity is being qualified.
