WTFox MCP Server
Connect Claude, or any AI assistant, to your WTFox dealership CRM. Ask about leads, deals, quotes and appointments in plain language, straight from the chat.
This address is the connector endpoint, not the web app. The WTFox web app is at app.wtfox.ai.
Operational, v0.3.89Endpoint
https://mcp.wtfox.ai/mcp
Everyone connects to this same URL. Your identity comes from your sign-in or your key, not from a separate address per dealership.
Option 1: sign in with your WTFox account Recommended
Nothing to install and no key to copy. You add one link in Claude, then sign in to WTFox once.
In Claude
- Open Customize, then Connectors.
- Click + and choose Add custom connector.
- Paste
https://mcp.wtfox.ai/mcpand click Add. - Click Connect next to WTFox.
Then WTFox opens in your browser
- Sign in to WTFox if you are not already signed in.
- A screen shows what Claude is asking to access. Click Approve.
- Back in Claude, WTFox shows as connected. Start asking.
On a Team or Enterprise plan, an Owner adds the connector once under Organization settings, then Connectors. Everyone else starts from step 4.
You only see what your own WTFox login can see. To disconnect later, open WTFox Settings → API Keys → Connected apps, or remove it from Claude's Connectors.
Option 2: connect with an API key For developers and other tools
- Sign in to WTFox and open Settings → API Keys.
- Create a key, choosing its scopes: Read (always on), Write, and Review Queue.
- Copy the key. It is shown only once.
{
"mcpServers": {
"wtfox": {
"url": "https://mcp.wtfox.ai/mcp",
"headers": {
"Authorization": "Bearer wtfox_your_key_here"
}
}
}
}
The server only registers the tools your key has scopes for. A read-only key will
not see create_lead,
reply_to_conversation, or the Review Queue tools at all.
Things to ask once connected
- “Summarise my pipeline and flag any deal that has gone quiet for more than a week.”
- “Draft a follow-up to the leads that asked about financing yesterday.”
- “What is waiting in my Review Queue, and what would you approve?”
Reference
| Path | Purpose |
|---|---|
/mcp | JSON-RPC over Streamable HTTP. Requires a bearer token. |
/health | Liveness and build version. |
/.well-known/oauth-protected-resource | RFC 9728 metadata pointing at the authorization server. |