# Relaystation [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://relaystation.ai  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/relaystation

## Description
Pay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the Relaystation MCP server does

The Relaystation MCP server is described as pay-per-call infrastructure for agents. Its listed capability areas are file storage and handoff, compute tools, messaging, electronic signatures, and KYC.

File storage and handoff cover the movement or exchange of files between participants or agent workflows. Compute tools indicate access to externally provided computation. Messaging covers communication functions, while e-signature supports electronic signing workflows. KYC refers to know-your-customer processes. The description does not specify supported file types, messaging channels, signature providers, identity checks, compute runtimes, or geographic availability.

The pay-per-call designation is important when evaluating the service. Confirm those details before selecting Relaystation for an automated workflow with predictable or high request volume.

## Limitations and notes

The available source is the project URL and a short description; a README was not provided. As a result, the Relaystation MCP server cannot be documented here with verified installation commands, configuration fields, environment variables, transport details, authentication steps, client compatibility, or named tools. The description also does not establish whether all listed capabilities are available through one server configuration or require separate services.

Before implementation, verify how the server is launched, how an agent authenticates, how pay-per-call usage is metered, and what responses and errors each capability returns. Developers should also confirm how files are retained and transferred, what data KYC processing requires, and whether e-signature or messaging actions need user approval. These unknowns do not contradict the listed capabilities; they mark details that require confirmation from Relaystation's documentation.

_Full upstream README: https://allmcps.com/mcp/relaystation/readme_