Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps.
MCPpedia last refreshed this data
io.github.gitayg/appcrane is an MCP server that deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"appcrane": {
"env": {
"APPCRANE_KEY": "your_api_key",
"APPCRANE_URL": "https://crane.example.com",
"APPCRANE_GITHUB_TOKEN": "ghp_optional_for_github_passthrough"
},
"args": [
"-y",
"appcrane-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked appcrane-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP server for Dynatrace Managed to access logs, events, and metrics.
An MCP server for Azure DevOps
MCP Security Weekly
Get CVE alerts and security updates for io.github.gitayg/appcrane and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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 X-API-Key. This package is a thin stdio MCP server that:
appcrane_* 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 (74 tools). To actually invoke tools against your instance, set:
| Env var | Required | Description |
|---|---|---|
APPCRANE_URL | for calls | Your instance base URL, e.g. https://crane.example.com |
APPCRANE_KEY | for calls | Your AppCrane API key (sent as X-API-Key) |
APPCRANE_GITHUB_TOKEN | optional | A GitHub PAT (sent as X-Github-Token) to unlock the github_* passthrough tools |
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 `getToolCata