Skip to main content

​
General

Super Magic is the AI assistant built into Thread Inbox. Ask it anything in plain language (about a ticket, a contact, a company, a device), and it finds the answer or does the work. Start with Meet Super Magic.
Not in chat. It reads freely, and before any write it shows a Confirm action card: nothing happens until you click Confirm. The exception is a Super Magic Agent running in a Flow: nobody confirms each step there, so the write tools you check in the Flow become its entire scope.
Super Magic only offers you the tools you’re allowed to use. Write actions are controlled by your admin, intents and flows are always admin-only, integration tools appear only once connected and enabled, and some tools need your own sign-in. Work through Why a tool might be missing or the admin guide troubleshooting checklist.

​
Skills

Skills can be triggered wherever Super Magic itself runs, plus in Flows:
  • Super Magic in Inbox: run a skill on demand in chat, confirming each write.
  • Super Magic in the Slack and Teams Companion Apps: the same saved skills, from the channel you’re already working in.
  • A Flow: the Run Skill action (beta) runs a shared skill unattended on every matching ticket. See Flows.
Thread MCP is the one place that can’t trigger a saved skill — see the next question.
No. Thread MCP puts Thread’s tools inside your own LLM (Claude, ChatGPT, Copilot, Cursor), with a curated subset of Super Magic’s reads and writes. Saved skills live in Super Magic, so an MCP client can’t invoke one by name. Working from an MCP client, run the skill’s prompt text itself instead.
A Flow’s Run Skill action runs shared skills only. A personal skill is skipped silently, and only an admin can share one. See the Flows FAQs for the rest of the checklist.
Skill instructions are capped at 3,000 characters, and the same cap applies to a Flow’s agent prompt. A longer skill saved before the cap keeps running — you just can’t save it again until it’s shortened. Building with Super Magic covers how to get a long prompt under the limit.
A skill is a prompt that does one job on your tickets, run on demand in Super Magic with you confirming each write. A Super Magic Agent is a Flow action that fires on a matching ticket event and runs unattended, with the write tools you checked as its scope. See Agents and Skills.

​
Thread MCP

Copilot Studio, yes. Microsoft ships two Copilot products that both connect an MCP server, and only one works with Thread today:
  • Copilot Studio, the agent builder, needs nothing but the Thread MCP URL and a Thread sign-in. Follow Connect Copilot Studio to Thread MCP.
  • Microsoft 365 Copilot custom federated connectors asks for a Reference ID and an OAuth client ID and secret issued by the MCP server. Thread issues none of those, so that path isn’t available. If a setup dialog asks for those fields, you’ve landed on the federated connector path: use Copilot Studio instead.
Authentication → OAuth 2.0, then Configuration type → Dynamic (with discovery), with every credential field left empty. Thread’s MCP server publishes OAuth 2.1 discovery metadata and supports dynamic client registration, so Copilot Studio discovers the endpoints and registers itself when you select Create.Never pick Manual: it requires a client ID and secret preissued by the MCP server, which Thread doesn’t hand out. Microsoft describes all three options in Configure OAuth 2.0 authentication.
That failure happens before Copilot Studio ever contacts Thread, so nothing on Thread’s side fixes it. Copilot Studio builds a Power Platform custom connector behind the scenes, and it could not create one. The usual cause is an orphaned connector from an earlier failed attempt: it exists in Dataverse, never shows in the Copilot Studio UI, and blocks every retry, including retries under a new name.Delete it in Power Apps under Custom connectors, wait a few minutes, then retry with a plain name such as Thread. The full checklist, covering environment permissions, data loss prevention policies and the Dynamic fallback, is in the developer guide.