Open the JT Power Tools Chrome extension and go to the MCP tab. Select Gemini from the platform picker to see your configuration with keys pre-filled.
Edit your Gemini CLI settings file at:
On Windows, this is typically %USERPROFILE%\.gemini\settings.json. Create the file if it doesn't exist.
Add the following to your settings.json file under the mcpServers key:
Or use the Copy Config button in the JT Power Tools extension MCP tab — it pre-fills your keys automatically.
After saving settings.json, restart the Gemini CLI for the MCP server to be picked up.
That's it! Ask Gemini about your JobTread data. Try:
"Show me my active jobs" or "What tasks are due this week?"
Gemini CLI uses the httpUrl key (not url) for remote MCP servers. This is per Google's Gemini CLI documentation. The JT Power Tools extension generates the correct format automatically when you select Gemini.
Gemini CLI vs gemini.google.com: MCP is currently supported through the Gemini CLI (command line tool). The gemini.google.com web interface does not yet support connecting custom MCP servers directly.
Gemini CLI connects to the JT Power Tools MCP server using bearer token authentication. Your License Key and Grant Key are combined into a single token that authenticates each request.
The MCP server provides 24 read-only tools for querying your JobTread data — jobs, budgets, tasks, schedules, contacts, daily logs, and more. Your data cannot be modified through MCP.
"401 Unauthorized" — Double-check your License Key and Grant Key. Make sure the format is Bearer LICENSE_KEY:GRANT_KEY with a colon separator.
"MCP server not found" — Make sure you're using httpUrl (not url) in your Gemini settings. Restart the CLI after saving.
"Grant Key expired" — Grant keys expire after 3 months of inactivity. Generate a fresh one from the JT Power Tools extension → MCP tab.
"Tier doesn't include MCP access" — MCP requires a Power User subscription. Upgrade here.
Still stuck? Join our Discord for help.