Schema | remote-agent-connector

remote-agent-connector

Describes the environment variables required to run the server.

Name	Required	Description
`REMOTE_AGENT_BIND_HOST`	Yes	Host interface to bind to (e.g., 0.0.0.0)
`REMOTE_AGENT_BIND_PORT`	Yes	Port to bind to (e.g., 3030)
`REMOTE_AGENT_DATABASE_URL`	Yes	Database URL for the remote agent (e.g., postgres://... or sqlite:///...)
`REMOTE_AGENT_HUB_AUDIENCE`	Yes	Audience for the hub (e.g., remote-agent-connector)
`REMOTE_AGENT_ALLOWED_HOSTS`	Yes	Comma-separated list of allowed hosts (e.g., remote-agent-mcp-connector:3030,127.0.0.1:3030,localhost:3030,10.21.4.101:3051)
`REMOTE_AGENT_PRIVATE_MCP_URL`	Yes	Private MCP endpoint URL (e.g., http://remote-agent-mcp-connector:3030/mcp)
`REMOTE_AGENT_ALLOW_SQLITE_DEV`	No	Set to 1 to allow SQLite for local development only
`REMOTE_AGENT_MCP_BEARER_TOKEN`	Yes	Bearer token for MCP authentication
`REMOTE_AGENT_PUBLIC_RELAY_URL`	Yes	Public relay WebSocket URL (e.g., wss://10.21.4.101:3051/relay)
`REMOTE_AGENT_ALLOW_INSECURE_HTTP`	No	Set to 1 to allow insecure HTTP for local development only
`REMOTE_AGENT_HUB_DELEGATION_SECRET`	Yes	Secret used for hub delegation
`REMOTE_AGENT_OPERATOR_BEARER_TOKEN`	Yes	Bearer token for operator authentication

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues