Puter MCP
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
Valem - Deterministic reactive state models. Create your own calculators/forms with AI
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
5/5 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (valem.run)
Zuerst: Welche KI nutzt du?
Wähle deine App, dann erscheinen die Schritte unten.
Klappt mit Claude · etwa 2 Min.
Kein Schlüssel, nichts zu installieren · Einmal auf claude.ai oder in der Desktop-App einrichten, dann im Chat nutzen · kostenlose Konten können 1 hinzufügen · bei Team/Enterprise fügt ein Owner ihn hinzu
CustomizeConnectors
Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue
Valemhttps://valem.run/mcpAuthentication so lassen, wie Claude es erkannt hat, dann Add klicken
+ConnectorsValem
Nutze Valem und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude sagt, dass es Valem nutzt, oder ein Werkzeug von Valem in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit ChatGPT nur in Firmen-Tarifen
ChatGPT Business, Enterprise oder Edu im Web, hinzugefügt von Admin oder Inhaber des Workspace · Mit Free, Plus oder Pro: Dein ChatGPT-Tarif kann MCP noch nicht selbst verbinden
Plugins+Add custom MCP server
Namen eingeben, Adresse unter Connection einfügen, Risikohinweis abhaken und Create as a plugin klicken
Valemhttps://valem.run/mcpNeuen Chat öffnen und vor dem Tippen Valem aus deinen Plugins wählen
Nutze Valem und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn ChatGPT sagt, dass es Valem nutzt, oder ein Werkzeug von Valem in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von OpenAI abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit Claude Code · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen
claude mcp add --transport http --scope user valem https://valem.run/mcpValem sollte in der Liste als verbunden erscheinen
Nutze Valem und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude Code sagt, dass es Valem nutzt, oder ein Werkzeug von Valem in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit Cursor · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
Nutze Valem und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Cursor sagt, dass es Valem nutzt, oder ein Werkzeug von Valem in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Cursor abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit VS Code · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
VS Code fragt nach einer Bestätigung; klicke Install
Nutze Valem und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn VS Code sagt, dass es Valem nutzt, oder ein Werkzeug von Valem in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von VS Code abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Andere Apps mit MCP, etwa Windsurf, Zed oder Gemini CLI, fügen Server unterschiedlich hinzu. Sieh in der App-Liste nach
Adresse für Apps, die über das Web verbinden
https://valem.run/mcpJSON-Einstellungen stehen unten unter „Für Entwickler“
Claude Code
claude mcp add --transport http --scope user valem https://valem.run/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"valem": {
"url": "https://valem.run/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"valem": {
"type": "http",
"url": "https://valem.run/mcp"
}
}
}Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.
Verbinden sich über das Internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 10. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
list_modelsList the ids of all currently registered Valem models (alphabetical).
create_modelCreate a new model from a declarative ModelSpec. The spec carries the JSON schema plus derivations (computed fields), constraints (invariants), and optional effects. Returns the created id. Fails (isError) on an invalid spec. If the requested id is already taken, a numeric postfi
get_model_infoGet summary info for a model: id, version, and derivation/meta/constraint/effect counts.
get_specGet the full stored ModelSpec JSON for a model.
get_libraryList the JSONata functions and values a model's library exports — what an expression in this model may call, with signature, arity and originating layer. Call it before writing an expression so you reuse the model's existing vocabulary instead of re-deriving it. Returns null when
get_stateGet a model's merged state (base fields plus all computed derived fields). On a large model this is the biggest context cost — narrow it: pass 'paths' to project only specific subtrees (canonical addresses, each spliced back into a pruned document at its address), and/or 'depth'
get_fieldGet the value of a single field by its JSON Path address (e.g. "$.order.total"). Evaluates a LAZY derivation on demand.
mutateApply field mutations to a model and run the reactive pipeline (derivations recompute, constraints enforce, effects dispatch). 'mutations' is a flat map keyed by canonical JSON Path address, e.g. {"$.order.qty": 3}. A ROLLBACK constraint violation returns isError with the structu
patch_modelApply an RFC 6902 JSON Patch document to a model and run the reactive pipeline. Unlike 'mutate' (a flat address→value map), a patch expresses array insert/remove/move and test/copy ops, e.g. [{"op":"add","path":"/order/items/-","value":{...}}, {"op":"remove","path":"/order/items/
get_effective_schemaGet the effective JSON Schema for a field: the static schema overlaid with LIVE meta-derived constraints (current min/max/required/…). Check this BEFORE writing a value to learn what the reactive pipeline will accept, instead of discovering an invalid mutation only by trying it a
snapshotCapture an immutable point-in-time snapshot of a model's state (base document + derived/meta caches). A natural safety step before a risky evolve_spec: keep the returned snapshot and, if the change goes wrong, hand it back to 'restore' to roll the state back.
restoreRestore a model's state from a snapshot previously returned by 'snapshot' (pass it back verbatim as 'snapshot'). Overwrites the model's current base state. The snapshot must be for the same model.
explainExplain why a field is what it is: returns the recent derivation/constraint trace records for a path from the in-memory ring buffer (inputs, expression, result). For a constraint use the synthetic path "$constraint: ". Trace records can be bulky — pass 'limit' to return only the
get_historyList the ISO-8601 timestamps of a model's committed mutations (most recent 100).
get_auditQuery a model's durable, append-only audit trail (newest-first): one record per committed reactive cycle (mutations, derivedUpdated, traces, flaggedConstraints, dispatchedEffects, source, sequence). This is the queryable superset of get_history/explain — it survives the in-memory
verify_auditVerify the tamper-evidence hash chain of a model's durable audit trail. Returns {valid, recordsChecked, firstBrokenSequence, detail}; a false 'valid' points at the first altered/reordered/deleted record. (Embedded mode has no hash chain and reports valid.)
upload_blobStore binary content (base64-encoded in 'data') in the content-addressed blob store and get back a BlobRef {$blobId, $mediaType, $bytes} to embed in a model's binary field. Storage is content-addressed (SHA-256), so uploading identical bytes returns the same $blobId.
download_blobFetch a blob's bytes by id, base64-encoded in the result. Pass 'modelId' to fetch a blob referenced by a specific model (access-scoped); omit it for a direct store fetch. Large blobs may exceed the result-size limit — this channel suits small binaries only.
evolve_specApply an incremental SpecEvolution diff to a model, preserving live state. Returns the new version. Fails (isError) if the evolved spec is invalid, if expectedVersion no longer matches, or if a schema change would strand existing state. Prefer targeted diffs (upsertSchemaNodes/up
delete_modelRemove a model from the registry. Fails (isError) if the model does not exist.
get_viewEvaluate a model's embedded view definition against current state and return the resolved component tree. Pass an optional 'viewId' for a named view; omit for the default view.
get_domain_guidanceGet vetted instructions for the hard modelling shapes this domain involves (progressive tax/fee charges, per-period schedules, classification, date math, group-by, …). Read the model description in ANY language, pick the matching topic ids, and call this BEFORE authoring the spec
validate_specValidate a ModelSpec WITHOUT creating it: returns a 'valid' flag plus structured findings (errors + warnings, each with a location and message). Use this to iterate on a draft — fix the reported errors, re-validate — before committing with create_model.
eval_expressionEvaluate a single JSONata expression against a sample input document and return the computed value, or the exact compile/eval error. Write the expr exactly as in a derivation/constraint 'expr': bare dot-paths, no leading $ (e.g. "loan.amount * loan.annualRate / 1200"). Use this t
test_specRun a spec's embedded test cases (or ad-hoc given->expect cases) through the real reactive pipeline in a throwaway runtime, returning pass/fail plus per-field failures (path, expected, actual). Use this to certify domain behavior before create_model / promotion.
dry_runCompile a candidate ModelSpec in an ISOLATED throwaway runtime, apply optional sample mutations, and return the resulting merged state (base + derived) — WITHOUT registering it in the live registry. Use this to preview the full reactive cascade of a draft spec.
convert_spreadsheetCompile an uploaded .xlsx workbook's OWN formulas into a ready ModelSpec — deterministic transpilation (Excel formula language -> JSONata), never an LLM call: every number the compiled spec computes is checked to exactly match what the source workbook itself computed. One workshe
search_documentDeterministic, LLM-free search over an uploaded PDF/DOCX: ranks the document's pages/sections against your query (term-overlap, no embedding model, no network call) and returns the top matches with page/section citations and verbatim quotes. Cost is bounded by topK, never by docu
pair_browserPair this MCP session with a browser tab on the hosted Valem sandbox so both drive the same live model session. Mints a pairing on first call (or resumes an existing not-yet-approved one) and waits up to a minute for the developer to approve it. Returns {status:"paired"|"already_
valem_spec_guideHow to write a Valem ModelSpec that render_model accepts: sections, path notation, JSONata rules, view components and common mistakes. Call this once before writing your first spec in a conversation.
render_modelShow the user a Valem model as an interactive card they can edit in the chat: a form whose computed fields update on every change, checked by a deterministic engine. Use it when the user asks for a calculator, quote, budget, planner, pricing or any model with inputs and computed
explain_valueExplain how a value in a Valem card was computed: the formula, the values it read and the inputs it ultimately comes from, as Valem's engine has them for the given inputs. Use it when the user asks why a number is what it is. Pass the specHash and current inputs from the latest r
valem_recomputeCalled by the Valem card when the user edits an input. Not for direct use: call render_model instead.
show_modelShow the user one of this server's models (created with create_model) as an interactive card in the chat. Every edit the user makes in the card is a mutate on the model, so get_state and explain see it. Use it after create_model or evolve_spec when the user should see or try the
valem_card_editCalled by the Valem card when the user edits a stored model. Not for direct use: call mutate instead.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 12. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto vlad-public-code bestätigt, dem das Repo gehört
Code zuletzt geändert: vor 10 Tagen
Nutzt Apache-2.0
Antwort in 178 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 35 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.
Noch keine Bewertungen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 5 von 5 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt vor 10 Tagen geändert, und die neueste Version (1.0.0) kam vor 3 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL und funktioniert daher auch in Apps mit Remote-MCP, etwa ChatGPT Business und höher.
In derselben Kategorie: Puter MCP, XcodeBuildMCP, XcodeBuildMCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
A spreadsheet engine for AI agents. An LLM describes a domain as a JSON spec (fields, formulas, invariants); Valem compiles it into a live model that recomputes every dependent value on each change, refuses changes that break a rule, and can explain why any number is what it is.
LLMs are good at *describing* a domain and bad at *keeping state consistent* over it. Ask one to maintain a quote, an order, or a loan application across twenty turns and the total drifts from its line items, a limit checked three messages ago is forgotten, and arithmetic is off by a rounding step.
Valem moves the rules out of the conversation and into a deterministic runtime:
The agent writes the spec; Valem validates it, tests it, and keeps it true.
In the browser, no install. Open valem.run, describe a model in plain words ("a mortgage with overpayments", "an invoice with VAT and discounts"), then type into the live form and watch every derived value update.
From your agent (MCP, hosted, nothing to download):
# Claude Code
claude mcp add --transport http valem https://valem.run/mcp
Claude Desktop: Settings → Connectors → *Add custom connector* → https://valem.run/mcp. Then ask the agent to call pair_browser and it will build models you see live in a browser tab. The authoring tools (validate_spec, eval_expression, test_spec, dry_run) work without pairing. Guide: Connect your agent.
Self-hosted with Docker:
docker run --rm -p 8080:8080 ghcr.io/vlad-public-code/valem:latest
{
"id": "order", "version": "1.0.0", "schema": {}, "derivations": [ { "path": "$.order.items[*].lineTotal", "expr": "$parent.qty * $parent.price" }, { "path": "$.order.total", "expr": "$sum(order.items.(qty * price))" } ], "constraints": [ { "id": "max-order", "expr": "order.total <= 5000", "message": "Order exceeds the cap", "policy": "rollback" } ] }
Write qty on any line item and lineTotal and total recompute; a write that pushes the total over 5,000 is rejected before it commits. Full format: ModelSpec reference.
| You want | Use |
|---|---|
| An agent that maintains structured state | The MCP server, hosted (valem.run/mcp) or self-hosted (stdio jar from Releases) |
| A backend shared by many clients | valem-web: REST + WebSocket, pluggable storage (filesystem, Postgres, Mongo, Redis, S3) |
| The engine inside your JVM app | Embed valem-core/valem-service |
| Scripting with no server | The JSON console (one JSON command per line on stdin) |
| A live model inside your web page | Embed a live model |
Clients: TypeScript and Java SDKs.
Published at [valem.run/docs](https://valem.run/docs/) (source in docs/), organised in six chapters: Getting started, Usage scenarios, Model guide, Reference, Deployment, Extending. Good first reads:
valem.* propertyThe console app is the fastest way to use Valem from a script or an AI agent. It reads one JSON command per line from stdin and writes one JSON response per line to stdout. No HTTP, no browser, no server process. All state is held in memory for the lifetime of the process.
# Build the fat jar (first time)
mvn install -pl valem-core,valem-service -q mvn package -pl valem-console -q
java -jar valem-console/target/valem-console-1.0.0-SNAPSHOT.jar
echo '{"cmd":"list-models"}' | java -jar valem-console/target/valem-console-1.0.0-SNAPSHOT.jar
Example session:
// stdin
{"cmd":"create-model","spec":{"id":"order","version":"1.0.0","schema":{},"derivations":[{"path":"$.total","expr":"subtotal + tax"}]}} {"cmd":"mutate","id":"order","mutations":{"$.subtotal":100,"$.tax":8}} {"cmd":"get-state","id":"order"}
// stdout {"ok":true,"result":{"id":"order","status":"created"}} {"ok":true,"result":{"success":true,"mutatedPaths":["$.subtotal","$.tax"],"derivedUpdated":["$.total"],...}} {"ok":true,"result":{"subtotal":100,"tax":8,"total":108}}
Full command list: console JSON protocol.
# From the repo root — build and start the Spring Boot server on port 8080.
mvn install -pl valem-core,valem-service -q mvn spring-boot:run -pl valem-web
The API is now available at http://localhost:8080, with the management UI served at /. Storage is in-memory by default; other backends are à-la-carte adapter jars (mvn -Pweb-postgres -pl valem-web package, then --valem.storage.type=postgres) — see configuration.md. For durable setups, persistence layout, and the hardening checklist see operations.md.
To enable LLM-powered spec generation, configure a provider before starting (the key is read from valem.llm.api-key, settable as VALEM_LLM_API_KEY; there is no provider-specific env fallback):
# Anthropic (default provider)
export VALEM_LLM_API_KEY=sk-ant-... mvn spring-boot:run -pl valem-web
VALEM_LLM_PROVIDER=openai VALEM_LLM_MODEL=gpt-4o \ VALEM_LLM_API_KEY=$OPENAI_API_KEY mvn spring-boot:run -pl valem-web
ollama serve first)VALEM_LLM_PROVIDER=ollama VALEM_LLM_MODEL=llama3 mvn spring-boot:run -pl valem-web
Without any provider configured the server starts normally; the /models/generate* endpoints return 503. All LLM knobs (providers, tool budgets, retries, temperatures): configuration.md.
In a separate terminal:
cd valem-ui
npm install # first time only npm run dev
Open http://localhost:5173 in your browser.
The UI proxies all /models and /blobs requests (including WebSocket connections) to the backend, which must be running.
The UI's ✦ Generate button drives a human-in-the-loop workflow: enter a model ID and a plain-text domain description → Preview Prompt (editable) → send to the LLM → review/edit the generated spec → Register Model. The same workflow is available over REST (POST /models/generate/preview → /models/generate → /models).
See generating-specs-with-llm.md for the workflow and provider setup, and llm-prompts.md for the exact prompts and the validate-and-repair loop.
# Create a model
curl -s -X POST http://localhost:8080/models \ -H 'Content-Type: application/json' \ -d '{ "id": "order", "version": "1.0.0", "schema": {}, "derivations": [ { "path": "$.order.total", "expr": "order.subtotal + order.tax" } ], "constraints": [ { "id": "max-order", "expr": "order.total <= 5000", "message": "Order exceeds the cap", "policy": "rollback" } ] }'
curl -s -X POST http://localhost:8080/models/order/mutations \ -H 'Content-Type: application/json' \ -d '{ "$.order.subtotal": 200, "$.order.tax": 20 }'
curl -s http://localhost:8080/models/order/state | python -m json.tool
Every endpoint (audit, snapshots, views, blobs, spec evolution, composition, …): api-reference.md.
# All modules
mvn test
mvn test -pl valem-core
The valem-e2e module contains Playwright browser tests that drive the full stack (backend + UI).
Prerequisites: the backend must be running on port 8080 (see Running the backend). The UI dev server is started automatically by Playwright.
cd valem-e2e
npm install # first time only npx playwright install # download browser binaries (first time only)
npm test # headless Chromium npm run test:headed # watch the browser npm run test:ui # Playwright interactive UI mode npm run report # open the last HTML report
Apache-2.0 — see LICENSE.