Developer Tools
termal.in
A cross-platform SSH client with tabbed terminal, SFTP, and MCP support for AI agents to access remote hosts.
ENDPOINT 1
https://termal.in/api/v1/mcp
MCP server metadata
- Name
- termalin
- Version
- 0.1.0
Manage the user's servers through Termalin: hosts_list shows the reachable servers, ssh_exec runs a command, sftp_list/read/write handle files. Servers are reached keylessly through the user's Termalin Connectors.
Known tools 8
generate_passwordGenerate a strong random password — handy when creating a user or setting a password on a server.
Inferred read-onlyssh_execRun a single shell command on one of your servers and return its combined output.
Potential side effectssftp_readRead a text file from one of your servers over SFTP and return its contents.
Inferred read-onlydata_tablesList the tables / collections / keys of a database on one of your servers — passwordless, over the same local-client path as data_query.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.termalin]
url = "https://termal.in/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"termalin": {
"type": "http",
"url": "https://termal.in/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: termalin
Remote MCP URL: https://termal.in/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"termalin": {
"url": "https://termal.in/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"termalin": {
"type": "http",
"url": "https://termal.in/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "termalin",
"transport": "streamable-http",
"url": "https://termal.in/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.