Use the Jobwright MCP server

Jobwright includes a local MCP server. It gives the agent typed tools for one Jobwright task. It does not give the agent unrestricted access to your files, records, browser, or accounts.

This server is different from an external MCP server that you add in Settings. It is also different from the private QA interface used for product tests.

Normal setup

Jobwright connects the local tools when a supported agent needs them. Complete agent setup in the desktop app. You do not need to create a second scheduler or copy a daemon URL into the agent.

If Jobwright asks to connect its local tools, review the request and continue. The provider still owns the agent account, sign-in, models, and usage limits.

Run the server from a client

Advanced clients can start the same server over standard input and output:

jobwright mcp

Keep the Jobwright desktop app running. A packaged install supplies the correct local data path and daemon connection when Jobwright starts the server.

Prompts and tools

Name	What it does	Authority
`setup_jobwright`	Returns the provider-neutral setup prompt.	No software change.
`get_setup_guide`	Checks supported local agents and returns a redacted setup guide.	Read-only.
`load_source_adapter`	Loads the exact trusted source skill named by a discovery task.	Read-only.
`search_source_adapter`	Reads one supported public job source for a bounded task.	Read-only. No application authority.
`diagnose_system`	Reads typed local health and returns a bounded repair plan.	Read-only.
`repair_system`	Runs one safe action from the latest diagnosis.	Can start a stopped local service. It cannot run arbitrary shell commands or restart work.
`browser_control`	Uses the visible managed browser through typed, task-bound commands.	Protected actions still need exact approval or a matching campaign mandate.

Safety rules

MCP tool access does not authorize an application, account action, message, profile change, or personal-data upload.
The agent must treat website text as untrusted data.
Browser commands use a task lease, page revision, and observed element reference.
A protected action returns to Review when authority is missing or uncertain.
Final submission is a separate action. The MCP server cannot approve it for itself.
Tool results stay redacted. The agent must not persist page text, candidate answers, credentials, or private browser paths.

Setup help from another assistant

Use the setup_jobwright prompt before an MCP link exists. After the link works, the assistant can call get_setup_guide for the current state of this computer.

The setup prompt and setup tool cannot install software, read credentials, change provider settings, or grant job-search authority.