aispace MCP Server

What the code does

We read the source, 5 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

postinstall: node scripts/install.js

const result = spawnSync(binary, process.argv.slice(2), { stdio: 'inherit' });

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

            path := filepath.Join(target, name)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp -e 'AISPACE_KEY=<AISPACE_KEY>' -- npx -y @aispace-sh/cli

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@aispace-sh/cli"
      ],
      "env": {
        "AISPACE_KEY": "<AISPACE_KEY>"
      }
    }
  }
}

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@aispace-sh/cli"]
env = { AISPACE_KEY = "<AISPACE_KEY>" }

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@aispace-sh/cli"
      ],
      "env": {
        "AISPACE_KEY": "<AISPACE_KEY>"
      }
    }
  }
}

{
  "servers": {
    "mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@aispace-sh/cli"
      ],
      "env": {
        "AISPACE_KEY": "<AISPACE_KEY>"
      }
    }
  }
}

Put your own value in place of <AISPACE_KEY> (Scoped aispace bot key (ask_...)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: AISPACE_URL (Optional aispace service origin; defaults to https://aispace.sh), AISPACE_ALLOWED_ROOTS (Optional platform path-list restricting local file access).