@nativeharness/connectors

How an agent reaches GitHub or your API without the credential ever entering the sandbox.

npm install @nativeharness/connectors

On hydrate, an nh command is written into the guest and given a token minted for that one command. Code inside runs:

nh list                              # what is connected
nh docs github create_issue          # a tool's parameters
nh call github create_issue '{…}'    # run it; prints JSON

The gateway verifies the token, attaches the real credential on your side, and records the call against the execution. To a model there are only ever three operations — list, docs, call — never N connectors × M tools.

A connector is declared, not coded: identity, auth, and tools with JSON Schema parameters. Keys go in headers or the query string, Basic credentials are encoded for you, and a binary response is stored whole rather than decoded as text.

Remote MCP servers are connectors too — kind: "mcp" and a server_url. The tools are discovered with tools/list, their descriptions treated as untrusted, and a tool is mutating unless the server marks it read-only. MCP servers that use OAuth are signed in to with nothing set up by hand: discovery and dynamic client registration are built in. Every request the MCP client makes — sign-in included — goes through the same outbound guard as an HTTP connector: declared hosts only, https, public addresses, bounded redirects.

Sixty-two ready-made declarations ship separately in @nativeharness/catalog. With the nativeharness package, pass them as new Harness({ connectors: { registry } }).

Part of nativeharness — the agent harness native to your app. Apache-2.0 · docs · source