ALSO Cloud Marketplace MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ALSO Cloud Marketplace MCP ServerList all companies under parent 12345"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ALSO Cloud Marketplace MCP
MCP-Server für die ALSO Cloud Marketplace Simple API — damit KI-Assistenten (Cursor, Claude, Gemini CLI, OpenAI Codex, …) direkt auf Companies, Subscriptions, Users, Invoices usw. zugreifen können.
Protokoll | Model Context Protocol (stdio) |
API | |
Stack | TypeScript / Node.js 20+ |
SDK-Library | go-also-cloud-wrapper (gleiche Auth & Marketplaces) |
Schnellstart
git clone https://github.com/pitwch/also-cloud-marketplace-mcp.git
cd also-cloud-marketplace-mcp
npm install
npm run buildBenötigte Umgebungsvariablen:
Variable | Beispiel | Pflicht |
|
| ja |
|
| ja |
|
| ja |
|
| nein |
|
| nein |
ALSO_CLOUD_MARKETPLACE akzeptiert eine volle URL oder einen Country-Key:Switzerland, Germany, Austria, Debug, …
Related MCP server: SMB AI Command Platform MCP Server
Installation in Clients
Überall gilt: Server lokal starten (stdio), Credentials als env setzen.
Pfad unten durch deinen Clone ersetzen, z. B. C:/DEV/also-cloud-marketplace-mcp oder /home/you/also-cloud-marketplace-mcp.
Empfohlene Variante (gebaut)
command: node
args: [<REPO>/dist/index.js]Alternative (ohne Build, via tsx)
command: npx
args: [tsx, <REPO>/src/index.ts]Voraussetzung: zuvor npm install im Repo.
Cursor
Settings → MCP → Add new MCP server (oder
mcp.jsonbearbeiten).Eintrag hinzufügen:
{
"mcpServers": {
"also-cloud": {
"command": "node",
"args": ["C:/DEV/also-cloud-marketplace-mcp/dist/index.js"],
"env": {
"ALSO_CLOUD_MARKETPLACE": "Switzerland",
"ALSO_CLOUDUSER": "you@example.com",
"ALSO_CLOUDPW": "your-password"
}
}
}
}Server aktivieren / Cursor neu laden.
Im Chat Tools von
also-cloudnutzen, z. B. „Liste Companies unter Parent 12345“.
Claude Desktop
Config öffnen: Settings → Developer → Edit Config
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Gleichen
mcpServers-Block wie bei Cursor einfügen.Claude Desktop vollständig neu starten.
Im Chat das Hammer-/Tools-Icon prüfen —
also-cloudsollte erscheinen.
Claude Code (CLI)
claude mcp add also-cloud --env ALSO_CLOUD_MARKETPLACE=Switzerland --env ALSO_CLOUDUSER=you@example.com --env ALSO_CLOUDPW=secret -- node /path/to/also-cloud-marketplace-mcp/dist/index.jsPrüfen:
claude mcp listGemini CLI
Config in ~/.gemini/settings.json (oder projektbezogen .gemini/settings.json):
{
"mcpServers": {
"also-cloud": {
"command": "node",
"args": ["/path/to/also-cloud-marketplace-mcp/dist/index.js"],
"env": {
"ALSO_CLOUD_MARKETPLACE": "Switzerland",
"ALSO_CLOUDUSER": "you@example.com",
"ALSO_CLOUDPW": "your-password"
}
}
}
}Oder per CLI:
gemini mcp add also-cloud --env ALSO_CLOUD_MARKETPLACE=Switzerland --env ALSO_CLOUDUSER=you@example.com --env ALSO_CLOUDPW=secret -- node /path/to/also-cloud-marketplace-mcp/dist/index.jsDocs: MCP servers with Gemini CLI
OpenAI — Codex CLI / ChatGPT Desktop / IDE
Codex nutzt TOML (~/.codex/config.toml), geteilt mit ChatGPT Desktop & Codex-IDE:
[mcp_servers.also-cloud]
command = "node"
args = ["/path/to/also-cloud-marketplace-mcp/dist/index.js"]
[mcp_servers.also-cloud.env]
ALSO_CLOUD_MARKETPLACE = "Switzerland"
ALSO_CLOUDUSER = "you@example.com"
ALSO_CLOUDPW = "your-password"Oder:
codex mcp add also-cloud \
--env ALSO_CLOUD_MARKETPLACE=Switzerland \
--env ALSO_CLOUDUSER=you@example.com \
--env ALSO_CLOUDPW=secret \
-- node /path/to/also-cloud-marketplace-mcp/dist/index.js
codex mcp listIn der TUI: /mcp zeigt verbundene Server.
Hinweis ChatGPT Web: Custom MCP dort braucht i. d. R. einen öffentlichen HTTPS-Endpoint (Remote/Tunnel), kein lokales stdio. Für lokalen Betrieb Codex CLI / Desktop verwenden.
Docs: OpenAI MCP / Codex
VS Code (GitHub Copilot / MCP)
Je nach Extension analog Cursor: MCP-Server mit command/args/env eintragen.
Pfad auf dist/index.js zeigen und Credentials setzen.
Verwendung (Beispiele)
Nach der Anbindung kannst du natürlichsprachlich fragen:
„Welche Marketplaces gibt es?“ →
list_marketplaces„Zeig Companies unter Parent 523525“ →
get_companies„Hole Subscriptions für Account …“ →
get_subscriptions„Latest Invoices für März 2026“ →
get_latest_invoices_for_period„Lege einen User unter Company X an“ →
create_user(Write)
Discovery aller API-Endpoints:
Tool
list_api_endpoints(optional Filtertag,onlyReadable)
Tools (Überblick)
~58 Tools. Vollständige Liste inkl. Risiko-Flags: Tool list_api_endpoints.
Session & Meta
Tool | Zweck |
| Country-Keys → Base-URLs (ohne Login) |
| Katalog der Simple-API |
| Session prüfen / verwerfen |
| Escape Hatch (u. a. destruktive Endpoints) |
Lesen
Bereich | Tools |
Company / Reseller / Dept / User |
|
Subscriptions |
|
Catalog |
|
Billing |
|
Sonst |
|
Schreiben (gezielt freigeschaltet)
Bereich | Tools |
Accounts |
|
Subscriptions |
|
Actions |
|
Upgrade / Renew |
|
Credit / Deal |
|
Nur über api_request (destruktiv / selten)
TerminateAccount, DeleteMarketplace*, DeleteSpecialDeal, Marketplace-Create/Delete, …
→ bewusst kein eigenes Tool, damit die KI sie nicht versehentlich aufruft.
Entwicklung
npm run dev # stdio via tsx
npm run typecheck
npm run build
npm start # node dist/index.jsWichtig: Auf stdout nur MCP-JSON-RPC schreiben — Logs nur mit console.error.
Sicherheit
Credentials nie committen; nur in Client-
envoder lokaler.env(nicht für stdio-Hosts nötig, wennenvin der MCP-Config steht).Write-Tools ändern Produktivdaten — Clients mit Tool-Bestätigung nutzen (Cursor/Claude/Gemini Prompt).
Destruktive Operationen bewusst hinter
api_requestbelassen.
Links
Go-Wrapper: https://github.com/pitwch/go-also-cloud-wrapper
Swagger: https://app.swaggerhub.com/apis-docs/MarketplaceSimpleAPI/MarketplaceSimpleAPI/1.0.0
License
MIT © Pedrett IT+Web AG
This server cannot be deployed
Maintenance
Related MCP Connectors
One SSO, hundreds of apps, every endpoint open to your AI. Not workflows. A receipt for every call.
Find and call verified APIs from any AI assistant, with free trial calls and previewed writes.
Query your books, company data, business health, and ship invoices from your AI assistant.
Ask your Quickbase apps in plain language. Read-only by default; writes need human approval.
Related MCP Servers
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with the Nimble REST API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.482 npmApache 2.0- AlicenseAqualityDmaintenanceEnables AI assistants to interact with SMB platform APIs for querying business data, managing tasks, accessing connectors, dashboards, and monitoring security.16MIT

Schematic MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage billing, plans, features, and entitlements via Schematic. Supports company lookup, plan management, feature creation, and override configuration through natural language.16 npm2MIT
Alternative Payments MCPofficial
AlicenseNot gradedqualityAmaintenanceProvides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.Apache 2.0