E2E Networks Cloud & TIR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| E2E_API_KEY | No | Your E2E API Key from MyAccount → Security / API Tokens | |
| E2E_LOCATION | No | Default location, e.g. DEL-1 or NCR-1 | |
| E2E_AUTH_TOKEN | No | Your E2E Auth Token (Bearer token) | |
| E2E_PROJECT_ID | No | Your E2E Project ID |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| e2e_list_nodesB | List all compute nodes (virtual machines and GPU instances) in your E2E Cloud project, including status, IP addresses, plans, and regions. |
| e2e_get_nodeA | Get detailed information about a specific compute node by its ID (specs, status, public/private IPs, attached disks, security groups). |
| e2e_create_nodeC | Launch and provision a new compute node or GPU instance on E2E Cloud. |
| e2e_node_actionC | Execute a lifecycle action on a compute node: power_off, power_on, reboot, reinstall, save_images, rename, lock, or unlock. |
| e2e_delete_nodeA | Terminate and delete a compute node from E2E Cloud. Warning: This permanently removes the node and its local disk. |
| e2e_list_plansB | List available compute plans, GPU instances, CPU/RAM configurations, and pricing options. |
| e2e_list_os_imagesB | List available OS categories, distributions (Ubuntu, Debian, CentOS, AlmaLinux, Windows), and version templates. |
| e2e_get_node_healthB | Retrieve server health information and metrics (CPU utilization, memory usage, disk space) for a node. |
| e2e_list_volumesA | List all block storage volumes in your E2E Cloud project (size, IOPS, attached node status, filesystem). |
| e2e_create_volumeC | Create an independent block storage volume on E2E Cloud. |
| e2e_attach_volumeC | Attach a block storage volume to a compute node (VM). |
| e2e_detach_volumeC | Detach a block storage volume from a compute node. |
| e2e_delete_volumeA | Permanently delete an unattached block storage volume. |
| e2e_list_bucketsB | List all EOS (E2E Object Storage) S3-compatible buckets in your account. |
| e2e_create_bucketC | Create an EOS (E2E Object Storage) bucket. |
| e2e_delete_bucketA | Delete an EOS object storage bucket. The bucket must be empty before deletion. |
| e2e_list_sfsC | List all SFS (Shared File System / Elastic File Storage) instances. |
| e2e_list_vpcsB | List all Virtual Private Clouds (VPCs) in your E2E Cloud project. |
| e2e_create_vpcC | Create a new Virtual Private Cloud (VPC) network. |
| e2e_delete_vpcC | Delete a VPC network by its network ID. |
| e2e_list_reserved_ipsC | List all reserved (static public) IP addresses in your project. |
| e2e_action_reserved_ipC | Attach, detach, or live-reserve a static public IP to/from a compute node or load balancer. |
| e2e_list_security_groupsB | List security groups attached to or available for a specific compute node. |
| e2e_attach_security_groupC | Attach a security group to a compute node. |
| e2e_detach_security_groupC | Detach a security group from a compute node. |
| e2e_list_load_balancersC | List all managed Load Balancers (Application Load Balancers and Network Load Balancers) in your project. |
| e2e_list_databasesA | List all managed database clusters (DBaaS) in your project (MySQL, PostgreSQL, MariaDB, Kafka, Valkey, OpenSearch). |
| e2e_get_databaseB | Get detailed information, topology, connection endpoints, and health of a managed database cluster. |
| e2e_create_databaseC | Provision a managed database cluster (MySQL, PostgreSQL, etc.). |
| e2e_database_actionC | Execute a control action (start, stop, restart) on a managed database cluster. |
| e2e_list_database_plansB | List available DBaaS database sizing plans, engine versions, and pricing. |
| e2e_list_k8s_clustersB | List all managed Kubernetes clusters in your E2E Cloud project. |
| e2e_get_k8s_clusterC | Get detailed information about a managed Kubernetes cluster by its service ID. |
| e2e_list_k8s_node_poolsC | List all node pools attached to a managed Kubernetes cluster. |
| e2e_tir_list_notebooksC | List all AI Labs and Jupyter notebook instances in E2E TIR (AI/ML platform). |
| e2e_tir_create_notebookC | Provision an AI Lab instance with GPU acceleration (PyTorch, TensorFlow, vLLM, etc.) in E2E TIR. |
| e2e_tir_notebook_actionC | Execute a control action (start, stop, reboot, attach_reserve_ip) on an AI Lab notebook instance. |
| e2e_tir_list_gpu_skusA | List available NVIDIA GPU hardware SKUs on E2E TIR (H100, A100, L40S, A40, A30, L4, V100, T4) with pricing and specs. |
| e2e_tir_list_model_endpointsB | List deployed model inference endpoints in E2E TIR (e.g., vLLM or HuggingFace endpoints). |
| e2e_tir_list_datasetsC | List all datasets stored in E2E TIR for AI/ML training and fine-tuning. |
| e2e_tir_list_training_clustersB | List managed Slurm / distributed GPU training clusters in E2E TIR. |
| e2e_list_projectsC | List all available IAM projects and access control scopes in your E2E Cloud account. |
| e2e_get_billing_summaryC | Get estimated monthly usage, prepaid credits balance, or billing summary. |
| e2e_test_connectionA | Verify that the MCP server can authenticate and connect to the E2E Networks Cloud REST API. |
| e2e_configure_credentialsA | Configure E2E Networks API credentials in ~/.e2e/credentials and ~/.e2e/config. Allows any AI assistant (Google Antigravity, Claude, Cursor, Codex) to set up or update API credentials directly. location and project_id are optional and should be omitted to allow searching across all projects and locations. |
| e2e_raw_requestA | Execute a direct, authenticated HTTP request against ANY E2E Networks Cloud REST API endpoint (MyAccount or TIR AI platform). Automatically handles authentication (API key + Bearer token), project scoping, and error normalization. Consult the E2E API docs (https://docs.e2enetworks.com/api/myaccount/ or https://docs.e2enetworks.com/api/tir/) for specific path structures. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| e2e-status | |
| e2e-architecture |
TDQS
Scored across 46 tools
Most tools target a distinct resource+action (nodes, databases, k8s, volumes, buckets, VPCs, reserved IPs, TIR notebooks), so selection is generally clear. Minor overlap exists between e2e_get_node and e2e_get_node_health, and the catch-all e2e_raw_request could in principle shadow every other tool, but the descriptions keep boundaries readable.
Nearly all names follow an e2e_ prefix with a predictable verb_noun pattern (list_nodes, get_node, create_volume, delete_bucket), plus a consistent e2e_tir_ namespace for AI tools. A few names invert to noun_action (e2e_node_action, e2e_database_action, e2e_action_reserved_ip), a minor deviation but still predictable.
46 tools is heavy by count (normally warranting a low score), but the server spans a genuinely large cloud domain (compute, networking, storage, DBaaS, k8s, billing, and a full AI/ML platform). Spread across these services it is roughly 4-5 tools each, so it is borderline rather than excessive.
Several domains are read-only with no lifecycle operations: load balancers, security groups, k8s clusters, and SFS offer only list/get with no create/delete. Compute and database flows are well covered, and the e2e_raw_request escape hatch plus credential/connection tools mitigate the gaps, but the surface is uneven.