HTTP through SSH
Test internal APIs without manual tunnels.
Open an SSH session to a jump host. Pick that session as the route for an HTTP request. Hit an internal-only API and inspect response, timing, headers, and errors — without ssh -L, kubectl port-forward, or a VPN client. Postman v2.1, OpenAPI 3.x, cURL, and HAR imports work as expected.
GraphQL and realtime
One client, every protocol you need.
Side-by-side query + variables editor for GraphQL. WebSocket and Server-Sent Events for realtime. Realtime collections, like REST, route through active SSH sessions when the endpoint is internal-only.
Data Inspector
Postgres, MySQL, SQL Server, SQLite, Redis, Mongo — same workspace.
Open a database connection, run a query, inspect the schema, watch a Health dashboard (active sessions, locks, slow queries) — all in the same window as the SSH session and the API client. Six engines including T-SQL on Microsoft SQL Server (Pro and above). No context switch to a separate IDE.
SSH and local terminal
A real terminal next to everything else.
Saved SSH connections, key-based or password auth (with scoped credentials from the vault), SCP / SFTP file transfer, and a local terminal that opens in the active Space's working directory. Tabs and panes for parallel sessions.
Docs and runbooks
Documentation that lives where the work happens.
Notes, runbooks, incident reports, and IPAM records inside the Space. Capture the curl that worked, the query that explained the slowness, the config diff that fixed the bug — and the next engineer finds it next to the connection.
Cloud Shells
aws, gcloud, and az — already logged in.
A local terminal per profile with the provider CLI pre-authenticated from the Space's stored credentials. Point at an existing ~/.aws named profile and your SSO and assume-role chains work exactly as they do in your own shell — ShellYard never holds the key. Every shell opens with the resolved identity printed, which is the check that stops you running against the wrong account. Pro and above.
Connectors (MCP)
Attach Claude Code to your own infrastructure.
ShellYard runs as a local MCP server, so Claude Code, Claude Desktop, or a local Ollama-backed client drives your inventory, documents, and read-only device commands on its own model subscription — one claude mcp add away. Bound to localhost with a per-install bearer token; anything that changes state pauses for an approval modal inside ShellYard. Pro and above.
Magellan
AI for the output you just generated.
Attach an HTTP response, a slow query, a packet capture, a config diff, or a log line — Magellan explains what happened and helps draft the documentation. BYO Anthropic / OpenAI / Gemini / Ollama key. ShellYard takes no AI markup.
Private infrastructure
Built for the network you can't reach from your laptop.
Behind a jump host. Inside a customer VPN. On a lab subnet. Behind staging. ShellYard is designed for the work that doesn't happen on the public internet — and keeps the connection, request, response, and runbook together when it does.