Multi-Protocol Bridge

Available ActionsEach successful request consumes credits as outlined below.

ftp_upload^5crftp_download^5crftp_list^5crftp_delete^5crssh_execute^5crmqtt_publish^5cr

Details

Protocol Bridge is an HTTP gateway that enables AI agents, automation workflows, and modern applications to interact with traditional network protocols without native protocol support. It translates simple HTTP requests into FTP, SSH, and MQTT operations, making it easy to integrate file transfers, remote command execution, and IoT messaging into any system that can make web requests. The tool supports secure connections including FTPS, SSH key authentication, and MQTTS with TLS, ensuring enterprise-grade security for sensitive operations. Connection details can be passed via intuitive URL strings or explicit parameters, giving developers flexibility in how they configure each action. Protocol Bridge is ideal for building automation pipelines, connecting legacy infrastructure to modern APIs, orchestrating DevOps tasks, and enabling large language models to perform real-world actions across diverse systems. For email sending workflows, use the dedicated SMTP Mailer tool which provides a streamlined interface specifically optimized for email delivery.

Use Cases

FTP file upload automation, FTP file download, secure FTPS file transfer, remote directory listing, automated file deletion, SSH remote command execution, server administration automation, DevOps task orchestration, IoT MQTT message publishing, sensor data transmission, smart home device control, MQTT broker integration, AI agent protocol access, LLM tool integration, workflow automation, legacy system integration, HTTP to FTP bridge, HTTP to SSH gateway, HTTP to MQTT proxy, no-code automation backend, serverless protocol access, cloud function protocol support, CI/CD pipeline integration, infrastructure automation, remote server management, file synchronization, backup automation, system monitoring automation

Connect Your Agent In 5 Min

Watch the setup guide for your platform

Or Install Locally

STDIO connector for Claude Code, Codex, Cursor, Zed, and other LLMs that require STDIO or custom connections. This lightweight connector routes requests to https://api.agentpmt.com/mcp. All tool execution happens in the cloud and the server cannot edit any files on your computer.

npm install -g @agentpmt/mcp-routeragentpmt-setup

curl -X POST "https://api.agentpmt.com/products/purchase" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ********" \
  -d '{
    "product_id": "6948d263b54506f955d789f0",
    "parameters": {
      "action": "ftp_upload",
      "url": "example_url",
      "content": "example_content",
      "content_encoding": "text"
    }
  }'

import requests
import json

url = "https://api.agentpmt.com/products/purchase"

headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer ********"
}

data = {
    "product_id": "6948d263b54506f955d789f0",
    "parameters": {
        "action": "ftp_upload",
        "url": "example_url",
        "content": "example_content",
        "content_encoding": "text"
    }
}

response = requests.post(url, headers=headers, json=data)
print(response.status_code)
print(response.json())

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "6948d263b54506f955d789f0",
  parameters: {
    "action": "ftp_upload",
    "url": "example_url",
    "content": "example_content",
    "content_encoding": "text"
  }
};

fetch(url, {
  method: "POST",
  headers,
  body: JSON.stringify(data)
})
  .then(response => response.json())
  .then(data => console.log(data))
  .catch(error => console.error("Error:", error));

const axios = require('axios');

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "6948d263b54506f955d789f0",
  parameters: {
    "action": "ftp_upload",
    "url": "example_url",
    "content": "example_content",
    "content_encoding": "text"
  }
};

axios.post(url, data, { headers })
  .then(response => {
    console.log(response.status);
    console.log(response.data);
  })
  .catch(error => {
    console.error("Error:", error.message);
  });

Login to view your API and budget keys. The example above uses placeholder values. Sign in to see personalized code with your bearer token.

This tool supports credit-based access for external agents using AgentAddress identities or standard crypto wallets. External agents should use the External Agent API to buy credits with x402 and invoke this tool.

1. Buy Credits

Purchase credits via x402 payment (500 credit minimum, 100 credits = $1).

# Request payment requirements (returns 402 + PAYMENT-REQUIRED header)
curl -i -s -X POST "https://www.agentpmt.com/api/external/credits/purchase" \
  -H "Content-Type: application/json" \
  -d '{ "wallet_address":"0xYOUR_WALLET", "credits": 500, "payment_method":"x402" }'

# Sign the EIP-3009 authorization, then retry with signature header
curl -s -X POST "https://www.agentpmt.com/api/external/credits/purchase" \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <base64-json>" \
  -d '{ "wallet_address":"0xYOUR_WALLET", "credits": 500, "payment_method":"x402" }'

2. Create a Session Nonce (nonce used in signed balance/invoke)

curl -s -X POST "https://www.agentpmt.com/api/external/auth/session" \
  -H "Content-Type: application/json" \
  -d '{ "wallet_address":"0xYOUR_WALLET" }'

3. Invoke This Tool

Sign the message with your wallet (EIP-191 personal-sign), then POST to the invoke endpoint.

# Sign this message (wallet MUST be lowercased):
# agentpmt-external
# wallet:0xyourwallet...
# session:<session_nonce>
# request:<request_id>
# action:invoke
# product:6948d263b54506f955d789f0
# payload:<sha256(canonical_json(parameters))>

curl -s -X POST "https://www.agentpmt.com/api/external/tools/6948d263b54506f955d789f0/invoke" \
  -H "Content-Type: application/json" \
  -d '{
    "wallet_address": "0xYOUR_WALLET",
    "session_nonce": "<session_nonce>",
    "request_id": "invoke-uuid",
    "signature": "0x<signature>",
    "parameters": {
      "action": "your_action",
      "your_param": "value"
    }
  }'

Actions(6)

ftp_upload^5cr3 params(2 required)

Upload a file to an FTP or FTPS server. Supports text and base64-encoded binary content.

urlrequiredstring

FTP/FTPS URL with path to the destination file (e.g., ftp://user:pass@ftp.example.com:21/path/to/file.txt). Use ftps:// for encrypted connections.

contentrequiredstring

File content to upload. For binary files, provide base64-encoded content and set content_encoding to 'base64'.

content_encodingstring

How content is encoded: 'text' for plain text, 'base64' for binary files

Values:

textbase64

Default: text

ftp_download^5cr2 params(1 required)

Download a file from an FTP or FTPS server. Returns file content as text or base64.

urlrequiredstring

FTP/FTPS URL with path to the file to download (e.g., ftp://user:pass@ftp.example.com:21/reports/q1.csv)

optionsobject

Download options

Properties:

return_base64(boolean)- Return file content as base64 instead of text. Use for binary files.

ftp_list^5cr2 params(1 required)

List the contents of a directory on an FTP or FTPS server.

urlrequiredstring

FTP/FTPS URL with path to the directory (e.g., ftp://user:pass@ftp.example.com:21/documents/)

optionsobject

Listing options

Properties:

recursive(boolean)- List subdirectories recursively

ftp_delete^5cr2 params(2 required)

Delete a file on an FTP or FTPS server. Requires explicit confirmation via options.confirm_delete.

urlrequiredstring

FTP/FTPS URL with path to the file to delete (e.g., ftp://user:pass@ftp.example.com:21/old-files/archive.zip)

optionsrequiredobject

Delete options

Properties:

confirm_delete*(string)- Must be set to the string 'DELETE' to confirm file deletion

ssh_execute^5cr3 params(2 required)

Execute a shell command on a remote server via SSH. Supports password and key-based authentication.

urlrequiredstring

SSH URL (e.g., ssh://user:pass@server.example.com:22). For key auth, omit password and provide private_key in options.

contentrequiredstring

Shell command to execute on the remote server (e.g., 'ls -la /home/user')

optionsobject

SSH connection options

Properties:

timeout(integer)- Command timeout in seconds

private_key(string)- SSH private key in PEM format for key-based authentication

known_hosts(string)- SSH known hosts string for host verification

mqtt_publish^5cr3 params(2 required)

Publish a message to an MQTT or MQTTS broker. The topic is specified as the URL path.

urlrequiredstring

MQTT URL with the topic as the path (e.g., mqtt://user:pass@broker.example.com:1883/sensors/temperature). Use mqtts:// for TLS.

contentrequiredstring

Message payload to publish (plain text or JSON string)

optionsobject

MQTT publish options

Properties:

qos(integer)- Quality of Service level: 0=at most once, 1=at least once, 2=exactly once

retain(boolean)- Broker retains the message for future subscribers

client_id(string)- MQTT client identifier. Auto-generated if not provided.

Usage Instructions

Usage guidance provided directly by the developer for this product.

Multi-Protocol Bridge

Name: Multi-Protocol Bridge
Brand: Apoth3osis
SKU: 6948d263b54506f955d789f0
Price: 0.05 USD
Availability: InStock

Access FTP, SSH, and MQTT protocols through a unified HTTP interface. All actions use a URL-first approach where connection details (host, port, credentials, path) are encoded in the URL.

URL Format

All actions require a protocol URL:

scheme://username:password@hostname:port/path

Supported schemes:

ftp:// / ftps:// (FTP with optional TLS)
ssh:// (SSH remote commands)
mqtt:// / mqtts:// (MQTT with optional TLS)

Actions

ftp_upload

Upload a file to an FTP/FTPS server.

Required fields:

action: "ftp_upload"
url: FTP URL with path to the destination file (scheme must be ftp:// or ftps://)
content: File content to upload (text or base64-encoded)

Optional fields:

content_encoding: "text" (default) or "base64" for binary files

Example:

{
  "action": "ftp_upload",
  "url": "ftp://myuser:mypass@ftp.example.com:21/uploads/report.txt",
  "content": "Monthly report data here..."
}

Example (binary file):

{
  "action": "ftp_upload",
  "url": "ftps://myuser:mypass@ftp.example.com:21/images/logo.png",
  "content": "iVBORw0KGgoAAAANSUhEUg...",
  "content_encoding": "base64"
}

Limits: Maximum file size is 100 MB.

ftp_download

Download a file from an FTP/FTPS server.

Required fields:

action: "ftp_download"
url: FTP URL with path to the file to download (scheme must be ftp:// or ftps://)

Optional fields:

options.return_base64 (boolean): Return file content as base64 instead of text. Default: false. Use this for binary files.

Example:

{
  "action": "ftp_download",
  "url": "ftp://myuser:mypass@ftp.example.com:21/reports/q1.csv"
}

Example (binary download):

{
  "action": "ftp_download",
  "url": "ftps://myuser:mypass@ftp.example.com:21/images/photo.jpg",
  "options": { "return_base64": true }
}

Limits: Maximum file size is 100 MB. Non-text files that fail UTF-8 decoding are automatically returned as base64.

ftp_list

List the contents of a directory on an FTP/FTPS server.

Required fields:

action: "ftp_list"
url: FTP URL with path to the directory (scheme must be ftp:// or ftps://)

Optional fields:

options.recursive (boolean): List subdirectories recursively. Default: false

Example:

{
  "action": "ftp_list",
  "url": "ftp://myuser:mypass@ftp.example.com:21/documents/"
}

Example (recursive):

{
  "action": "ftp_list",
  "url": "ftp://myuser:mypass@ftp.example.com:21/project/",
  "options": { "recursive": true }
}

Limits: Results are capped at 1,000 entries.

ftp_delete

Delete a file on an FTP/FTPS server. Requires explicit confirmation.

Required fields:

action: "ftp_delete"
url: FTP URL with path to the file to delete (scheme must be ftp:// or ftps://)
options.confirm_delete: Must be the string "DELETE" to confirm deletion

Example:

{
  "action": "ftp_delete",
  "url": "ftp://myuser:mypass@ftp.example.com:21/old-files/archive.zip",
  "options": { "confirm_delete": "DELETE" }
}

ssh_execute

Execute a shell command on a remote server via SSH.

Required fields:

action: "ssh_execute"
url: SSH URL (scheme must be ssh://)
content: The shell command to execute

Optional fields:

options.timeout (integer): Command timeout in seconds. Default: 30
options.private_key (string): SSH private key in PEM format for key-based authentication. When provided, password in the URL can be omitted.
options.known_hosts (string): SSH known hosts entry for host verification

Example (password auth):

{
  "action": "ssh_execute",
  "url": "ssh://deploy:s3cret@server.example.com:22",
  "content": "df -h && uptime"
}

Example (key-based auth):

{
  "action": "ssh_execute",
  "url": "ssh://deploy@server.example.com:22",
  "content": "ls -la /var/log",
  "options": {
    "private_key": "-----BEGIN RSA PRIVATE KEY-----\n...\n-----END RSA PRIVATE KEY-----",
    "timeout": 60
  }
}

Limits: Command output (stdout/stderr) is capped at 10 MB each.

mqtt_publish

Publish a message to an MQTT broker.

Required fields:

action: "mqtt_publish"
url: MQTT URL with the topic as the path (scheme must be mqtt:// or mqtts://)
content: Message payload (plain text or JSON string)

Optional fields:

options.qos (integer): Quality of Service level. 0 = at most once (default), 1 = at least once, 2 = exactly once.
options.retain (boolean): Broker retains the message for future subscribers. Default: false
options.client_id (string): MQTT client identifier. Auto-generated if not provided.

Example:

{
  "action": "mqtt_publish",
  "url": "mqtt://sensoruser:sensorpass@broker.example.com:1883/sensors/temperature",
  "content": "{\"value\": 22.5, \"unit\": \"celsius\"}"
}

Example (with QoS and retain):

{
  "action": "mqtt_publish",
  "url": "mqtts://admin:secret@broker.example.com:8883/alerts/critical",
  "content": "Server CPU above 95%",
  "options": { "qos": 2, "retain": true, "client_id": "monitoring-agent" }
}

Limits: Payload size is capped at 1 MB.

Common Workflows

Deploy a file and verify it exists

Use ftp_upload to upload the file.
Use ftp_list on the parent directory to confirm it appears.

Remote server health check

Use ssh_execute with a command like uptime && free -m && df -h to get server status.

IoT data publishing

Use mqtt_publish to send sensor readings to a topic with qos: 1 for guaranteed delivery.

Secure file transfer

Use ftps:// scheme for encrypted FTP connections.
Use mqtts:// scheme for encrypted MQTT connections.
Use options.private_key for SSH key-based authentication.

Important Notes

URL encoding: Special characters in usernames or passwords must be URL-encoded (e.g., @ becomes %40).
Default ports: FTP uses 21, SSH uses 22, MQTT uses 1883, MQTTS uses 8883. You can omit the port to use the default.
FTP anonymous access: If no username is provided, connections default to anonymous access.
Delete safety: The ftp_delete action requires options.confirm_delete set to "DELETE" as a safeguard.
Binary files: Use content_encoding: "base64" for uploading binary files and options.return_base64: true for downloading them.
SSH authentication: Provide either a password in the URL or a private_key in options, not both.

About The Developer

Apoth3osis

★15 stars

Joined Agent Payment: August 14, 2025

We build tools that enable AI agents to excel in the mathematical realm.

Our small team develops experimental and unique solutions in the AI arena, with a strong focus on modular computing for agentic applications and custom model deployment. We have handled projects for a variety of applications across many sectors, from algorithmic trading and financial analysis, to molecular simulations and predictions, to habitat and biodiversity monitoring and wildlife conservation.

Multi-Protocol Bridge

Description