Other MCP Clients Setup - JT Power Tools

Overview

The JT Power Tools MCP server is compatible with any client that supports the Model Context Protocol (MCP). This guide provides the technical details needed to connect any MCP client to your JobTread data.

What You'll Need

JT Power Tools Premium - Active subscription with MCP access
License Key - Your JT Power Tools license key
Grant Key - Your JobTread API grant key (from the API tab in the extension popup)
MCP-Compatible Client - Any application supporting MCP

Server Endpoints

Endpoint	URL	Purpose
SSE Endpoint	`https://mcp.jobtread-tools.pro/sse`	Server-Sent Events for real-time communication
Message Endpoint	`https://mcp.jobtread-tools.pro/message`	HTTP POST for sending messages
Health Check	`https://mcp.jobtread-tools.pro/health`	Server health status
Tools List	`https://mcp.jobtread-tools.pro/tools`	Available MCP tools

Authentication

All requests must include an Authorization header with a Bearer token. The token format is:

Authorization: Bearer LICENSE_KEY:GRANT_KEY

Where:

LICENSE_KEY - Your JT Power Tools premium license key
GRANT_KEY - Your JobTread API grant key

Security Note

Keep your keys secure. Never share them publicly or commit them to version control.

Standard MCP Configuration

For clients using the standard MCP JSON configuration format:

{
  "mcpServers": {
    "jobtread": {
      "url": "https://mcp.jobtread-tools.pro/sse",
      "headers": {
        "Authorization": "Bearer YOUR_LICENSE_KEY:YOUR_GRANT_KEY"
      }
    }
  }
}

Claude Desktop (via mcp-remote)

Claude Desktop only supports local stdio servers. Use mcp-remote as a bridge:

Step 1: Install mcp-remote

npm install -g mcp-remote

Step 2: Configure Claude Desktop

Add to ~/.claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "jobtread": {
    "command": "npx",
    "args": [
      "mcp-remote",
      "https://mcp.jobtread-tools.pro/sse",
      "--header",
      "Authorization: Bearer YOUR_LICENSE_KEY:YOUR_GRANT_KEY"
    ]
  }
}

HTTP API Usage

For custom integrations, you can use the HTTP endpoints directly:

List Available Tools

curl -X GET "https://mcp.jobtread-tools.pro/tools" \
  -H "Authorization: Bearer YOUR_LICENSE_KEY:YOUR_GRANT_KEY"

Call a Tool

curl -X POST "https://mcp.jobtread-tools.pro/message" \
  -H "Authorization: Bearer YOUR_LICENSE_KEY:YOUR_GRANT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "tools/call",
    "params": {
      "name": "search_jobs",
      "arguments": {
        "query": "kitchen remodel"
      }
    }
  }'

Available Tools

The MCP server provides these read-only tools:

Tool Name	Description	Parameters
`search_jobs`	Search and list JobTread jobs	`query` (optional), `status` (optional)
`list_customers`	Get customer information	`limit` (optional)
`list_vendors`	Get vendor information	`limit` (optional)
`list_tasks`	Get tasks and to-dos	`job_id` (optional), `status` (optional)
`get_budgets`	Get budget details for jobs	`job_id` (required)
`knowledge_lookup`	Search knowledge base	`query` (required)

Read-Only Access

For security, the MCP server currently provides read-only access to your data. To make changes, use the JobTread web interface.

Testing the Connection

Use the health endpoint to verify your connection:

curl -X GET "https://mcp.jobtread-tools.pro/health"

Expected response:

{
  "status": "healthy",
  "version": "1.0.0"
}

Troubleshooting

401 Unauthorized

Check that your License Key is valid and active
Verify the Grant Key is correct
Ensure the Authorization header format is correct: Bearer LICENSE:GRANT

403 Forbidden

Your subscription may not include MCP access
Check your subscription tier supports the MCP feature

Connection Timeout

Verify the endpoint URL is correct
Check your network connection
Try the health endpoint to verify server status

Empty Results

Verify your Grant Key has the necessary permissions in JobTread
Check that you have data in JobTread matching your query
Try regenerating your Grant Key in the API tab

Rate Limits

To ensure fair usage:

Requests per minute: 60
Concurrent connections: 5

If you exceed these limits, you'll receive a 429 (Too Many Requests) response.

Support

Need help setting up your MCP client?

💬

GitHub Issues

Ask questions or report issues

🔑

Premium Features

Learn about all premium features