Client integration

SharedData provides local data containers, an authenticated HTTP API, MCP access and worker execution. Choose the interface that fits your process boundary and grant only the permissions a client needs.

Data access through MCP

The SharedData package supplies the shareddata-mcp entry point. Configure it in a compatible agent client's MCP settings using the configuration and permissions of your own SharedData deployment. Review the supported tools and the deployment's authorization before granting access. Installing a client does not grant it access to your data.

Remote access and execution

Remote clients use the installation's endpoint and an appropriately scoped token:

Variable	Meaning
SHAREDDATA_ENDPOINT	Your SharedData server's HTTPS origin
SHAREDDATA_TOKEN	A token permitted to perform the requested operation

Keep values in your environment or secret store. See the HTTP API guide for remote container access and batch jobs for tracked execution.

A dispatch identifies a worker, repository, routine and arguments. Generic identifiers such as operator@WORKER, ExampleProject and jobs/example are illustrative, not a preconfigured worker fleet. Consult the client interface's documentation for accepted routine formats and arguments; different entry points can use different conventions.

Confirm the result

HTTP 201 means the command was queued. It does not mean the routine completed. Check the worker, schedule state, job result and logs before resubmitting a command. Permissions, credentials, lifecycle management and data ownership remain with the SharedData deployment operator.