appcrane-mcp
The standalone MCP connector for AppCrane — the self-hosted deployment platform for AI-built, agent-deployed apps.
AppCrane exposes an MCP server at <instance>/api/mcp that requires an . This package is a thin MCP server that:
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add appcrane-mcp -- npx -y appcrane-mcp@1.8.2รันในเทอร์มินัล
{ "mcpServers": { "appcrane-mcp": { "command": "npx", "args": [ "-y", "[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.
เปิดจากผู้เผยแพร่
The standalone MCP connector for AppCrane — the self-hosted deployment platform for AI-built, agent-deployed apps.
AppCrane exposes an MCP server at <instance>/api/mcp that requires an . This package is a thin MCP server that:
Standalone MCP connector for AppCrane — the self-hosted deployment platform for AI-built apps. Serves the appcrane_* tool catalog for offline introspection and proxies real tool calls to your AppCrane instance.
X-API-Keyappcrane_* tool catalog for tools/list introspection with zero configuration — it ships a bundled catalog.json, so registries and sandboxes (e.g. Glama) can start it in a container and introspect it offline.tools/call to your own AppCrane instance once APPCRANE_URL and APPCRANE_KEY are set.It runs anywhere Node 20+ is available, via npx appcrane-mcp.
Licensing: this connector is MIT. The AppCrane platform it talks to is a separate project and is AGPL-3.0. Installing this package does not pull the platform in — the connector is a client that talks to an AppCrane instance you host yourself.
There is no hosted service and no AppCrane account. The flow is entirely your own:
npx -y appcrane-mcp).tools/call to ${APPCRANE_URL}/api/mcp with your
X-API-Key. Your key stays in your own MCP client config; it is never sent anywhere
except the instance URL you set.npx appcrane-mcp
With no environment variables it still starts and answers tools/list from the bundled catalog (57 tools). To actually invoke tools against your instance, set:
This is a stdio command server (not an HTTP endpoint). Add it to your MCP client config like this:
{
"mcpServers": {
"appcrane": {
"command": "npx",
"args": ["-y", "appcrane-mcp"],
"env": {
"APPCRANE_URL": "https://crane.example.com",
"APPCRANE_KEY": "your_api_key",
"APPCRANE_GITHUB_TOKEN": "ghp_optional_for_github_passthrough"
}
}
}
}
Claude Code CLI:
claude mcp add appcrane \
--env APPCRANE_URL=https://crane.example.com \
--env APPCRANE_KEY=your_api_key \
-- npx -y appcrane-mcp
tools/list
APPCRANE_URL + APPCRANE_KEY are set → connects to ${APPCRANE_URL}/api/mcp (StreamableHTTP, header X-API-Key, plus X-Github-Token when the GitHub token is set), fetches the live, auth-filtered tool list, and returns it. If the instance is unreachable it falls back to the bundled catalog.catalog.json). This path needs no env vars, which is what a registry's introspection sandbox hits.tools/call → requires APPCRANE_URL + APPCRANE_KEY; forwards the call to the backend and returns its result. Without configuration it returns a clear "not configured" error.docker build -t appcrane-mcp .
# Introspection only (no config) — starts and serves tools/list:
docker run -i --rm appcrane-mcp
# Full use:
docker run -i --rm \
-e APPCRANE_URL=https://crane.example.com \
-e APPCRANE_KEY=your_api_key \
appcrane-mcp
npm install
npm run build # tsc -> dist/
npm run gen:catalog # regenerate catalog.json from the AppCrane platform source
npm run check:catalog # fail if catalog.json has drifted from that source
node scripts/test-list.mjs # smoke test: spawn over stdio, assert tools/list
Both catalog scripts import the platform's own getToolCatalog() from a sibling
deployhub checkout; set APPCRANE_SRC to point at its server/services/mcpTools.js
if yours lives elsewhere.
Bump version in package.json, commit, then push a matching tag:
git tag v1.7.1 && git push origin v1.7.1
.github/workflows/publish.yml publishes it to npm with npm Trusted Publishing: no npm
token and no one-time password, and npm attaches provenance (the commit it was built from).
The workflow refuses a tag that does not match package.json, and checks the catalog against
the platform's current main before publishing, so a stale catalog.json cannot ship. (It
has rotted silently before: 22 tools behind the platform, 35 advertised against 57 real.)
Run npm run check:catalog locally first to find out before CI does.
The same tag then lists the version in the official MCP Registry
as io.github.gitayg/appcrane, also by OIDC. Bump version and packages[0].version in
server.json together with package.json: the workflow refuses a tag that does not match all three.
(The listing sat at 1.0.0 while npm moved on, until this was automated.)
The bundled catalog.json is generated from the real tool definitions in the AppCrane platform (deployhub/server/services/mcpTools.js) and reflects the AWS-aligned tool vocabulary (appcrane_set_secret, appcrane_get_secret, appcrane_cp, and the stage parameter). It is committed so the package ships self-contained.
AppCrane is a self-hosted home for AI-built and AI-deployed apps. This connector is MIT-licensed to maximize adoption; the platform itself is AGPL.
Standalone MCP connector for AppCrane — the self-hosted deployment platform for AI-built apps. Serves the appcrane_* tool catalog for offline introspection and proxies real tool calls to your AppCrane
{ "mcpServers": { "appcrane-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}ภาพรวม
Standalone MCP connector for AppCrane — the self-hosted deployment platform for AI-built apps. Serves the appcrane_* tool catalog for offline introspection and proxies real tool calls to your AppCrane instance.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Appcrane ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-13 Standalone MCP connector for AppCrane — the self-hosted deployment platform for AI-built apps. Serves the appcrane_* tool catalog for offline introspection and proxies real tool calls to your AppCrane instance.