aispace

Name: aispace
Author: aispace-sh

by aispace-shversion 0.4.1i★ –iRuns on your computer

Registry namesh.aispace/mcp

Install

Overview

Description from the maker (original English)

Secure, expiring artifact storage and handoff for AI agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: AISPACE_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: AISPACE_KEY, AISPACE_URL, AISPACE_ALLOWED_ROOTS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "aispace": {
      "command": "npx",
      "args": [
        "-y",
        "@aispace-sh/cli",
        "mcp",
        "serve"
      ],
      "env": {
        "AISPACE_KEY": "your-value",
        "AISPACE_URL": "your-value",
        "AISPACE_ALLOWED_ROOTS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add aispace --env AISPACE_KEY=your-value --env AISPACE_URL=your-value --env AISPACE_ALLOWED_ROOTS=your-value -- npx -y @aispace-sh/cli mcp serve

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "aispace": {
      "command": "npx",
      "args": [
        "-y",
        "@aispace-sh/cli",
        "mcp",
        "serve"
      ],
      "env": {
        "AISPACE_KEY": "your-value",
        "AISPACE_URL": "your-value",
        "AISPACE_ALLOWED_ROOTS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "aispace": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@aispace-sh/cli",
        "mcp",
        "serve"
      ],
      "env": {
        "AISPACE_KEY": "your-value",
        "AISPACE_URL": "your-value",
        "AISPACE_ALLOWED_ROOTS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

AISPACE_KEY secret required env
Scoped aispace bot key (ask_...).
AISPACE_URL env
Optional aispace service origin; defaults to https://aispace.sh.
AISPACE_ALLOWED_ROOTS env
Optional platform path-list restricting local file access.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain aispace.sh (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32564 servers in this category
Published to the registry more recently than 39% of the other 32564 servers in this category
Basic checks equal to or better than 100% of the other 32564 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is aispace safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: AISPACE_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Tools MCP

by First-CH

Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

aispace

Secure temporary file sharing for AI agents and humans.

A scriptable CLI with expiring links, predictable JSON, and optional local age encryption.

Website · Documentation

aispace.sh is a bot-friendly file drop for outputs that are too large, structured, or temporary for chat. The open-source client is deliberately easy to automate: one binary, stable exit codes, streaming uploads, and share URLs printed on a predictable final line.

Built for agents: stable JSON on supported commands, documented errors, stdin support, and explicit noninteractive flags for automation. Secret-bearing handoff commands remain interactive.
Short-lived by design: file expiration, separately expiring links, revocation, and optional per-link download caps.
Private when needed: sealed asynchronous transfers encrypt filenames, file metadata, and content locally; their master key never reaches aispace. The existing age X25519 flow remains available for recipient-key workflows.

Sealed transfers, agent identities, device pairing, and adaptive durable-first intent are experimental surfaces. Ordinary uploads and durable R2 storage continue to work alongside them.

The hosted service is operated separately. This repository contains the client, agent skill, and integration examples—not the server, billing system, deployment configuration, or customer data.

Try it in 60 seconds

Install the latest release:

curl -fsSL https://aispace.sh/install.sh | sh

Authenticate with a key created in the aispace dashboard, then store a file:

aispace login --key ask_...

aispace upload report.pdf --json

On a Pro account, add a separately expiring public handoff:

aispace upload report.pdf --link --link-expires 1h --max-downloads 1

The URL is printed last on its own line, making it easy for an agent or shell script to capture. Add --json for a stable machine-readable response. An abridged response looks like:

{"file":{"id":"...","name":"report.pdf"},"link":{"url":"https://aispace.sh/d/...","expires_at":1757003600}}

Other installation channels:

npm install -g @aispace-sh/cli

brew install aispace-sh/tap/aispace go install github.com/aispace-sh/aispace-client@latest

Pin the shell installer with AISPACE_VERSION=v1.2.3. Release binaries support macOS, Linux, and Windows on amd64 and arm64. The shell installer supports macOS and Linux; use npm on Windows.

Using Grok Bot? Give Grok Bot a fast, bot-friendly way to share files with aispace.

Add the aispace bot to Grok Bot →

Give aispace to an agent

The repository includes a reusable Codex-compatible skill. Clone the repository and link the skill into your personal Codex skills directory:

git clone https://github.com/aispace-sh/aispace-client.git

mkdir -p ~/.codex/skills ln -s "$PWD/aispace-client/skills/aispace" ~/.codex/skills/aispace

Restart Codex, then ask it to use aispace when it needs to hand you a report, archive, image, or other generated artifact. The skill defaults to account-private storage unless you request a public link, prefers short expirations, and treats encryption identities as credentials.

Model Context Protocol (MCP)

The native CLI also exposes ten typed MCP tools over local stdio. Create a separately scoped bot key in the dashboard, export it in the environment that launches Codex, and add:

[mcp_servers.aispace]

command = "aispace" args = ["mcp", "serve"] env_vars = ["AISPACE_KEY", "AISPACE_URL", "AISPACE_ALLOWED_ROOTS"] startup_timeout_sec = 10 tool_timeout_sec = 120 default_tools_approval_mode = "writes"

[mcp_servers.aispace.tools.aispace_create_link] approval_mode = "prompt"

[mcp_servers.aispace.tools.aispace_revoke_link] approval_mode = "prompt"

[mcp_servers.aispace.tools.aispace_delete_file] approval_mode = "prompt"

Run codex mcp list to verify the connection. The ChatGPT desktop app, Codex CLI, and Codex IDE extension on the same host share this configuration. Keep the key in a secret store or injected environment; never put its expanded value in a committed project file or command argument. See docs/CLI.md for Claude Code and generic-host examples.

For custom agent runtimes, docs/LLM_USAGE.md includes a system-prompt snippet, OpenAI/Anthropic-compatible tool schemas, and a reference Python handler. See examples for runnable shell, CI, and encrypted-handoff recipes.

Common workflows

# Upload text from stdin and return an expiring public link (Pro).

echo "hello" | aispace upload - --name note.txt --link --link-expires 1h

Keep a file available only to this key.

aispace upload secret.txt --private

Share ciphertext; keep the generated age identity locally.

aispace upload secret.pdf --encrypt --identity-out secret.agekey --link

Authenticated handoff to another key on the same account—no public URL.

aispace upload notes.md --shared --json

Sealed multi-file handoff. The URL fragment holds the local decryption secret.

aispace transfer create report.pdf charts.png --sealed --link --expires 1d --max-downloads 1

Move that sealed transfer to a nearby browser/device with an expiring code.

aispace handoff offer "$TRANSFER_ID"

On the receiving CLI: aispace handoff receive J7KM-PQRT

Pin an agent and deliver without exposing a bearer decryption link.

aispace recipient add "$RECIPIENT_INVITATION" aispace recipient verify research-agent --fingerprint "$RECIPIENT_FINGERPRINT" aispace transfer create report.pdf --sealed --to research-agent --from my-agent --expires 7d aispace inbox receive "$DELIVERY_ID" --yes

Paste the link interactively, inspect its private manifest, then decrypt and verify.

aispace transfer receive

Receive, manage, and revoke.

aispace ls --json aispace download --output ./file aispace download --output ./file --verify # check the recorded SHA-256 aispace link --expires 30m --max-downloads 1 aispace revoke aispace rm

Follow docs/SECURE_HANDOFFS.md for sealed bundles, trusted agent inboxes, device pairing, adaptive R2 fallback, and recovery. The complete command reference is in docs/CLI.md; the HTTP contract is in docs/API.md.

upload accepts --name, --expires, --content-type, --sha256, --link, --link-expires, --max-downloads, --private, --shared, --encrypt, --recipient, and --identity-out. Uploads stream from disk. Encrypted uploads use age X25519 locally and store ciphertext as .age; the secret identity is never sent to the API.

transfer create uses aispace-sealed-v1: AES-256-GCM authenticated chunks and an encrypted manifest support multiple files, ranged retry, and a verified receipt. transfer receive accepts the secret from its prompt, --token-file, or AISPACE_TRANSFER_TOKEN; avoid putting a full fragment link or token in a process argument on shared systems.

transfer create --json omits bearer links and tokens unless --include-secret is explicit, and secret-inclusive JSON must be redirected rather than written to a terminal. handoff encode likewise accepts the protected prompt, --token-file, or AISPACE_TRANSFER_TOKEN.

With --json, errors also remain structured and are written to stderr. upload --link --json returns {"file": File, "link": ShareLink}; encrypted uploads add an "encryption" object.

Configuration

Precedence: flag > environment > config file > default.

Setting	Flag	Env	File key	Default
API key	`--key`	`AISPACE_KEY`	`key`	—
Server	`--url`	`AISPACE_URL`	`url`	`https://aispace.sh`

AISPACE_AGE_IDENTITY supplies a decryption identity when decrypt --identity-file is omitted. It is deliberately not accepted as a command-line value.

Config file: $XDG_CONFIG_HOME/aispace/config.json (default ~/.config/aispace/config.json), written with mode 0600. A warning is printed if the file is readable by others. AISPACE_CONFIG overrides the path.

Durations (--expires, --link-expires) accept Go syntax plus a d suffix: 30m, 24h, 7d, 1d12h, or a bare number of seconds. Omitting them uses the server defaults (7 days for files, 1 hour for Pro public links).

File permissions and links

File visibility controls authenticated key access. A public link is a separate capability: creating one requires a Pro account and makes that one file available to anyone holding the URL.

File mode	Who can access it?	File lifetime	Public-link lifetime	Download cap	Exposure if access leaks
`private`	Uploading key only	7 days by default; maximum 7 days on Free or 30 days on Pro	None	Account monthly limit	Private files belonging to that key, until deletion or expiry
`account`	Every active key on the account	7 days by default; maximum 7 days on Free or 30 days on Pro	None	Account monthly limit	Account-shared files, until deletion or expiry
`private` + public link	Uploading key and anyone with the URL	Maximum 30 days because links require Pro	1 hour by default; maximum 30 days and never beyond file expiry	Optional per-link cap	Only the linked file, until link expiry, revocation, exhaustion, file deletion, or file expiry
`account` + public link	Account keys and anyone with the URL	Maximum 30 days because links require Pro	1 hour by default; maximum 30 days and never beyond file expiry	Optional per-link cap	URL access ends with the link; account keys retain access until file deletion or expiry
Client-encrypted file	Visibility controls ciphertext access; only age identity holders can decrypt it	Same limits as the selected file mode	Same Pro-only limits when a link is created	Optional per-link cap	Plaintext exposure requires both the ciphertext and the age identity

Available duration syntax includes 30s, 15m, 1h, 36h, and 7d.

A file becomes unavailable when its file lifetime ends. A link can end sooner because it expired, was revoked, or reached its download cap. Deleting the file immediately ends authenticated key access and every associated public link.

Exit codes

Code	Meaning
0	success
1	generic error (network, 4xx/5xx not listed below)
2	usage error
3	authentication (401, or no key configured)
4	quota / size (402, 413)

| 5 | rate limited (429) — idempotent GETs sleep Retry-After (max 30s) and

Only the beginning is shown; read the rest in the repo

aispace

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Tools MCP

README from the maker

Try it in 60 seconds

Give aispace to an agent

Model Context Protocol (MCP)

Common workflows

Keep a file available only to this key.

Share ciphertext; keep the generated age identity locally.

Authenticated handoff to another key on the same account—no public URL.

Sealed multi-file handoff. The URL fragment holds the local decryption secret.

Move that sealed transfer to a nearby browser/device with an expiring code.

On the receiving CLI: aispace handoff receive J7KM-PQRT

Pin an agent and deliver without exposing a bearer decryption link.

Paste the link interactively, inspect its private manifest, then decrypt and verify.

Receive, manage, and revoke.

Configuration

File permissions and links

Exit codes