Homeroom

io.github.mattmacrocketPublished by GitHub account mattmacrocketv0.1.0-devUpdated Oct 26, 2026

Homeschool planning with private child selection and parent-reviewed curriculum and record drafts.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote Homeroom MCP server for homeschool planning, letting an assistant draft curriculum and records with private child selection and parent review.

What you can do
  • Draft curriculum plans for a homeschool program.
  • Create record drafts that a parent reviews before use.
  • Select which child a plan or record applies to, with private child selection.
  • No individual tools are listed, so exact operations are not documented.
When to use it
Useful for homeschooling parents who want an assistant to help draft curriculum and record entries while keeping child selection private and leaving final approval to the parent.
Requirements
A remote endpoint at homeroom.academy over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
It handles children's personal and educational data, so review what is shared with the service. Drafts are meant for parent review, but check anything before accepting it into records.

Installation

In SourceWeft

  1. Open Homeroom in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mattmacrocket%2Fhomeroom/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "homeroom": {
      "type": "http",
      "url": "https://homeroom.academy/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0-devLatestOct 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.