Customize and connect

Your assistant should fit the tools and habits you already have. Jarvis exposes provider configuration, MCP connections, Python extensions, reusable skills and agent profiles. The useful combination is the one you actually configure and can inspect.

Use the model configuration command and the matching credentials. Local servers need their own installed model and running process.

uv run jarvis model

Use Jarvis setup and the source documentation for each MCP server, extension or gateway adapter.

uv run jarvis setup

Run diagnostics when a dependency, model or connection is missing.

uv run jarvis doctor

Extension points are not preconnected services. MCP tools and skills describe what can be connected or taught. External accounts, dependencies and credentials still need setup.

Local-first is a data-path choice. Local files and settings stay on your machine until used by a configured tool or provider. Cloud models and connected services process the requests sent to them; voice requires Gemini Live.

You keep explaining the same review priorities at the start of each project.

Try: “Create a reusable review skill that checks public contracts, small-screen layouts and relevant tests.”

A reusable working method that can be applied when relevant. Quality still depends on the instructions, model and actual tool evidence.