CTERA

Provides an AI-driven interface to manage CTERA Portal files and folders via MCP
  • typescript

2

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "ctera-mcp-ctera-core": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/mcp-ctera-core/src",
        "run",
        "stdio.py"
      ],
      "env": {
        "ctera.mcp.core.settings.ssl": "true",
        "ctera.mcp.core.settings.host": "your.ctera.portal.domain",
        "ctera.mcp.core.settings.user": "your-username",
        "ctera.mcp.core.settings.scope": "user",
        "ctera.mcp.core.settings.password": "your-password"
      }
    }
  }
}

You can interact with the CTERA Portal through an MCP server that translates natural language or automation intents into file management actions. This setup lets you perform operations on CTERA Portal using command-like interactions, securely configured and ready for automation.

How to use

Connect an MCP client to the CTERA MCP server and start issuing commands to manage files and folders on your CTERA Portal. You will use standard MCP interaction patterns to request actions like creating folders, uploading or listing files, and organizing data. All credentials stay securely configured in environment variables, so you don’t need to embed sensitive information in your commands.

How to install

Prerequisites: you need a runtime capable of hosting MCP servers and, for the SSE option, a running CTERA Portal instance reachable from your environment.

Step 1: Prepare the environment variables and credentials you will use to access CTERA Portal. You will supply these values during configuration.

Step 2: Install or prepare the MCP runtime if you have not already installed it on your machine or in your deployment environment.

Step 3: Choose your connection method and configure the MCP server accordingly. You can run the server as a local stdio process or expose it via HTTP/SSE as described below.

Step 4: Start the MCP server and verify it is accepting connections from your MCP client.

Additional configurations and deployment options

Two common deployment methods are provided: a local stdio-based server and an HTTP SSE-based server. You can also deploy the server with Docker for easier management and isolation.

Configuration examples

{
  "mcpServers": {
    "ctera-core-mcp-stdio": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/mcp-ctera-core/src",
        "run",
        "stdio.py"
      ],
      "env": {
        "ctera.mcp.core.settings.scope": "user",
        "ctera.mcp.core.settings.host": "your.ctera.portal.domain",
        "ctera.mcp.core.settings.user": "your-username",
        "ctera.mcp.core.settings.password": "your-password",
        "ctera.mcp.core.settings.ssl": "true"
      }
    }
  }
}

Security and credentials

All sensitive information is provided through environment variables. Do not hard-code credentials in your MCP configurations. Use secure secret management practices in your deployment environment.

Docker deployment

You can run the MCP server using Docker for portability and isolation.

docker build -t mcp-ctera-core .
docker run -p 8000:8000 \
  -e ctera.mcp.core.settings.scope=user \
  -e ctera.mcp.core.settings.host=your.ctera.portal.domain \
  -e ctera.mcp.core.settings.user=your-username \
  -e ctera.mcp.core.settings.password=your-password \
  -e ctera.mcp.core.settings.ssl=true \
  mcp-ctera-core

Available tools

fileManagement

Manage files and folders on CTERA Portal through MCP commands and AI-driven intents.

aiCommandExecution

Execute AI-driven commands that map to CTERA Portal file operations and workflows.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational