tapestry-mcp

Unofficial, read-only MCP server for the Tapestry learning journal (tapestryjournal.com, Android com.fsf.tapestry), for parents and carers.

Tapestry has no public API. This logs in with your own email and password and calls the same internal /api/4/… endpoints the web app uses (found via tapestry-scraper). It may break if Tapestry changes their web app. Accounts using 2FA or SSO-only login aren't supported.

Tools

Related MCP server: librus-mcp

Add to Frona

Settings → MCP → Custom → Local package

Other MCP clients

{
  "mcpServers": {
    "tapestry": {
      "command": "npx",
      "args": ["-y", "github:Mpercy-Git/tapestry-mcp"],
      "env": { "TAPESTRY_EMAIL": "you@example.com", "TAPESTRY_PASSWORD": "…" }
    }
  }
}

Troubleshooting login

• Use the variable names exactly: TAPESTRY_EMAIL (or TAPESTRY_USERNAME) and TAPESTRY_PASSWORD. The value is the email address you sign in to tapestryjournal.com with — check it works in a browser first.

• Accounts linked to more than one school land on a "select school" page after login; the server picks the first school, or the one named in TAPESTRY_SCHOOL (part of its name, or the slug from /s/<slug>/ in the web address). The server log lists the schools it found.

• Accounts that sign in with Google/Microsoft only, or that need a 2FA code, can't be used.

• Add TAPESTRY_DEBUG=1 to the env to log each login step (status codes, URLs, form field names — never the password) to the server's stderr.

• The error message says which step failed: unreachable host, HTTP 419/429, a 2FA prompt, or back on the login page.

Notes

• Session cookies are only sent to tapestryjournal.com; media on other hosts (CDN) is fetched without them.

• If a field comes back empty, call get_observation with include_raw: true and adjust the mapping in src/server.js.

Dev

npm install && npm test

Requires Node 20+. No build step — plain ES modules, so installing straight from GitHub works.

Releasing

Bump version in package.json and in server.json (top-level and under packages), then merge to main. The Release workflow runs the tests, tags v<version> and publishes a GitHub release with the npm pack tarball attached. Pushes that don't change the version are a no-op; it can also be run by hand from the Actions tab.