Bastrio

io.bastrPublished by bastr.ioOfficial publishervrelease-20261015-ops1Updated Oct 27, 2026

Manage remote servers, SSH terminals, files, databases and proxies with scoped access and approvals.

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureFiles & Storage

Overview

AI-generated overview

Bastrio is a remote MCP endpoint for managing servers, SSH terminals, files, databases and proxies with scoped access and approvals.

What you can do
  • Manage remote servers and SSH terminals
  • Work with files on connected hosts
  • Access databases
  • Operate proxies
  • Apply scoped access and approval rules to these operations
When to use it
Useful when an assistant should operate remote infrastructure — servers, SSH sessions, files, databases or proxies — under scoped permissions and approval steps rather than with unrestricted access.
Requirements
A remote streamable HTTP endpoint at bastr.io, reachable over the network. OAuth authentication is required: send an Authorization header with the word Bearer, a space, and a Bastrio MCP API key created in the workspace MCP API keys page. No local runtime or environment variables are needed.
Before you install
The server grants access to servers, terminals, files, databases and proxies, so the API key is a powerful credential; keep it secret and scope it narrowly. Operations may change or delete data on connected systems, and approvals are the main safeguard. Review which hosts and resources the key can reach before connecting.

Installation

In SourceWeft

  1. Open Bastrio in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.bastr%2Fbastrio/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bastrio": {
      "type": "http",
      "url": "https://bastr.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. vrelease-20261015-ops1LatestOct 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.