ipasen-mcp

Unofficial MCP server for iPasen, the school-tracking platform for families in Andalusia, Spain (Séneca, Junta de Andalucía). It lets an AI assistant (Claude Code, Claude Desktop, OpenCode, OpenClaw…) check grades, absences, timetable, school messages, trips and the school calendar, and — with explicit human confirmation — report or justify absences, answer authorizations, reply to teachers, book parent-teacher meetings, etc.

Disclaimer

This project is not affiliated with, endorsed by or supported by the Junta de Andalucía. It is an independent client written for interoperability: it uses the same public HTTPS API as the official iPasen mobile app and contains no code, keys or assets from that app. Each user logs in with their own iPasen account to access their own family's data. Use it at your own risk and responsibility, and in line with the platform's terms of use. The API may change or be blocked at any time.

Contents: Features · Installation · Usage · Actions and confirmation · Tool reference · Troubleshooting · How it works

Features

• 37 read-only tools: daily overview, grades from the teacher's gradebook (with the mark of each assessment criterion), term grades, timetable, absences, school messages, upcoming events, school calendar, tutor and office hours, trip authorizations, lunch/after-school services…

• 16 actions: report/justify absences, answer trip authorizations, sign or decline documents, reply to or write to teachers, book/cancel meetings, mark messages, manage the people allowed to pick children up. Every action is a two-step preview → confirm call.

• Safe for autonomous agents: optional Telegram confirmation — the code goes to the human's phone and the agent never sees it.

• Children are selected by first name (child="Ana"); the messages the school sends once per child are merged into one.

• Two-factor authentication with trusted devices; several accounts (e.g. both parents) side by side.

• MCP tool annotations: queries are readOnlyHint, irreversible actions destructiveHint.

• Digest for scheduled jobs (school_digest + mark_digested): each school message is seen once, e.g. to turn it into tasks and calendar events.

• OpenClaw installer that your OpenClaw agent can run by itself.

Related MCP server: EduPage MCP Server

Installation

Requirements

• Python 3.10+

• An iPasen family account (the username and password you use in the iPasen app)

• Outbound HTTPS to seneca.juntadeandalucia.es (and api.telegram.org if you use Telegram confirmation)

OpenClaw (easiest: let your agent do it)

Send this to your OpenClaw assistant:

Install the iPasen MCP for me following https://github.com/boraita/ipasen_mcp/blob/main/clients/openclaw/INSTALL.md — read it entirely before running anything, and ask me whatever you need.

It will ask for your iPasen login, whether you want actions or only queries, and (for actions) your Telegram chat id. Or run the installer yourself on the OpenClaw host:

mkdir -p ~/mcp && cd ~/mcp
curl -fsSLO https://raw.githubusercontent.com/boraita/ipasen_mcp/main/clients/openclaw/install.py

# queries only
IPASEN_USER='your_user' IPASEN_PASSWORD='your_password' python3 install.py --agent main

# queries + actions confirmed by a code sent to your Telegram
IPASEN_USER='your_user' IPASEN_PASSWORD='your_password' python3 install.py --agent main --telegram-chat-id 123456789

The installer downloads the server, creates the virtualenv, stores secrets in ~/.config/ipasen-mcp/<name>/credentials.env (mode 600, never in openclaw.json), registers the server, grants it to the agent, writes a skill with your family's data, and probes it (39 tools read-only, 55 tools with actions). Re-run it to update. Details and options: clients/openclaw/INSTALL.md.

Claude Code, Claude Desktop, OpenCode

1. Get the code and create a virtualenv

git clone https://github.com/boraita/ipasen_mcp.git ~/ipasen_mcp && cd ~/ipasen_mcp
python3 -m venv venv && venv/bin/pip install -r requirements.txt
# if `python3 -m venv` fails (no ensurepip, e.g. minimal Debian/Ubuntu), use uv:
# uv venv --python 3.12 venv && VIRTUAL_ENV=$PWD/venv uv pip install -r requirements.txt

2. Store your credentials in a private file (keeps the password out of client configs, which get copied into backups and logs):

mkdir -p ~/.config/ipasen-mcp && chmod 700 ~/.config/ipasen-mcp
umask 077; cat > ~/.config/ipasen-mcp/credentials.env <<'EOF'
IPASEN_USER=your_user
IPASEN_PASSWORD=your_password
EOF

3. Check the login

cd ~/ipasen_mcp && venv/bin/python -c "import server; print(server.login()); print(server.children())"

You should see {'ok': True} and your children. If it says two_factor_required, see Two-factor authentication.

4. Register the server in your client

Claude Code

claude mcp add ipasen-mcp -s user -- ~/ipasen_mcp/venv/bin/python ~/ipasen_mcp/server.py

Claude Desktop — claude_desktop_config.json (Settings → Developer → Edit config):

{
  "mcpServers": {
    "ipasen": {
      "command": "/Users/YOU/ipasen_mcp/venv/bin/python",
      "args": ["/Users/YOU/ipasen_mcp/server.py"]
    }
  }
}

OpenCode — ~/.config/opencode/config.json:

"mcp": {
  "ipasen": {
    "type": "local",
    "command": ["/home/YOU/ipasen_mcp/venv/bin/python", "/home/YOU/ipasen_mcp/server.py"],
    "enabled": true
  }
}

Any other MCP client: stdio transport, command <repo>/venv/bin/python <repo>/server.py.

Restart the client and ask "What's new at school?".

Configuration

Settings are read from the server's environment first, then from the credentials file:

Two-factor authentication

If your account uses 2FA, ask the assistant to log in: it calls login(), iPasen sends you a code, you give it to the assistant, and it calls login(code="123456"). With the default trust_device=True the code is not asked again on that machine.

Several accounts (e.g. both parents)

Run one server per account with its own files, and register each under a different name:

claude mcp add ipasen-partner -s user \
  -e IPASEN_CREDENTIALS_FILE=$HOME/.config/ipasen-mcp/partner/credentials.env \
  -e IPASEN_STATE_FILE=$HOME/.config/ipasen-mcp/partner/session.json \
  -- ~/ipasen_mcp/venv/bin/python ~/ipasen_mcp/server.py

In OpenClaw: install.py --name ipasen_partner --agent partner --deny-agent main ….

Updating and uninstalling

• Update: cd ~/ipasen_mcp && git pull && venv/bin/pip install -r requirements.txt, then restart the client. OpenClaw: re-run install.py with the same options.

• Uninstall: remove it from the client (claude mcp remove ipasen-mcp -s user), then delete ~/ipasen_mcp and ~/.config/ipasen-mcp. OpenClaw: python3 install.py --uninstall --purge.

Usage

Just talk to your assistant. Examples:

Tips:

• Start with children or overview; every other tool takes child="<first name>" (case/accent-insensitive) or nothing for all children.

• Data from the school (subjects, weekdays, absence reasons) comes in Spanish; the assistant answers in your language.

• Dates for actions are dd/mm/yyyy.

Actions and confirmation

Actions send something real to the school. Each one is called twice:

1. Without confirm_code → nothing is sent. The response is "status": "PREVIEW — nothing has been sent" with exactly what would be sent (student, dates, time slots, recipients, text).

2. With the same arguments plus confirm_code → it is sent ("status": "SENT").

The code is bound to the exact request: if anything changes, it is rejected and a new preview is needed. Invalid data (unknown id, wrong date, ambiguous recipient, two children when one is required…) returns "REJECTED — nothing has been sent" with the reason.

Where the code comes from depends on IPASEN_CONFIRM_MODE:

⚠️ In inline mode an agent can confirm itself. This happened in testing: an agent previewed a message to a teacher and sent it 1.4 s later without asking. If your client does not ask you before each tool call, use telegram mode or hide the action tools.

To enable telegram mode outside OpenClaw, add to your credentials file:

IPASEN_CONFIRM_MODE=telegram
IPASEN_TELEGRAM_BOT_TOKEN=123456:ABC...   # a bot you created with @BotFather
IPASEN_TELEGRAM_CHAT_ID=123456789         # your user id; send the bot a message first

Full rules, where every id comes from, and per-action details: ACTIONS.md. Advice for keeping agents safe: CLIENTS.md.

Tool reference

Queries (read-only)

Actions (preview → confirm)

Troubleshooting

How it works

The older seneca/jsp/pasendroid/ API (used by 2021-era projects) is no longer what the app uses.

Known server quirks:

• centros/datos-centro fails when several children attend the same school (NonUniqueResultException); school_info uses the home-screen data instead.

• seguimiento/get-notas-evolucion returns 404; not exposed.

• The agenda only accepts yyyy-mm-dd dates after the start of the school year.

• mensajeria/get-conversaciones returns the whole conversation with a sender (10 per page, oldest first); read_message picks the requested message from it.

• "Administrador PASEN" notices are regenerated on every request and keep no read state.

Files

License

MIT.