> ## Documentation Index > Fetch the complete documentation index at: https://help.owlery.ai/llms.txt > Use this file to discover all available pages before exploring further. # AI Assistants & MCP > Owlery does not currently offer a Claude connector or MCP server. Here's what exists today and what's in development. **Owlery does not currently offer a Claude connector or an MCP server.** If you've been asked to connect Owlery to Claude, ChatGPT, Copilot, or an in-house agent, there is no first-party connector to install today. If what you're after is an AI assistant that can answer questions about your freight, see [Hootie](/shippers/hootie) — our AI teammate for Slack, Teams, and email, currently in beta for customers on request. ### What this means today * There is no Owlery MCP server to add to Claude, Claude Code, or any other MCP client. * Owlery does not appear in the connector directories of Claude, ChatGPT, or Microsoft Copilot. * Nothing in `Settings → Integrations` will connect Owlery to a third-party AI assistant. * Hootie is Owlery's own assistant and is added through Slack or Teams — not through an MCP client. If you find something claiming to be an official Owlery connector for an AI assistant, it isn't ours — please let us know at [support@owlery.ai](mailto:support@owlery.ai). ### What you can do in the meantime Two options, depending on what you need: **Ask about the Hootie beta.** If the goal is "let people ask questions about our freight in the tools they already use," [Hootie](/shippers/hootie) covers that in Slack, Teams, and email — without you building or maintaining anything. It's in beta and available to customers on request. **Build on the Open API.** If you need Owlery data inside your own assistant or agent, our [Open API](https://owlery.ai/open/api) is the supported path, and several customers have used it as the foundation for internal tooling. A few things worth knowing before you go down that road: * You'll be responsible for the connection, its credentials, and anything the assistant does with the data it reads. * Treat API credentials the way you'd treat any other production secret — an assistant with a saved key inherits everything that key can do. * Freight data often contains customer names, addresses, and rates. Check with whoever owns data policy at your company before routing it through a third-party model. ### What's in development Our AI roadmap is actively in development. Hootie is the first thing to ship from it, and native support for third-party AI clients — including MCP — is part of what we're evaluating next. We're not announcing dates or specific clients yet. ### Tell us what you'd want If you have a specific use case in mind — a question you'd want to ask an assistant about your loads, a workflow you'd want it to handle — that feedback genuinely shapes what we build first. Email [support@owlery.ai](mailto:support@owlery.ai) and tell us what you'd use it for.