Code and integrations
When no ready-made integration exists, you write a function. Every function exported from a TypeScript workspace becomes a tool for agents, with its real arguments.
If a system has an interface, a TypeScript function turns it into a tool.
Every workspace has a git repository with commit history.
Secrets are declared in the node and read at runtime.
The code nodes
| Node | Where it runs | What it offers the agent | Persistence |
|---|---|---|---|
| Connector | Cloud container, Node.js 22 | The functions in tools.ts as typed tools | One git repository per node |
| Sandbox | Cloud container | Shell and files: exec, readFile, writeFile, editFile, listFiles | Ephemeral per conversation, or shared and persistent |
| Machine at your site | Customer's Linux server or Windows PC | The machine's shell and files | The machine's file system |
| Connector at your site | Node.js on the customer's machine | TypeScript functions close to local systems | Platform git repository |
The two "at your site" nodes are described in On-premise and legacy systems.
The connector
- Your functions. The functions as tools, which you give to the right agents.
- Edit this workspace. The development tools (run commands, read and write files, commit) for a developer agent. You can also work by hand from the Code section.
- Tools the code can call. The code can in turn call the tools of other nodes.
- Start a conversation. The code can converse with an agent.
- Template. You can start from an example or from a Microsoft 365 template with mail, calendar, OneDrive/SharePoint, Teams and people.
Third-party MCP servers
TeraBrain NX brings the tools of third-party MCP servers into the project as if they were native tools.
| Remote MCP server | Hosted MCP server | |
|---|---|---|
| For servers | Published on the web (GitHub, Linear, Notion, another TeraBrain NX project) | Distributed as a command (npx, uvx) |
| Where it runs | At the provider | In a dedicated container on the platform |
| Credentials | None, bearer token or OAuth | Environment variables: values or organization secrets |
| Per member | Yes | No: one process for everyone |
There is also a ready-made variant with a remotely driven browser (open page, click, type, read, screenshot), with no keys or accounts.
Related pages
On-premise and legacy systems
Making agents work with systems that have no public address: internal ERPs, local databases, shared folders.
Data and knowledge
MySQL databases, file storage and skill library: the persistent state of agents and code.
Building with external assistants
Using Claude, Codex or other assistants to build and develop TeraBrain NX projects, with the person's own rights.
Security
Roles, groups, credentials, enterprise sign-in and least privilege: how to protect an agent system.
Have an agent to take to production?Let’s talk.
We show you TeraBrain NX on your case: systems to connect, access and controls.