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.
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.
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.