# Choose What to Connect | EasyNet Docs

Source: https://easynet.run/docs/connect

Docs / Choose what to connect
[Docs](https://easynet.run/docs)

Docs

# Start with what your agent cannot reach.

Choose the resource you want your agent to use. Compare the setup steps and access requirements before you start.

These are different starting points, not four steps you must complete. Each guide explains its result and what still needs a separate check.

## Choose a resource

### A function on a provider machine

EasyRemote, currently Python

Source workspace · paired Runtime

What this guide helps you do

Register your function and check that it appears in the local capability directory.

Implementation, model weights, dependencies, and credentials remain with the provider. Inputs and returned output cross the call boundary.
[Function setup](https://easynet.run/docs/connect/function)

### A device or operator workflow

EasyNet CLI

Public installer · account to pair

What this guide helps you do

Install and pair a device, start its Runtime, and request the live device directory.

The CLI owns daemon pairing and Runtime lifecycle. The device keeps its execution and policy boundary.
[Runtime setup](https://easynet.run/docs/connect/runtime)

### Tools you want to use through MCP

Choose where you want the tools to be used

Public CLI · paired Runtime for live tools

What this guide helps you do

Connect EasyNet tools to Codex, or configure an upstream MCP server. Choose one direction.

Choose one path below. Each needs explicit setup; connecting tools does not automatically make them discoverable or grant permission to call them.
[Use EasyNet from Codex](https://easynet.run/docs/connect/mcp?direction=inbound#run-guide)[Give an EasyNet Agent an MCP tool](https://easynet.run/docs/connect/mcp?direction=outbound#run-guide)

### Mapped folders, clipboard items, favorites, or captures

Device Context

Public CLI · local setup

What this guide helps you do

Save a project folder mapping and inspect local references. Then follow the separate steps for agent access.

References remain device-scoped under the local Context store. Capturing a reference does not make it Realm-visible.
[Context setup](https://easynet.run/docs/connect/context)

## Check your connection

For a resource you want another agent to use, check each stage separately. Local setup does not automatically make it discoverable or give an agent permission to call it.

01

### Available on this device

Check the local status or listing: is the provider or adapter reachable on this device?

02

### Visible to the intended agent

Request the live directory in the intended scope: does it contain your capability?

03

### A permitted call completes

Make a call as the intended agent and inspect its result and terminal Receipt. Finding a capability is not the same as executing it.

Next

## Explore examples or get help

Not ready to connect a resource? Inspect the public function examples. For a guided function connection with a second caller, request Technical Alpha.
[Run the public source check](https://easynet.run/docs/source-check)[Request Technical Alpha](https://easynet.run/pilot)