What stays local
System implementation, credentials, and provider-owned data access.
CRM reads and follow-up creation become narrow typed operations without database credentials.
Each new agent integration rebuilds the wrapper, while shortcuts tend to grant more access than the task needs.
Publish three allowlisted operations: account read, revenue read, and follow-up creation.
System implementation, credentials, and provider-owned data access.
Validated identifiers, bounded parameters, released JSON results, caller identity.
Agent platforms can reuse the backend through stable schemas; MCP may present the same Abilities.
The project demonstrates the capability backend; it does not reimplement an MCP server or full catalog.
44c768ca26d0f92a5ab9d1d03342895c29c27dc6This Provider/Client walkthrough requires compatible EasyRemote, EasyNet-Cli, and EasyNet-Axon sibling source checkouts, a compatible Hub, and a paired, running Runtime. The source is public; clean installation from public packages is not yet verified. Technical Alpha offers guided setup. Use the pinned EasyRemote revision below; this page does not pin the other components. Runtime admission still determines whether the caller may execute the function.
# From EasyRemote revision 44c768ca26d0f92a5ab9d1d03342895c29c27dc6
cd gallery/projects/02_mcp_tool_mesh
# Terminal 1
uv sync --frozen
uv run python node.py
# Terminal 2 (same project)
uv run python client.pyRead the setup first. You need compatible sibling source checkouts, a compatible Hub, and a paired, running Runtime. Technical Alpha offers guided help; public-package clean installation is not yet verified.