Official description2 sourcesMCP servers2d ago
gitayg/appcrane-mcp
Self-hosted, MCP-native deployment p
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add appcrane-mcp -- npx -y appcrane-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 0 ★ · gitayg/appcrane-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-15 · last seen 2026-10-16 · seen 2× · listed by 2 sources
- Score
- score 203 · 2 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
gitayg/appcrane-mcp；first catalogued 2026-10-15；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
appcrane-mcp
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The standalone MCP connector for **AppCrane** — the self-hosted deployment platform for AI-built, agent-deployed apps.
AppCrane exposes an MCP server at /api/mcp that requires an X-API-Key. This package is a thin **stdio** MCP server that:
1. Serves the full 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.
2. **Proxies real 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.
How you connect
There is no hosted service and no AppCrane account. The flow is entirely your own:
1. You self-host AppCrane (AGPL) somewhere you control.
2. You issue an API key from that instance.
3. Your agent runs this connector locally over **stdio** (npx -y appcrane-mcp).
4. The connector forwards each 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.
Install / run
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:
| 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 |
MCP client configuration
This is a **stdio** command server (not an HTTP endpoint). Add it to your MCP client config like this:
Claude Code CLI:
How it works
- **tools/list**
- If 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.
- If not configured → returns the **bundled static 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
Development
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.
Releasing
Bump version in package.json, commit, then push a matching tag:
AppCrane exposes an MCP server at /api/mcp that requires an X-API-Key. This package is a thin **stdio** MCP server that:
1. Serves the full 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.
2. **Proxies real 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.
How you connect
There is no hosted service and no AppCrane account. The flow is entirely your own:
1. You self-host AppCrane (AGPL) somewhere you control.
2. You issue an API key from that instance.
3. Your agent runs this connector locally over **stdio** (npx -y appcrane-mcp).
4. The connector forwards each 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.
Install / run
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:
| 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 |
MCP client configuration
This is a **stdio** command server (not an HTTP endpoint). Add it to your MCP client config like this:
Claude Code CLI:
How it works
- **tools/list**
- If 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.
- If not configured → returns the **bundled static 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
Development
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.
Releasing
Bump version in package.json, commit, then push a matching tag:
- Source
- awesome · https://github.com/gitayg/appcrane-mcp
- Browse by field
- MCP servers
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.