MagicSchool AI

Save lesson plans and materials into your MagicSchool Resource Library.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the MagicSchool AI connector does

The MagicSchool MCP server saves teaching content from Claude, ChatGPT or any MCP agent into a teacher's MagicSchool Resource Library. It is deliberately one-way: a single write tool imports lesson plans, activities and planning notes, and MagicSchool states the connector cannot read, search or export anything already in the platform.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

MagicSchool AI tools (1)

  • import_document_to_resource_library

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • MagicSchool publishes no tool list. Its help article describes what the connector does in prose but never names a tool, so the one name comes from Anthropic's directory. There is no second enumeration to diff against — that is a weaker position than a clean diff, and the difference matters. What MagicSchool does publish is a negative enumeration: an explicit list of what the connector cannot do, which is unusual and is the strongest boundary evidence here.
  • We could not read the tool's schema or annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here and the read/write classification is ours from the name.
  • No scope separates anything. The resource descriptor advertises only openid, email and profile; the authorization server adds phone and offline_access. All are identity claims. With one write tool the practical consequence is small, but nothing at consent constrains the connector — the constraint is the tool surface itself.
  • It is import-only, which is the point and also the ceiling. You cannot search your Resource Library, pull a saved rubric into the conversation, or check whether an import already exists. Every session starts blind to what MagicSchool already holds.
  • Nothing stops a teacher importing content about a named student. The connector reaches no student records, but it writes whatever document it is handed. Where a conversation contains identifiable student work or a behaviour note, importing it puts that into MagicSchool.
  • Availability is an admin switch you may not control. MagicSchool states organizations decide whether the connector is available and can disable it later. Individual teachers cannot enable it themselves.
  • No rate limits are published. MagicSchool's connector documentation states none, and we did not test.
  • Duplicate imports are not addressed. MagicSchool's troubleshooting advises retrying a failed import, and does not say whether a retry after a timeout creates a second Resource Library item. Assume it can, and check the library rather than retrying blindly.
  • MagicSchool disclaims the upstream half. Its documentation notes the third-party application is not operated by MagicSchool and that MagicSchool does not control how content is handled before import. The privacy posture of the conversation the content came from is your agent vendor's, not MagicSchool's.

Frequently asked questions

Can the MagicSchool connector read student data?

No, and MagicSchool commits to that in writing. Its connector help article states the connector cannot access student data, rosters, classroom data, LMS or SIS data, or district knowledge. The single tool the directory lists imports a document; nothing in the listing reads, searches or exports anything. The commitment is a vendor statement, not something an outside probe can confirm.

How many tools does the MagicSchool MCP server have?

Anthropic's directory lists exactly one, and it reaches one operation. The name is import_document_to_resource_library, which imports a document into your MagicSchool Resource Library. It takes no service, action or endpoint selector, so it does not dispatch to a wider API the way one-tool connectors sometimes do. MagicSchool publishes no tool list of its own to check that against.

Does the MagicSchool connector work with the dozens of MagicSchool teacher tools?

No. MagicSchool markets a large catalogue of AI generators for teachers, and the connector reaches none of them. MagicSchool's help article states the connector does not use Raina, MagicSchool tools, or MagicSchool AI providers to generate content. Content is generated by your AI agent and then saved into MagicSchool, so the platform's tool catalogue stays out of reach.

What OAuth permissions does the MagicSchool MCP server request?

Only identity claims. MagicSchool's RFC 9728 resource descriptor declared openid, email and profile on 2026-08-22, and its authorization server adds phone and offline_access. None of those narrows what the connector can do. The boundary here comes from the tool surface being a single import, and from your organization's admin switch, not from scope selection at consent.

Can the connector delete or overwrite my MagicSchool resources?

No tool in the listing deletes or updates anything. The single tool imports content as a new Resource Library item, and MagicSchool describes deletion as an action inside MagicSchool with its own confirmation prompt. So the connector's worst case is unwanted new items in your library, which you remove yourself. Nothing existing is modified.

Why can't I see MagicSchool as a connector in Claude?

Your school or district has not enabled it. MagicSchool states the connector is available only if your organization has turned it on, and tells users who cannot see or connect to it to contact their MagicSchool administrator. The same admin control works in reverse: an organization can disable connector access later, which disconnects it for everyone.

Is MagicSchool FERPA and COPPA compliant?

MagicSchool holds independent certifications for both. Its trust page names iKeepSafe FERPA certification, iKeepSafe COPPA Safe Harbor certification, SOC 2 Type II attestation and 1EdTech TrustEd Apps certification. Those cover the MagicSchool platform, which does process student data as a school service provider. The connector is scoped away from that data by MagicSchool's own description.

What happens to content I send into MagicSchool?

It becomes a new Resource Library item you can open and edit. MagicSchool states imported content is stored under its normal retention and privacy policies, the same as content you save manually. MagicSchool also notes it does not control how your AI agent handled that content before import, so the agent's own policies govern everything upstream of the save.

Sources

More Data & Research connectors

  • Airfield Directory

    Look up airfields, landing fees, fuel prices, pilot reports and METAR/TAF from an AI agent.

  • Airtable

    Read, write and restructure Airtable bases from your AI assistant.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put MagicSchool AI to work.

Connect MagicSchool AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.