The Connector Directory: The Whole K-12 Ecosystem in One Place
Claude for Teachers ships with a directory of K-12 connectors — ASSISTments, Brisk, Canva, Coteach, Diffit, Eedi, MagicSchool, Snorkl, TeachFX — that unify a fragmented edtech landscape inside one conversation.
Ask a teacher how many apps they're expected to use and watch them wince. The edtech problem was never a shortage of tools — it was the opposite. A tool for diagrams, a tool for leveling text, a tool for slides, a tool for practice problems, each with its own login, its own tab, its own island of data that never spoke to any other. Every one of them saved time in isolation and cost time in aggregate, because the teacher became the integration layer, ferrying context by hand from one app to the next.
The Claude for Teachers connector directory is a direct answer to that fragmentation. Instead of nine tabs, you get one conversation that can reach into the specialized tools when it needs them. New connectors in Anthropic's directory bring a working slice of the K-12 ecosystem — ASSISTments, Brisk Teaching, Canva for Education, Coteach, Diffit, Eedi, MagicSchool, Snorkl, TeachFX — into a single place where Claude already understands your standards and your curriculum. The unlock isn't any one connector. It's that they compose.
What a connector actually is
A connector is a controlled bridge between Claude and an outside system — a knowledge source or a specialized capability. It's not a bundle of buttons bolted onto a chat window; it's a way for Claude to use an external tool as part of doing your task, then bring the result back into the same conversation. Anthropic even open-sourced the K-12 teacher skills with a plugin/ layout that bundles teacher-focused third-party MCP servers users can enable — the same connector idea, packaged for anyone building on Claude Code.
There are really two kinds of connector in Claude for Teachers, and it's worth keeping them straight. One grounds Claude in knowledge: the Learning Commons Knowledge Graph connector, included for every CfT teacher, gives Claude academic standards across all fifty states plus the competencies beneath them and the order students learn them. The other kind grounds Claude in a capability: the partner tools that generate diagrams, level text, build designs. The first tells Claude what "correct and aligned" means. The second lets Claude produce specific artifacts. Together they mean an artifact is standards-aligned by construction, not by afterthought.
The directory, in one view
Here is the partner ecosystem in its own exact terms — this is the one table this piece will spend. Each row is the connector's precise stated capability, nothing added:
| Connector | What it does | Where it fits |
|---|---|---|
| ASSISTments | Generate auto-scored, standards-aligned math problems for practice/assessment | Math practice & assessment |
| Brisk Teaching | Create interactive student activities and standards-aligned lessons; ideas to classroom-ready materials in seconds | Activity & lesson creation |
| Canva for Education | Turn lesson materials into classroom-ready designs and interactive experiences | Design & visual materials |
| Coteach | Create high-quality math diagrams grounded in K-12 curriculum | Math visuals |
| Diffit | Create and adapt instructional materials for every student | Adapting materials |
| Eedi | Generate diagnostic questions that reveal student thinking (English & Spanish) | Diagnostic assessment |
| MagicSchool | Make instructional content classroom-ready | Finishing content |
| Snorkl | Insights about classes, assignments, and student progress to inform instruction | Progress insight |
| TeachFX | Personalized instructional feedback grounded in real classroom talk | Teacher feedback |
Read down the "where it fits" column and you can see the arc of a teacher's actual work — plan, create, adapt, design, assess, diagnose, review, reflect. The directory isn't a random pile of integrations; it's coverage of the workflow.
Composition is the whole point
Any one of these connectors is available as a standalone product elsewhere. What the directory changes is that they stop being islands. Because Claude sits in the middle, holding your standards and your curriculum, the output of one connector can become the input to the next without you carrying it by hand.
Picture a single planning session. Claude, grounded in the Learning Commons standards graph, drafts a standards-aligned lesson. You reach for Coteach when it needs a clean math diagram, Canva when a handout should look like a real classroom design, Diffit when the same content has to reach every learner, MagicSchool to make the final materials classroom-ready. Then Eedi generates the diagnostic exit ticket, Snorkl surfaces how the class did, and TeachFX grounds feedback on how you ran the discussion. That is nine tools' worth of work in one conversation — and crucially, each step inherits the standards-alignment of the step before it, instead of resetting to a blank, context-free prompt in yet another tab.
The edtech problem was never too few tools. It was that the teacher had to be the integration layer, carrying context between apps by hand. A connector directory moves that integration burden into the software, where it belongs.
Why the directory is a public good, not just a feature
There's a bigger frame worth naming. The connector directory is one of the public goods Anthropic is shipping alongside Claude for Teachers, in the same spirit as the open-source teaching skills and the published write-up of how those skills were evaluated. Opening a directory of K-12 connectors — rather than building a walled set of first-party features — is a bet on an ecosystem: existing edtech companies keep doing what they're best at, and Claude becomes the connective tissue that makes their tools compose.
That bet extends past the tools. Anthropic has pointed at Playlab supporting a national network of lab schools, helping educators become builders of classroom AI rather than only users — the same open, ecosystem-first instinct one level up. The connector directory and teacher-as-builder are two expressions of one idea: the future of classroom AI is a network of interoperable pieces, not a single monolith. You can see the same logic in the marketplace's own education agent skills and lesson-plan studio — composable pieces meant to be assembled, not a one-size app.
What it means for how you build your stack
Practically, the directory changes how you should think about adopting tools. You're no longer choosing one app and living inside it. You're assembling a stack of specialized connectors around a common grounding — your standards, your curriculum, your class context — and letting Claude move work between them. The right mental model isn't "which single tool replaces my workflow" but "which connectors cover the steps my workflow already has."
Start from the workflow, not the tool. Map your week — plan, create, adapt, assess, review — and turn on the connectors that cover each step. Because they all share the same standards-grounded conversation, adding one doesn't fragment your process the way adding the eleventh browser tab used to. That's the promise the directory is built to keep: more capability, less fragmentation.
Want to go deeper on how the grounding layer works? Read the Learning Commons Knowledge Graph explainer, start with the series hub, or browse more builder insights.
Part of the Claude for Teachers series. Related: MagicSchool + Claude: Making Instructional Content Classroom-Ready · The Learning Commons Knowledge Graph Connector, Explained. Browse AI tutoring skills or more builder insights.