Schema | Jarvis CLI

Jarvis CLI

Describes the environment variables required to run the server.

Name	Required	Description	Default
`JARVIS_HOME`	No	Configuration folder used by Jarvis. Defaults to ~/.jarvis (Windows: %USERPROFILE%\.jarvis). Set this to reuse an existing jarvis-ts data folder so API keys and tunnel addresses are not recreated.	~/.jarvis
`PC_MCP_PORT`	No	MCP server port. The server binds to 127.0.0.1 and exposes /mcp. Defaults to 8765.	8765
`PC_MCP_ENABLE_READ`	No	Enable read tools. Defaults to true.	true
`PC_MCP_ALLOWED_DIRS`	No	Allowed folders for file and terminal tools, separated by ';'. Supports ~ and %USERPROFILE%. If empty, folders are auto-detected.	~/Work;Desktop;Downloads;Documents
`PC_MCP_ENABLE_WRITE`	No	Enable write tools. Defaults to true.	true
`PC_MCP_TERMINAL_MODE`	No	Terminal command policy mode: allowlist (recommended) or blocklist. Defaults to allowlist.	allowlist
`JARVIS_DASHBOARD_PORT`	No	Dashboard port. The dashboard binds to 127.0.0.1 and is token-protected. Defaults to 8766.	8766
`PC_MCP_ENABLE_TERMINAL`	No	Enable terminal tools. Defaults to true.	true
`PC_MCP_EXTRA_ALLOWED_COMMANDS`	No	Additional commands to add to the terminal allowlist, separated by ';'. Example: Start-Process;Stop-Process.

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 recent community issues