Admin

Scipio Admin

The Admin application is the main hub for all all system information and a great companion for system admins & developers . It is here that you can find:

1. Server – Server & System information
   1. Memory allocation
   2. Log
   3. Cache-Settings
   4. Request-Overview
   5. Account Management
   6. List of components / applications
   7. Artifact information (List of available Screens/Requests)
2. Entity Engine – Entity (database) information
   1. Entity List
   2. Data-Editor
   3. SQL-Processor
   4. Database-Performance Tests
   5. Connection/Pool Status
   6. Scipio Utility Services (Reload-Theme-Data, Create demo-Data)
3. Service Engine – Service information
   1. Service List
   2. Job List
   3. Job Scheduler
   4. Service Scheduler
4. Label Manager – Label information
5. Geo Management – Geo location settings
6. Development – Tools & Utilities
   1. Developer Documentation
   2. Layout Demo
7. Import / Export
   1. XML Data Export
   2. XML Data Import
8. Solr – Search engine configuration – a link to the Solr user interface

The application in 4.0#

scipio-erp-admin-webtools

The administration application in 4.0: the entity engine, the service engine, the job queue and the state of the install.

Do it with an agent#

The administration application ships the six core tools. They are the ones that do not belong to a single application: they describe the install, reach any service and any entity, and say who the token is.

claude mcp add --transport http scipio-admin "https://<host>/admin/mcp" --header "Authorization: Bearer <token>"

Six tools carry the application. Every call names the tool and one action.

• scipio_apps — list, tools, call, skill_list.
• scipio_service — search, call.
• scipio_entity — find, store.
• scipio_document — search, get.
• scipio_whoami — whoami.
• scipio_admin — install_info, reload_registry, device_token_create.

Ask the install what it is#

“Which applications does this install run, and which tools may I use?”

The agent calls scipio_admin:install_info, scipio_apps:list and scipio_apps:tools. scipio_whoami answers with the user behind the token and that user’s permissions.

Reach a service that has no tool#

“Find the service that recalculates a product price and run it for MF_BIKE.”

The agent calls scipio_service:search, reads the parameters and calls scipio_service:call. This is the escape hatch: every service of the system is reachable, under the token’s permissions.

Give a shop floor tablet its own token#

“Make a token for the welding line tablet that may only work on the shop floor.”

The agent calls scipio_admin:device_token_create. The token is a user login in the SCIPIO_FLOOR group with the MANUFACTURING_FLOOR permission, so the tablet reaches the floor tools and nothing else.

The token is a user login. The agent does what that user may do, and nothing more. Every call writes one audit row. Read the security model before you hand a token out.