Auto-discovered marketplace from stevekinney/lesson-plan-adapter
npx claudepluginhub stevekinney/lesson-plan-adapterAdapts K-12 lesson plans to classroom learning needs using the UDL framework. Connects to a deployed Lesson Plan Adapter MCP server.
stevekinneyLesson Plan Adapter is a hosted MCP integration for K-12 teachers who use Claude and want classroom-ready adaptations grounded in Universal Design for Learning. The core interaction is intentionally simple: a teacher defines their classroom profile once, then reuses it whenever they paste a lesson plan. That persistent context changes the entire quality of the assistance. Instead of generic “differentiate for ELLs” advice, the system can generate activity-specific options tied to the teacher's grade band, subject, time block, device constraints, and the UDL-aligned learning needs they selected. It is designed to produce concrete choices a teacher can implement immediately, while also making the reasoning visible so the teacher learns the pattern, not just the answer.
Available across Claude web, desktop, and mobile via a hosted MCP server with OAuth authentication.
Under the hood, this is a remote MCP server with persistence, not a prompt in a trench coat. The system stores a single learning profile per user and uses it as durable context across Claude sessions, which is what makes the adaptations consistent and meaningfully personalized over time. That same persistence layer also stores adaptation summaries and teacher reflections, so the assistant can avoid repeating strategies that didn't work and reinforce patterns that did. Continuity is a product feature here, not just a technical detail.
The implementation is a Bun and Turbo monorepo with three main layers. The web application is a SvelteKit app that handles authentication UI, Google sign-in, OAuth endpoints, and the MCP HTTP transport. The MCP package contains the server logic, including tools, resources, prompts, the UDL taxonomy, and orchestration instructions that guide Claude through setup, adaptation, and deep-dive flows. The database package provides the Drizzle schema, migrations, and shared database client, with the data model covering auth and session tables, OAuth client and token records, MCP session tracking, the persistent profile, saved adaptations, and reflection entries tied to those adaptations.
The MCP surface area is deliberately shaped around a teacher workflow rather than a grab bag of endpoints. Profile tools manage the persistent classroom context, workflow tools save and retrieve adaptations and reflections, and follow-up tools generate materials or simplify text when a teacher wants to implement a specific strategy. Resources expose the current user and profile state so Claude can reason consistently, and prompts enforce structured flows so the system stays predictable and safe.
Security and privacy are treated as baseline requirements, not optional polish. OAuth uses authorization code flow with PKCE, redirect URIs are checked strictly, tokens are hashed at rest, and MCP sessions are scoped per user and evicted after inactivity. The privacy posture is classroom-level only, with explicit instructions not to store or repeat student names and to sanitize reflection inputs so teachers don't accidentally turn their notes into a data leak.
Once the server is deployed, any teacher can connect it from Claude's settings:
https://your-deployed-url.example.com/mcp).To adapt a lesson plan, paste it into the conversation and ask Claude to adapt it for your classroom.
The examples/ directory contains lesson plans you can paste directly into a conversation to try the adapter:
RuFlo Marketplace: Claude Code native agents, swarms, workers, and MCP tools for continuous software engineering
No description available.
Code intelligence powered by a knowledge graph — execution flows, blast radius, and semantic search