Connect an AI agent to your Montessori school: FutureNerds MCP server

Who can connect, and what they can reach

Two switches control access, and both are off when a school starts.

1. An administrator opens Settings, chooses Configure AI Access, and turns on Enable MCP Server, Enable CLI, or both. Turning a switch off later ends access for every member on that channel, and their existing keys stop working on it.
2. Each person then creates their own key. They open their profile, choose the AI Access tab, and use the Create API Keys card.

A new key asks for:

• School: the school the key works for
• Works With: MCP Server or Command Line
• Label: a name you will recognize later, such as "Laptop terminal"
• Expires On: one year from today unless you pick another date

The key is shown once. FutureNerds stores only a SHA-256 hash of it. The key list shows each key as Active, Expired or Revoked, with the last time it was used. Revoke stops a key right away, for good.

A key belongs to one person, one school and one channel. The assistant gets the same access that person has in the app. The tool list is filtered by their roles, and the database applies the same row-level security rules as the website. Destructive actions, such as deletes and payment changes, need an explicit confirmation.

Configuration for Claude and Cursor

Replace fn_YOUR_KEY with the key you copied.

Claude Code. Run this once:

claude mcp add --transport http futurenerds https://www.futurenerds.dev/api/mcp --header "Authorization: Bearer fn_YOUR_KEY"

Or add it to a project's .mcp.json:

{
  "mcpServers": {
    "futurenerds": {
      "type": "http",
      "url": "https://www.futurenerds.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer fn_YOUR_KEY"
      }
    }
  }
}

Claude Desktop. Add FutureNerds to claude_desktop_config.json through mcp-remote, a small Node.js bridge that sends the header for Claude Desktop:

{
  "mcpServers": {
    "futurenerds": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.futurenerds.dev/api/mcp",
        "--header",
        "Authorization:${FUTURENERDS_AUTH}"
      ],
      "env": {
        "FUTURENERDS_AUTH": "Bearer fn_YOUR_KEY"
      }
    }
  }
}

Cursor. Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "futurenerds": {
      "url": "https://www.futurenerds.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer fn_YOUR_KEY"
      }
    }
  }
}

The fnerds command-line tool

fnerds is the FutureNerds CLI. It calls the same tools over the same endpoint.

• Sign in with fnerds auth login, which opens a browser. A browser login counts as an MCP connection, so it needs Enable MCP Server.
• Or set FNERDS_API_KEY to a key with Works With set to Command Line. This needs Enable CLI.
• fnerds child list and fnerds attendance mark --child-id <id> --classroom-id <id> --date 2026-10-14 --status present run common actions.
• fnerds tool capabilities lists your schools, roles and tools. fnerds tool call <name> --args '{...}' runs any tool.
• --json prints JSON, and --confirm confirms a destructive action.

What it costs

FutureNerds is free for your first 10 students. After that it costs $0.50 per child per month, with no setup fee. If your school collects payments from families through FutureNerds, standard Stripe fees plus 1% apply. See pricing.