Tread Connection docs

Updated October 5, 2026

Tread Connection connects your AI assistant to JobTread. It works with Claude, Meta Muse and any other assistant that supports remote MCP servers. Members ask about their jobs, schedule and daily logs in plain language, and get JobTread how-to answers grounded in JobTread's public Help Center, tuned to 6 trade brains. It is a remote MCP server at https://treadconnection.ai/mcp.

1. What you need
2. Connect it to Claude
3. Connect it to Muse
4. Other MCP clients
5. Connect your JobTread account
6. Tools
7. Photos to posts
8. Where the JobTread knowledge comes from
9. What each person can see
10. Sign-in and security (for IT admins)
11. Limits
12. For reviewers and automated testers
13. Troubleshooting
14. Support

What you need

• A Tread Connection membership. See plans.
• A JobTread account. For job data, someone with admin rights in your JobTread organization connects it once (see below). The knowledge base works without it.
• An AI assistant that supports remote MCP servers: Claude (web, desktop or mobile), Meta Muse, or another MCP client.

Connect it to Claude

1. In Claude, add Tread Connection from the connector directory, or go to Settings > Connectors > Add custom connector and enter https://treadconnection.ai/mcp.
2. Claude opens the Tread Connection sign-in page. Enter the email you use for the Tread Connection community and we email you a 6-digit code. Codes expire after 10 minutes.
3. If you have a Tread Connection API key instead, open Use an API key instead and paste it.
4. Approve, and you are sent back to Claude with the tools ready.

To disconnect, remove or disconnect Tread Connection in Claude's connector settings and Claude stops using it. To cut access off on our side right away, regenerate your API key at treadconnection.ai/my/access. That ends every assistant connection made with the old key at once. Your JobTread connection belongs to your Tread Connection account, not to one assistant, so it stays until you close your account or email us to remove it.

Connect it to Muse

1. In Muse, add Tread Connection from the connector list. Until the listing is live, ask Muse in the chat: "Add a custom connector for Tread Connection. It is a remote MCP server at https://treadconnection.ai/mcp."
2. Muse opens the Tread Connection sign-in page. Enter the email on your Tread Connection community account and we email you a 6-digit code, or open Use an API key instead and paste your key.
3. Approve, and Muse lists the tools. Ask it to run my_account to check the connection.

To disconnect, remove Tread Connection in Muse. Muse can revoke its tokens on our side through the revocation endpoint (see Sign-in and security). To end every connection yourself, regenerate your API key at treadconnection.ai/my/access. Your JobTread connection belongs to your Tread Connection account, not to Muse, so it stays until you close your account or email us to remove it.

Other MCP clients

Point any client that supports remote MCP over Streamable HTTP at https://treadconnection.ai/mcp. Clients that support OAuth discover everything from the metadata below and register themselves. Clients that don't can send a Tread Connection API key as Authorization: Bearer <key>.

Connect your JobTread account

This is done once per JobTread organization, by someone with admin rights in it.

1. Open JobTread > Settings > Integrations > API.
2. Find your organization's section header and click + Grant on it. Use the grant for your organization, not "All Organizations".
3. Name it Tread Connection, save, and copy the key. JobTread only shows it once.
4. Sign in at treadconnection.ai/my/team/connect and paste the key. We check it with a read-only query, show you which organization it belongs to, and connect only after you confirm.

Nothing is written to your JobTread account during this step.

Tools

These are the 15 tools a member sees. None of them change anything in JobTread, and none is a sensitive write. Tools that take a job accept either the job number shown in my_jobs (for example 101) or the JobTread job ID.

Extra tools for organization admins

An admin of a connected organization also gets tools to audit their JobTread setup, back up and compare configuration, and see open customer invoices and vendor bills. Three of these can write to JobTread, and each is built to be safe to try:

• apply_audit_fix and bulk_apply_audit_fix apply a short fixed list of configuration fixes (a missing sales tax rate, a time entry cost item, placeholder workflow names, missing job custom fields). Both preview the change by default and only write when the admin asks for it. A backup is taken first.
• restore_backup recreates configuration items that are missing from the organization. It previews by default, never overwrites or deletes existing items, and only writes when the admin asks for it.

Every tool carries MCP read-only and destructive hints, so your assistant can ask you before running one that writes.

Errors

A tool that can't answer returns a plain-language message instead of failing silently. The ones you may see: no JobTread account connected yet, a job your JobTread role can't see (it names the job and suggests my_jobs), a missing required input (the message names the field), JobTread errors passed through with the organization they came from, and the rate-limit message, which says when the limit resets. Sign-in problems come back from /mcp as a 401 with a WWW-Authenticate header that points to the OAuth metadata.

Photos to posts

Turn a finished job's photos into a week or month of social posts. Claude looks at every photo, sorts before, progress and after, pairs before and after shots only when they show the same spot, writes a caption for each platform from what is actually in the photos, and shows you the plan before anything is scheduled.

What you need

• Claude with Tread Connection connected (see above).
• The job's photos uploaded to the job in JobTread (the job's Files). Phone photos in JPEG or PNG work. HEIC files are skipped.
• A scheduler to post from. Zernio is the most direct: add its connector in Claude (https://mcp.zernio.com/mcp) and Claude creates the posts as drafts for you to approve. It is free for your first two accounts, for example your Facebook page and Instagram. Metricool and GoHighLevel work through a CSV Claude writes for you, and Buffer or Meta Business Suite by copy and paste.

How to run it

1. Ask Claude: "Make social posts from job [name or number] with photos_to_posts."
2. Claude looks at each photo and notes what it shows. Tell it anything it can't see, like the town, the customer's OK to share, or what the job was.
3. Review the plan it shows you (which photos, which platform, the caption) and ask for changes.
4. Say go. Claude creates drafts in your scheduler, or hands you the CSV. Nothing publishes until you approve it there.

Photos come from the job the way your JobTread role sees it. The post links point to JobTread's own image server, so the scheduler can fetch them without you downloading anything.

Where the JobTread knowledge comes from

jobtread_help and load_agent answer from three kinds of material:

• Articles from JobTread's public Help Center. Answers quote short passages and link to the original article.
• Notes we wrote from JobTread's public training videos.
• Guides Tread Connection wrote.

Every passage names its source. When a Help Center passage and one of our notes disagree, the tool tells your assistant to go with the Help Center. For questions that are clearly outside JobTread, such as tax, legal, insurance or hiring advice, the tool declines instead of returning passages. For everything else, it returns the closest passages and tells your assistant to answer only from them and to say plainly when they don't cover the question. We check the Help Center for changes every 6 hours and the video library once a day.

Tread Connection is an independent product of Rising Creek Construction LLC. It is not affiliated with or endorsed by JobTread, and JobTread's names and content belong to JobTread. If JobTread asks us to change or remove any of its material, we will. Rights holders can reach us at jakemauldin@risingcreek.ai.

What each person can see

A JobTread grant key covers the whole organization, so Tread Connection limits results by each person's JobTread role when it runs a query:

• Owners and admins see the full organization.
• Project managers see the jobs they are assigned to.
• Vendors see their own work.
• Customers see their own job, and only daily logs marked visible to them.

No member can reach another organization's data.

Sign-in and security (for IT admins)

• Protocol. MCP over Streamable HTTP at https://treadconnection.ai/mcp. Every tool requires a signed-in member.
• Authorization. OAuth 2.0 authorization code flow with PKCE (S256) and dynamic client registration. Metadata: /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp.
• Clients. Clients register at /register and must list their redirect URIs (https, or http on localhost). Codes are only sent to a registered redirect URI, are single-use, expire after 10 minutes, and are bound to the client they were issued to. Registered clients must use PKCE.
• Tokens. Access tokens last up to 30 days and refresh tokens up to one year, and refresh tokens rotate on each use. A connection nobody uses expires on its own. Clients can revoke a token at /oauth/revoke (RFC 7009), which ends that connection immediately. We can also disable a member's key, which blocks every request made with it, within one business day of a request.
• Stored credentials. API keys, OAuth access and refresh tokens, and web sign-in sessions are stored only as SHA-256 hashes. No plaintext key or token is kept in the database or in its backups, and our web server logs redact keys and tokens from every request. A key is shown once, when it's created, and can't be looked up later: a lost key is replaced, not recovered. Send a key in the Authorization: Bearer header, not in a URL.
• Sign-in methods. A one-time code sent to the member's email, or a personal API key. Automated testers should use Use an API key instead on the sign-in page, which needs no email.
• JobTread access. Uses the grant key your organization created. We use it only to run the tools your members call.
• Transport. HTTPS only, with HSTS.
• Data. What we store and for how long is in the privacy policy. Terms are here.

Limits

• Every authenticated request to /mcp gets X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers back, including the 429 you get when you're over the limit. A request without a valid key or token gets a 401 with no rate-limit headers, because there's no account to count it against. The my_account tool shows the same limits. Help, agent and account tools don't count toward the hourly limit.
• Requests per hour depend on your plan: 60 for members sponsored by a contractor, 100 on Member and Partner, 200 on Partner Pro and 300 on Team. Free doesn't include MCP/AI tool access, so it has no rate limit here — see pricing. When you hit the limit, the server says how long until it resets.
• One account works on all your devices — there's no device limit. We count apps and networks only to spot a key shared across a company, and we'll reach out if we see that. Team members should get their own invite instead of sharing a key.

For reviewers and automated testers

Directory and store reviewers get an API key tied to Summit Ridge Builders (Demo), a fictional company with sample jobs, tasks and daily logs. It sees the 15 member tools, none of which change anything in JobTread, and it can't reach any real company's data. The key is a test credential, not a production one, and it has member permissions only.

1. Add https://treadconnection.ai/mcp as a connector.
2. On the Tread Connection sign-in page, click Use an API key instead (it is collapsed under the email field), paste the key and approve. Clients without OAuth can send the key as Authorization: Bearer <key> instead.
3. Run my_account. It should show the reviewer account on the Member plan.

Prompts that exercise the tools against the demo company:

• "What jobs are active?" (my_jobs, five active jobs including 101)
• "Give me the overview for job 101." (job_overview, Prairie Ridge Corporate Center)
• "Show the daily logs for job 101." (job_dailylogs) and "Show recent daily logs." (my_dailylogs)
• "What tasks are on the schedule, and which are overdue?" (my_tasks)
• "How do I write a formula in a JobTread budget line?" (jobtread_help, load_agent)
• "What agents can I use, and which trade specializations are there?" (browse_agents, my_agents), then "Set my trade to pool builder." (set_brain)

The demo jobs have no photos, so photos_to_posts answers that the job has none and view_job_photo has nothing to show. No region or account limits apply. There is no checkout or payment inside the connector.

• It allows 1,000 requests an hour and no device limit. You can check both yourself: every authenticated /mcp response carries the rate-limit headers, and the my_account tool reports both.
• It stays active through the review. If it ever stops working, email jakemauldin@risingcreek.ai and we'll respond within one business day.

Troubleshooting

• "No JobTread account connected." Your organization hasn't connected JobTread yet. See Connect your JobTread account.
• The sign-in code didn't arrive. Check spam, and make sure you used the email on your Tread Connection community account. Codes expire after 10 minutes, so request a new one if it's late.
• "Rate limit" message. Wait for the time it shows, then try again.
• "API key suspended." That only happens if we disable a key by hand. Email us and we'll sort it out.
• A job doesn't show up. Your JobTread role may not include it. Ask your JobTread admin.

Support

Email jakemauldin@risingcreek.ai, or post in the Tread Connection community. Tread Connection is a product of Rising Creek Construction LLC and is not affiliated with JobTread.

Privacy Policy · Terms of Service · treadconnection.ai