Browse documentation
Your business, connected
Your apps.
Your MightWork.
Connect your store, send new leads to your other apps, or give an assistant access to your workspace. Choose a guide and check the first result.
Help me connect my existing MightWork account to this assistant and finish setup. Follow https://mightwork.us/docs/getting-started and the assistant-specific guide at https://mightwork.us/docs. Configure what you can; guide me through sign-in, workspace selection and consent. Never ask for credentials in chat. Call workspace to verify the business and permissions, then review setup using permitted tools. Ask only for missing details. Draft missing business facts, services, hours and timezone from my answers. MCP cannot save these settings: help me enter them through the dashboard with my authorization, or give me ready-to-paste values and links. Verify saved changes. Return a checklist of what works, what needs input and what is blocked. Do not change bookings, send messages or spend money during setup.
Apps
WooCommerce
Bring the contact from each new WooCommerce order into your MightWork Leads inbox.
Shopify
Bring contacts from new Shopify orders into your selected MightWork workspace.
Zapier
Use MightWork's New Lead trigger to start a Zap when a contact enters your Leads inbox.
AI assistants
Claude
Use MightWork tools from a Claude custom connector or Claude Code.
ChatGPT
Add MightWork as a custom MCP app using your existing ChatGPT account.
Grok
Add MightWork as a custom connector in Grok, or call it from the xAI API.
Meta Muse
Give Muse a custom connector to your workspace with its own API key.
Reference
MCP server
One authenticated server for your workspace's business tools.
Client API
Call the same operations from scripts, custom agents and your own applications.
Agent skills
Small task playbooks that use live MightWork tools and respect your permissions.
Help
Fix a connection
Find the missing step without sharing a password or API key.
Lead forms
Build a form people can complete and correct. Try the working HTML, then add the server checks that a browser cannot enforce.