# ecbyts > ecbyts connects environmental and occupational models, field data and reports. The Agent Hub explains the current browser context and offers connection setup for AI agents. Reading instructions does not grant access. ## Hosted MCP: four authorized reads 1. Open the application and choose **Agente IA / AI Agent**, then **Connect AI**. Use **Copy configuration** for this installation's configured MCP HTTP endpoint. It is derived from the installation's configured backend as `/functions/v1/mcp`; there is no default endpoint for unconfigured environments. 2. A human account holder creates the key in **Create or manage key**. Select operations, models, an optional organization restriction and expiry; revoke it in the same panel when access ends. If the environment has not yet received these controls, wait for its update. Agents do not create accounts or keys automatically. 3. Configure an MCP HTTP client with the copied JSON. Replace the literal `` placeholder privately in that client. Check the configured destination first; never paste a real key into chat or send it to a different server. Authentication uses `Authorization: Bearer `. Available read names: `list_models`, `get_model_summary`, `get_elements`, `get_observations`. The key and server restrict which operations and owner models are accessible. The service does not write data or read the model currently open in a browser. Calls are subject to the holder's plan quota. A copied configuration is not proof that the endpoint is deployed, reachable or authorized. Example: `list_models`, then `get_model_summary` with an authorized `modelId`; `get_elements` can filter by `family`, and `get_observations` by `modelId`, `elementId` and `parameter`. ## Installed portable CLI and its MCP adapter Obtain the CLI artifact and its verification information through the authorized distribution channel. No public npm package or direct download is announced here. If already installed, inspect the actual version and supported contract: ```text ecbyts --json doctor ecbyts --json capabilities list ecbyts --json schema models.list ``` `doctor` checks only the local environment; it does not authenticate or probe the server. A catalog entry is not proof of an executable command or remote authorization. Read the installed version's availability and schema before use. Cloud writes remain dependent on their implemented server contract. For the installed CLI's MCP adapter, use `ecbyts harness --stdio` with credentials configured in the client's protected environment. On Windows, clients without a shell must start `node` with the full path to `ecbyts-cli/bin/ecbyts.mjs` under `npm root --global`, followed by `harness` and `--stdio`. Consult the artifact's guide for environment-specific credential setup. This adapter is distinct from the development server below. ## Dedicated HTTPS browser through the installed CLI harness In the same persistent `ecbyts harness --stdio` process, `browser_open` opens its own visible, non-persistent Chromium window at https://ecbyts.com. Complete normal login and select the authorized model in that window. `browser_pair` connects an ephemeral public key to the current account, organization and model for up to ten minutes. `doctor --offline` reports the pinned optional driver and browser availability. Use `browser_context`, `browser_catalog`, `browser_history` and `browser_run` with `transport: "owned-ui"`. The paired session allows `model.elements.list`, `model.elements.get` and `model.elements.update`; execution uses the existing command bar, permissions and history. Keep the reviewed expectedContext and correlate requestId/entryId. A paired signature identifies the controller key, not an AI vendor or additional product rights. After an uncertain outcome, use `browser_result` with lookupRequestId; never resend the effect with a new id. Existing receipt lookup remains available after the hundred-request limit while the same session remains authorized. `browser_close`, EOF and process shutdown close only owned resources; save explicitly before closing. A visible scene update is not proof of cloud persistence. Isolated one-shot CLI calls cannot retain this browser, and unavailable UI contracts do not permit development-bridge injection or attachment to a personal browser. ## Legacy MCP development server `scripts/ecbyts-mcp-server.mjs` is for developers who already have the repository and its local dependencies. It rejects new scoped agent keys; do not reuse a new restricted hosted key with this legacy server. Its `ecbyts_agent_hub` tool provides static repository guidance, not the browser session or its open model. That tool is absent from the hosted service. ## Guides - [Connection guide](https://ecbyts.com/docs.html#mcp-server) - [Installed CLI and MCP adapter guide](https://ecbyts.com/docs.html#mcp-cli) - [Development server](https://ecbyts.com/docs.html#mcp-local) - [Excel/API OpenAPI](https://ecbyts.com/openapi/ecbt-api.json)