- Doc
- CS-02
- Employer
- i2c Inc.
- Role
- Design and build
- Status
- In use
Multi-Manager: from SFTP client to AI tooling hub
A desktop app that restored server access after off-the-shelf clients stopped working, then gave AI assistants controlled access to servers, Jira, Confluence, Bitbucket and TeamCity through MCP.
- Java
- JavaFX
- SSH
- SFTP
- MCP
Context
Engineers reach servers through a non-standard authentication flow that is required for compliance.
Problem
After a security change, WinSCP and other off-the-shelf clients no longer worked with that flow. Every file transfer and server task had to be done by hand over SSH from the command line.
Approach
Version 1: SFTP Manager
A JavaFX desktop app with SSH and SFTP sessions built around the required authentication flow. It brought back a graphical workflow for file transfer and server access.
Version 2: server access for AI assistants
I wrote MCP servers so that AI assistants such as Claude could work on the database, web and QA servers through the same controlled sessions that engineers use.
Version 3: Multi-Manager
I added MCP integrations for self-hosted Jira, Confluence, Bitbucket and TeamCity. At the time, the official Atlassian integrations did not support the Data Center editions. The app now hosts a plugin that bundles several tools and skills so they work as one workflow, so I renamed it Multi-Manager.
Architecture
Stack
- Java
- JavaFX
- SSH
- SFTP
- MCP
What I learned
- A small tool that removes a daily problem is a good base to extend. Each later feature reused the same sessions.
- AI access to servers should go through the same controlled sessions that engineers use, never around them.