Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @apso/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add apso-cli -- npx -y @apso/cli@0.49.1รันในเทอร์มินัล
{ "mcpServers": { "apso-cli": { "command": "npx", "args": [ "-y", "@apso/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Define a schema. Get a production API. Keep the code.
Apso generates production-ready backend services from a JSON schema file. You get real framework code (NestJS, FastAPI, or Gin) that you own, run anywhere, and extend with standard patterns. For the complete documentation, see Apso Docs.
Apso CLI
Homebrew (macOS / Linux)
brew tap apsoai/tap
brew install apso
npm
npm install -g @apso/cli
Requires Node.js 18.0 or higher.
Apso works as an MCP server inside Claude Code, Cursor, Windsurf, and other MCP-compatible editors. Your AI assistant can design schemas, generate APIs, and deploy backends through conversation.
Claude Code
claude mcp add apso -- apso mcp serve
Cursor / VS Code / Other editors
Add to your MCP configuration:
{
"mcpServers": {
"apso": {
"command": "apso",
"args": ["mcp", "serve"]
}
}
}
Available tools:
Schema edit tools (from @apso/schema-tools) change the project's .apsorc one step at a time. Each write is linted with the rules apso generate enforces; a change that would add a lint error is rejected and the file is left as it was.
Available resources:
Authenticate with the Apso platform:
apso login
This opens a browser window for OAuth authentication. For CI/CD environments, use a token:
apso login --token <api-token>
# Create a new project
apso init --name my-app --language typescript
# Edit .apsorc to define your schema
# Generate code from schema
apso generate
# Start Postgres and run the API
apso dev
Your API is live at http://localhost:3000 with Swagger docs at /api. The generated code lives in src/autogen/ and is standard NestJS with TypeORM -- no Apso runtime dependency.
apso initCreate a new Apso project from a language-specific template.
apso init
apso init --name my-app --language typescript
apso init --name my-app --language python --skip-platform
When authenticated, apso init lets you create a new project or clone an existing one from the platform.
apso generateGenerate backend code from the .apsorc schema file.
apso generate
apso generate --language python
apso generate --skip-format
Generated files are placed in src/autogen/. These files are overwritten on each run. Place custom code in src/extensions/ to avoid losing changes.
apso devStart the local development server using Docker Compose.
apso dev
apso dev --build
apso dev --detach
Requires Docker and Docker Compose. Looks for docker-compose.yml in the current directory.
apso migrateDetect schema changes, generate migration SQL, and test against a local PGlite sandbox. No Docker or external database required.
apso migrate # Detect changes, generate and test SQL
apso migrate --apply # Update snapshot after successful test
apso migrate --reset # Clear sandbox and start fresh
apso migrate --sql # Output raw SQL only (for piping)
The sandbox works by comparing your current .apsorc against the last-known snapshot, generating the migration SQL, and executing it against an in-process Postgres instance (PGlite). If the migration fails locally, you know before it reaches any real database.
apso deployDeploy the linked service to the Apso platform. Runs a local migration check before deploying.
apso deploy
apso deploy --yes
apso deploy --skip-migrate
apso deploy --no-wait
If schema changes are detected, apso deploy shows the migration SQL and asks for confirmation before proceeding. If the migration fails locally, the deploy is blocked.
apso loginAuthenticate with the Apso platform via browser-based OAuth or API token.
apso login
apso login --token <api-token>
apso logoutClear stored credentials.
apso logout
apso whoamiDisplay information about the current authenticated user and linked project.
apso whoami
apso linkLink the current project to a platform service.
apso link
apso link --workspace my-team --service my-api
apso link --force
apso unlinkRemove the link between the current project and the platform.
apso unlink
apso statusShow the current service and latest build status.
apso status
apso logsView build logs for the linked service.
apso logs
apso logs <build-id>
apso openOpen the service dashboard or API endpoint in the browser.
apso open
apso projectsList services in a workspace.
apso projects
apso configView or modify CLI configuration.
apso config # Show all settings
apso config get apiUrl # Get a specific value
apso config set verbose true # Set a value
apso config reset # Reset to defaults
Configuration keys:
Boolean values accept true/false or 1/0.
Environment variables override config file values:
apso schemaManage schema synchronization between local .apsorc and the platform.
apso schema validate # Validate local schema
apso schema diff # Show diff between local and remote
apso schema push # Push local schema to platform
apso schema pull # Pull remote schema to local
These options work with any command:
apso [command] --help # Show command help
apso [command] --version # Show CLI version
The CLI sends anonymous usage data so we can see which commands are used and prioritize accordingly. It is opt-out and carries no personal data.
What is collected: command name (generate, init, deploy, …), CLI
version, OS and architecture, Node version, command duration and success, and
an anonymous install id (a random UUID stored in your CLI config — not derived
from any machine identifier). If you are logged in, events attribute to your
Apso account, the same as the web app.
What is never collected: your source code, your .apsorc or schema
contents, file paths, environment variable values, or any other file contents.
Opt out any of these ways:
apso config set telemetry off # persisted in your CLI config
export APSO_TELEMETRY=0 # per-shell
export DO_NOT_TRACK=1 # honors the consoledonottrack.com standard
On first run the CLI prints a one-time notice pointing at these opt-outs.
See docs/telemetry.md for full detail. Aggregate
public download stats (npm/PyPI) are available via node scripts/usage-stats.mjs.
git clone https://github.com/apsoai/cli.git
cd cli
npm install
npm run build
To run commands from the local build:
./bin/run generate
./bin/run migrate --sql
To develop continuously:
npm run build # Rebuild after changes
npm link # Make 'apso' command available globally
npm run test # Run all tests
npm run test:watch # Watch mode
npm run test:cov # Coverage report
env DEBUG=* ./bin/run generate
MIT
{ "mcpServers": { "apso-cli": { "command": "npx", "args": [ "-y", "@apso/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@apso/cli ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-15 Apso CLI