Everything you need to drive alinaflow from outside the app: keys scoped to what a caller may do, an MCP server so an AI agent can operate the workspace on your behalf, and the full REST reference.
How to get started with the Developer Portal
The Developer Portal is for connecting other software to your school: your own scripts, an integration your web developer builds, or an AI agent such as Claude or ChatGPT through MCP. Create a key in API / MCP, paste it into the tool you are connecting, and it acts with your own role, so it can never do more than you can. Revoke it there whenever it is no longer needed.
alinaflow has four portals, each for a different reader. The Enrollment Portal is public, for people who are not with you yet. The Family Portal is where the families you teach sign in. The Teacher Portal is where your teachers run their day. The Developer Portal is for connecting other software and AI agents to your school. The first three share one link: a visitor sees your Enrollment Portal, and a family or a teacher who signs in sees their own Portal.
API / MCP
Programmatic access to your school
Create API keys to connect Claude, ChatGPT, or any MCP client to your school, or to call the alinaflow API directly. Keys are personal: they act with your own role, so they can never do more than you can, and you can revoke them anytime.
The API / MCP screen in alinaflow
Keys for programmatic access, including the MCP server that lets other AI agents operate your workspace. A key carries exactly the role of the person it belongs to and can never exceed it, so a Viewer key is refused on every write. Issue keys scoped to the access you would give a person doing the same job, and revoke them here when they are no longer needed.
Sections of this screen
This screen is divided into sections: New key. Each is part of the same screen rather than a separate page.
New key
Give the key a name that says where it will be used, such as "Claude on my laptop" or "Zapier sync". That way you can tell your keys apart later and revoke the right one. The expiry date is optional, but it's worth setting one for a short test or a key you're handing to a contractor. The key acts with your own role, so if your role changes or your account is deactivated, the key stops working too.
New key tab
Key fields
API keys - Personal tokens for programmatic access. Create one, copy it once (it is shown a single time), then paste it into your client. Revoke it anytime.
Role - A key acts with your current role and location access, so it can never do more than you can. If your role changes, the key follows.
Deactivation - If your account is deactivated, every key you own stops working immediately.
MCP server - Point Claude, ChatGPT, or any MCP client at the MCP URL and authenticate with a key to let it read and write your school's data on your behalf.
API documentation - Every endpoint with its description and required role. Download the OpenAPI spec (MCP or v1) to generate a client.
API documentation
The full REST reference: every endpoint, its parameters and its responses, with the schemas generated from the API itself so they never drift.
