anylogicPLE-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALP_OUTPUT_DIR | Yes | Path where .alp files are saved | |
| ANYLOGIC_API_KEY | No | Optional API key for AnyLogic Cloud upload |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| anylogic_create_model_pleA | Create an AnyLogic simulation model that complies with PLE (Personal Learning Edition) limits. The model will be validated against PLE restrictions: max 10 agent types, max 200 blocks per agent, max 50,000 dynamic agents. Use this to create models that can be downloaded and run in free AnyLogic PLE. |
| anylogic_validate_pleA | Check if a model definition complies with AnyLogic PLE (Personal Learning Edition) limits. Returns detailed information about limit usage and any violations. |
| anylogic_upload_to_cloudA | Upload a PLE-compliant model to AnyLogic Cloud. Requires ANYLOGIC_API_KEY to be set. The model will be available for running simulations in the cloud, and source files can be downloaded for use in local AnyLogic PLE. |
| anylogic_download_for_pleB | Get download information for running model in AnyLogic PLE locally. Returns the model file and instructions for opening in free AnyLogic PLE software. |
| anylogic_get_ple_limitsB | Get information about AnyLogic PLE (Personal Learning Edition) limitations. Useful for understanding what restrictions apply when creating models. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: create, validate, get limits, download, and upload. No overlap in functionality.
All tools follow a consistent `anylogic_verb_noun` snake_case pattern, e.g., `anylogic_create_model_ple`, `anylogic_validate_ple`.
With 5 tools, the server is well-scoped for managing PLE-compliant AnyLogic models without being overwhelming or too sparse.
Covers creation, validation, limits, download, and upload. Missing update/delete functionality, but core lifecycle is present for the PLE context.