Ofw MCP Server

OurFamilyWizard MCP

A Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.

[!WARNING] AI-developed project. This codebase was entirely built and is actively maintained by Claude Sonnet 4.6. No human has audited the implementation. Review all code and tool permissions before use.

What you can do

Ask Claude things like:

• "Show me my recent OFW messages"
• "What's on the kids' calendar next week?"
• "List recent expenses and tell me what I owe"
• "Add a journal entry about today's pickup"
• "Draft a reply to the last message from my co-parent"

Requirements

• Claude Desktop
• Node.js 18 or later
• An active OurFamilyWizard account

Installation

1. Clone and build

git clone https://github.com/chrischall/ofw-mcp.git
cd ofw-mcp
npm install
npm run build

2. Add to Claude Desktop

Edit your Claude Desktop config file:

• Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the ofw entry inside "mcpServers" (create the key if it doesn't exist):

{
  "mcpServers": {
    "ofw": {
      "command": "node",
      "args": ["/absolute/path/to/ofw-mcp/dist/index.js"],
      "env": {
        "OFW_USERNAME": "your-email@example.com",
        "OFW_PASSWORD": "your-ofw-password"
      }
    }
  }
}

Replace /absolute/path/to/ofw-mcp with the actual path where you cloned the repo. On Mac, run pwd inside the cloned directory to get it.

3. Restart Claude Desktop

Quit completely (Cmd+Q on Mac, not just close the window) and relaunch.

4. Verify

Ask Claude: "What does my OFW dashboard look like?" — it should show your unread message count, upcoming events, and outstanding expenses.

Credentials

Credentials are read from environment variables, with two ways to provide them:

Option A — env block in Claude Desktop config (shown above, recommended):

"env": {
  "OFW_USERNAME": "your-email@example.com",
  "OFW_PASSWORD": "your-ofw-password"
}

Option B — .env file in the project directory:

cp .env.example .env
# edit .env and fill in your credentials

Environment variables always take priority over the .env file. You can also pass them directly on the command line:

OFW_USERNAME=you@example.com OFW_PASSWORD=yourpass node dist/index.js

Available tools

Read-only tools run automatically. Write tools ask for your confirmation first.

Troubleshooting

"0 messages" — Claude may have read the notification counts rather than the actual messages. Ask explicitly: "List the messages in my OFW inbox" or "Use ofw_list_message_folders then ofw_list_messages".

"OFW_USERNAME and OFW_PASSWORD must be set" — credentials are missing. Check the env block in your Claude Desktop config or your .env file.

403 Forbidden — wrong credentials. Verify your username/password at ofw.ourfamilywizard.com.

Tools not appearing in Claude — go to Claude Desktop → Settings → Developer to see connected servers and any error output. Make sure you fully quit and relaunched after editing the config.

Can't find the config file on Mac — in Finder press Cmd+Shift+G and paste ~/Library/Application Support/Claude/.

Security

• Credentials live only in your local config file or .env
• They are passed to the server as environment variables and never logged
• The server authenticates with OFW using the same login flow as the web app
• Use a strong, unique OFW password

Development

npm test        # run the test suite
npm run build   # compile TypeScript → dist/

Project structure

src/
  client.ts       OFW auth and HTTP client
  index.ts        MCP server entry point
  tools/
    user.ts       ofw_get_profile, ofw_get_notifications
    messages.ts   folders, list, get, send
    calendar.ts   list, create, update, delete events
    expenses.ts   totals, list, create
    journal.ts    list, create entries
tests/
  client.test.ts
  tools/

Auth flow

OFW uses Spring Security form login:

1. GET /ofw/login.form — establishes a session cookie
2. POST /ofw/login — submits credentials, returns { auth: "<token>" }
3. All API calls use Authorization: Bearer <token>
4. On 401, re-authenticates automatically and retries once

Tokens are cached for 6 hours.

License

MIT