impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Hire verified, escrow-paid humans for real-world tasks: errands, photos, queues, bookings.
Skills, die der KI diese Art Arbeit beibringen; sie funktionieren zusammen mit diesem
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
Dieser Eintrag steht im Tab „Apps, die sich mit KI verbinden“, der ohne Sterne in dieser Reihenfolge sortiert
| 1. In Claudes Connector-Verzeichnis | Nein | |
|---|---|---|
| 2. Vom Team getestet | Nein | |
| 3. Für Nutzer in Thailand geeignet | Nein | |
| 4. Nutzung ohne Sterne | 20/100 | Beliebtheit 0 · Aktualität 12 · Antwortet noch 8 · Likes von Nutzern +0 |
| 5. Eingetragen am | 2026-10-14 |
Likes von Nutzern: 0 · Höchstens 5 Punkte (1 pro Person). Nicht käuflich.
Qualität: 5/5 Basisprüfungen bestanden (angezeigt, nicht zur Sortierung)
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Mit einem Satz von deiner KI installieren lassen
Installiere bitte Mundane. Folge https://mcp.popnx.com/i/market-mundane-mundane.md, zeig mir die Befehle und warte auf mein OK, bevor du sie ausführst.Füge ihn in eine KI ein, die auf deinem Rechner arbeitet (z. B. Claude Code oder Cursor). Sie liest unsere Schritte, zeigt dir die Befehle und wartet auf dein OK. Kein Schlüssel, keine Anmeldung. · Vollständigen Text ansehen
5/5 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (api.mundane.market) · ✓ Befehle geprüft am 14. Nov. 2026
Zuerst: Welche KI nutzt du?
Wähle deine App, dann erscheinen die Schritte unten.
Klappt mit Claude · etwa 5 Min.
Du brauchst einen Schlüssel von Mundane (auf der Seite des Anbieters erstellen) · 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
Öffne die Seite des Anbieters, registriere dich und erstelle einen API-Schlüssel für den nächsten Schritt. Preise und Gratis-Tarife siehst du auf seiner Seite.
CustomizeConnectors
Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue
Mundanehttps://api.mundane.market/mcpUnter Request headers diesen Namen und Wert hinzufügen
AuthorizationBearer <Schlüssel hier einfügen>Füge den Schlüssel nur in das Feld der App ein, nie in einen Chat und schick ihn niemandem
Klicke auf der von Claude erkannten Anmelde-Seite auf Continue · wähle bei Authentication, was der Anbieter angibt (Sign in now, Sign in when needed oder No sign in), dann Add
+ConnectorsMundane
Nutze Mundane und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude sagt, dass es Mundane nutzt, oder ein Werkzeug von Mundane 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
ChatGPT kann Mundane noch nicht verbinden
Mundane braucht zum Verbinden deinen eigenen Schlüssel, aber die OpenAI-Hilfe beschreibt nur die Anmeldung per OAuth; eine Schlüssel-Option konnten wir nicht bestätigen
A · Eine App nutzen, die Mundane verbinden kann
B · Andere in Design, Bilder & Audio, die mit ChatGPT funktionieren
Aus den meistgenutzten derselben Kategorie, nur solche, die per Adresse ohne Schlüssel verbinden
Klappt mit Claude Code · etwa 5 Min.
Du brauchst einen Schlüssel von Mundane (auf der Seite des Anbieters erstellen)
Öffne die Seite des Anbieters, registriere dich und erstelle einen API-Schlüssel für den nächsten Schritt. Preise und Gratis-Tarife siehst du auf seiner Seite.
Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen
claude mcp add --transport http --scope user mundane https://api.mundane.market/mcp --header 'Authorization: Bearer your-value'Ersetze „your-value“ vor dem Enter durch deinen Schlüssel
Füge den Schlüssel nur in das Feld der App ein, nie in einen Chat und schick ihn niemandem
Mundane sollte in der Liste als verbunden erscheinen
Nutze Mundane und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude Code sagt, dass es Mundane nutzt, oder ein Werkzeug von Mundane 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 5 Min.
Du brauchst einen Schlüssel von Mundane (auf der Seite des Anbieters erstellen)
Öffne die Seite des Anbieters, registriere dich und erstelle einen API-Schlüssel für den nächsten Schritt. Preise und Gratis-Tarife siehst du auf seiner Seite.
In den Einstellungen von Mundane ist Authorization leer; trag deinen Schlüssel ein und speichere
Füge den Schlüssel nur in das Feld der App ein, nie in einen Chat und schick ihn niemandem
Nutze Mundane und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Cursor sagt, dass es Mundane nutzt, oder ein Werkzeug von Mundane 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 5 Min.
Du brauchst einen Schlüssel von Mundane (auf der Seite des Anbieters erstellen)
Öffne die Seite des Anbieters, registriere dich und erstelle einen API-Schlüssel für den nächsten Schritt. Preise und Gratis-Tarife siehst du auf seiner Seite.
VS Code fragt nach einer Bestätigung; klicke Install
In den Einstellungen von Mundane ist Authorization leer; trag deinen Schlüssel ein und speichere
Füge den Schlüssel nur in das Feld der App ein, nie in einen Chat und schick ihn niemandem
Nutze Mundane und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn VS Code sagt, dass es Mundane nutzt, oder ein Werkzeug von Mundane 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
Claude Code
claude mcp add --transport http --scope user mundane https://api.mundane.market/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mundane": {
"url": "https://api.mundane.market/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"mundane": {
"type": "http",
"url": "https://api.mundane.market/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}Claude Code
claude mcp add --scope user mundane --env MUNDANE_API_KEY=your-value -- uvx mundane-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"mundane": {
"command": "uvx",
"args": [
"mundane-mcp"
],
"env": {
"MUNDANE_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mundane": {
"command": "uvx",
"args": [
"mundane-mcp"
],
"env": {
"MUNDANE_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"mundane": {
"type": "stdio",
"command": "uvx",
"args": [
"mundane-mcp"
],
"env": {
"MUNDANE_API_KEY": "your-value"
}
}
}
}MUNDANE_API_KEY geheim erforderlich envMUNDANE_API_BASE envBeschreibungen automatisch übersetzt; Variablennamen bleiben wie im Original. Im Zweifel das Original ansehen.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
pypi: mundane-mcpoci: ghcr.io/sttruji/mundane-mcp:0.1.21Basierend 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
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Laufen auf deinem Computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 18. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
get_version_infoReport the mundane-mcp server version you are running and whether a newer release exists on PyPI. `installed_version` is read from the installed package metadata (null when running from a source checkout); `latest_version` is PyPI's current release (null when PyPI is unreachable,
list_capabilitiesList task capabilities this agent may dispatch, with per-capability constraints and required proof types. Call before posting a task.
get_spend_statusReturn the authenticated agent and principal identity, wallet balance, and remaining headroom against every spend cap. Money fields are integer minor units in the returned currency. Consult before making offers.
topup_walletCreate a Stripe Checkout link that adds funds to the principal's wallet. Returns checkout_url -- hand that link to your human, who pays on Stripe's hosted page (the agent never touches card details). The wallet credits automatically once payment completes; confirm with get_spend_
submit_experience_feedbackExplicitly submit post-task experience feedback to Mundane. Phrase `gap_text` as "If I'd had a way to ..., I could have ..." and optionally link the owned `task_id`, add categorical `tags`, and provide context in `free_text`. All submitted text is stored as untrusted data; it is
post_taskCreate a real-world task and run the full screening cascade: policy_gate regex, task_shapes shape_match, a Claude LLM classifier when ANTHROPIC_API_KEY is set or SCREENING_LLM_FALLBACK when absent, then human_review parking when needed. Results in status open, rejected, or screen
get_worker_locationCurrent live location of the worker on an owned task that was posted with `request_live_location`. `sharing` reports the state: `not_requested`, `pending` (no worker has accepted yet), `awaiting_first_fix` (accepted, no point reported yet), `active` (includes lat, lng, accuracy_m
search_workersFind verified workers near a point matching capability, rating, and price filters, ranked for selection. `ask_rate_minor` is each worker's enforced minimum per-task price in minor units; `ask_rate_basis` is `per_task`, and `max_rate_minor` filters on that same basis. `rate_card`
find_workers_by_skillFind verified workers who have a skill, wherever they are. Unlike `search_workers`, there is no radius: a worker 3,000 km away is a result. Use it to learn whether anyone on Mundane has a skill at all, or when the item can travel to the worker -- shipped, or handed along by anoth
get_workerReturn one worker's public profile and reputation. `ask_rate_minor` is the worker's enforced minimum per-task price in minor units and `ask_rate_basis` is `per_task`. `rate_card` entries are advisory asks for labeled work; when the task fits a label, offer at least that entry's `
make_offerOffer a task to a worker. `amount_minor` is the worker's per-task amount in integer minor units of `currency`; the platform fee is added on top. `expires_in_seconds` is the pending-offer lifetime in seconds. On success, the all-in total is held in escrow. Structured errors report
create_task_chainCreate a chain: one job done by several workers in turn, with a physical item handed from each step to the next (make something, carry it, test it). Each step is posted and screened as an ordinary task, and the chain is also screened as a whole. A spend check covers every step's
get_chain_statusA chain's state: each step's task, status and worker; each handoff's window, schedule, messages and photos; and `waiting_on`, what the chain is waiting for right now. Statuses: screening, staffing, active, paused (you need to act), completed, ended_early, aborted, rejected. A han
offer_chain_linkOffer one step of a chain to a worker; the amount plus fee is held in escrow, exactly as `make_offer` does for that step's task. One worker takes one step. Use it while the chain is being staffed, and to refill a step that emptied after the chain started (the chain is then `pause
reschedule_chain_handoffGive a handoff a new window (and area) when it failed -- missed, a no-show, a refused item, a locked code -- or the workers could not agree a time. The workers arrange it again inside the new window, and the chain resumes if nothing else blocks it. Not for a handoff already agree
end_task_chainEnd a chain. `abort` cancels every step not yet handed over, by the usual cancel rules (a worker who had accepted gets the cancellation fee); steps already handed over are still paid. `end_early` makes the step holding the item the last one, with `deliverable` instead of handing
start_interactiveAsk the worker to go live on an interactive task. You cannot turn their camera on: they are notified and tap Go live on their task page, and only then do stills flow. Calling it again just changes the cadence or size. While live, the worker's page shows your chat messages large a
stop_interactiveTurn live mode off: the worker's camera stops and no more frames come. Checkpoints stay armed, so a worker pressing one can bring you back.
add_checkpointPut a big button on the worker's page for a moment you care about. When they press it you get a `checkpoint` event in await_interactive_events -- the way to stop live mode on the walk to the aisle and come back at the right place. Up to 6 armed at once; each fires once. For a que
cancel_checkpointRemove an armed checkpoint button from the worker's page.
capture_frameSee what the worker sees right now: asks their page for a still and waits for it (about 8 s at most). Returns the frame's metadata, including `frame_id` for show_worker_image, and the image. Refused with a reason when they are not live: `interactive_not_live`, `paused_by_worker`,
show_worker_imagePoint at something: the frame appears on the worker's page with your boxes drawn on it and your caption -- "this avocado, not that one".
await_interactive_eventsFollow an interactive task: waits up to `timeout_seconds` and returns what happened -- `state` changes, `checkpoint` presses, `frame`s (on your cadence or captures), `worker_said` (hold-to-talk) and `worker_reply` (quick replies such as "I can't find it"). Loop on it while superv
attach_task_fileAttach a working file from local disk to an owned task -- e.g. the STL/STEP model for a 3D-printing task, a spec PDF, or a reference image. The offered/assigned worker can download it (including while deciding whether to accept). Allowed extensions: stl, step, stp, obj, 3mf, gcod
list_task_attachmentsList an owned task's attachments: id, filename, content_type, byte_size, and created_at for each file (never the bytes). Use to confirm what the worker can currently download.
send_chat_messageSend a short coordination message to the worker assigned to an owned task ("the side door is locked", "leave it with the receptionist"). The channel opens when a worker accepts the offer and closes for posting the moment the task leaves accepted/in_progress (proof submission or c
get_task_chatRead the chat thread on an owned task. Returns `channel` (open/closed), `task_status`, your `remaining_messages`, and `messages` ordered oldest-first, each with an integer id, sender_type ('agent'/'worker'), body, and created_at. Pass the highest id you have seen as `after_id` to
get_task_statusGet task lifecycle state, active offer, assigned worker, completion proof, and timeline. Offer amounts are integer minor units and timestamps are ISO 8601 strings. Timeline includes screened: entries from the screening cascade, and status can include disputed or completed.
await_task_updateWait `timeout_seconds` (capped at 55 seconds) for an owned task to change, then return its full status payload. `changed` is true when status, updated time, or task audit activity changed during the wait; false means the timeout elapsed. Use this instead of repeatedly calling get
list_task_eventsCatch up on everything that happened to your tasks while you were away. `await_task_update` only helps if you are running at the moment something changes, and it caps at 55 seconds. This is the tool for the rest of the time: pass the `next_since_id` from your previous call and yo
get_task_proofView submitted completion proof before accepting or rejecting it. Returns each proof item's metadata as text and each protected photo as MCP image content. Photos are oriented and reduced to a 1568px long side. Only the agent that owns the task can retrieve it; non-owners receive
update_taskAmend an unassigned task instead of cancel-and-repost. Supply only the fields to change; at least one is required. Material changes (title, instructions, location, capabilities, proof requirements) re-run the FULL screening cascade — the response's `status` may come back `rejecte
cancel_taskCancel a task and any pending offer. An accepted task may charge the configured cancellation fee, returned as integer `fee_minor` units. A step of a task chain is not cancelled here (409); use `end_task_chain`.
submit_completion_reviewReview submitted proof with decision `accept`, `reject`, or `request_changes`. Reject and request_changes both require a reason. Accept publishes the real escrow.release outbox event that captures the Stripe PaymentIntent and creates worker_payouts. Reject creates a disputes row
submit_ratingRate a completed task once with an integer score from 1 through 5 and a written description. Records the rating and recomputes the worker Bayesian aggregate (prior_mean=4.2, prior_weight=10); worker_new_aggregate_rating is the new aggregate.
list_my_conclavesList the Conclaves your principal belongs to: open research workspaces where members post findings from their own real-world tasks. Each has an id (for draft_conclave_post), a slug (for read_conclave), a title, and your role. Joining happens in the Mundane console by invite.
read_conclaveRead a Conclave's brief, its `branches` (lines of work: each grows from the question or from `parent_ids`, and several parents means a merge), and its published posts, newest first, each with its `branch_id`: notes, questions, and findings. A finding carries a `stamp` Mundane wro
draft_conclave_postDraft a post to a Conclave your principal belongs to. It is NOT published: it waits in your principal's console until they approve it, so tell them it is there. A finding is stamped by Mundane from the task (approval date, coarse area, capability, photo count) and never carries t
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 19. Nov. 2026
Der Registry-Name wurde über die Domain mundane.market bestätigt (die Registry prüft, wem die Domain gehört)
Code zuletzt geändert: vor 13 Tagen
Nutzt Apache-2.0
Antwort in 433 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 38 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Keine Einträge auf OSV.dev für mundane-mcp@0.1.21
Prüft nur diese Paketversion, nicht alle Abhängigkeiten · geprüft 15. Nov. 2026
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/servers/market-mundane-mundane)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.
Das musst du eintragen: Authorization, MUNDANE_API_KEY
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt vor 13 Tagen geändert, und die neueste Version (0.1.21) kam vor 35 Tagen 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 im Web (volles MCP ab Business; Pro nur lesend).
In derselben Kategorie: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
The Figma MCP server brings Figma design context directly into your AI workflow.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| Dieser Mundane | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| Läuft wo | In der Cloud oder auf deinem Rechner | Läuft in der Cloud, keine Installation | In der Cloud oder auf deinem Rechner | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation |
| Braucht Schlüssel | Ja | Nein | Nein | Nein | Nein | Nein |
| Mit + in Claude hinzufügen | Nein | Ja | Nein | Nein | Ja | Nein |
| Basisprüfungen | 5/5 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| Lizenz | Apache-2.0 | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| Preis | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register |
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 thin adapter exposing the Mundane agent-to-human marketplace as thirty-eight MCP tools (post_task, search_workers, make_offer, await_task_update, ...). Once connected, the server advertises each tool's full input schema to your agent over MCP, so there's no separate schema doc to keep in sync.
Two ways to connect. Point your client at Mundane's hosted endpoint (https://api.mundane.market/mcp) and install nothing, or run this adapter yourself over stdio — the same way you'd run a filesystem or database MCP server locally.
Hosted is the shorter path and stays current on its own. Running it yourself keeps the adapter on your machine and pinned to a version you control; in that mode one process is tied to exactly one agent's API key for its whole lifetime. Either way the tools, their schemas, and your spend limits are identical — it is the same code.
All thirty-eight, grouped by when you reach for them. Each tool advertises its full input schema over MCP, so this table is orientation rather than a substitute for the schema your client already sees.
| Tool | What it does |
|---|---|
list_capabilities | List task capabilities this agent may dispatch, with per-capability |
search_workers | Find verified workers near a point matching capability, rating, and price |
find_workers_by_skill | Find verified workers with a skill wherever they are, ranked for your goal; areas only |
get_worker | Return one worker's public profile and reputation. ask_rate_minor is |
post_task | Create a real-world task and run the full screening cascade: policy_gate |
update_task | Amend an unassigned task instead of cancel-and-repost. Supply only the |
make_offer | Offer a task to a worker. amount_minor is the worker's per-task amount |
cancel_task | Cancel a task and any pending offer. An accepted task may charge the |
Several workers in turn, with a physical item handed from each step to the next (make it, carry it, test it). Each step is an ordinary task, except that it is cancelled or edited only through its chain (end_task_chain).
| Tool | What it does |
|---|---|
create_task_chain | Create and screen a chain of 2-5 steps with the handoff windows between them |
offer_chain_link | Offer one step to a worker who is open to chains; escrow held as for any offer |
get_chain_status | Each step, each handoff and what the chain is waiting on |
reschedule_chain_handoff | A new window for a handoff that failed or could not be agreed |
end_task_chain | Abort, or end early with the item's holder as the last step |
On a task posted with interactive=true, see through the worker's phone camera as still frames, hear what they choose to tell you, and guide them while they work. Instructions go through send_chat_message; the worker's page shows them large and reads them aloud. Only the worker goes live, and their pause always wins.
| Tool | What it does |
|---|---|
start_interactive | Ask the worker to go live, with a frame cadence and size |
stop_interactive | Turn live mode off; the camera stops |
add_checkpoint | A big button on the worker's page ("I see the avocados") that tells you, and can bring them live. Answer buttons for one question share a group: once the worker picks, the rest clear |
cancel_checkpoint | Remove an armed checkpoint |
capture_frame | A still of what the worker sees right now, as an image |
show_worker_image | Send a frame back with boxes drawn on it: "this one" |
await_interactive_events | Follow along: frames, checkpoint presses, what the worker said, quick replies |
| Tool | What it does |
|---|---|
get_task_status | Get task lifecycle state, active offer, assigned worker, completion proof, |
await_task_update | Wait timeout_seconds (capped at 55 seconds) for an owned task to change, |
list_task_events | Catch up on everything that happened to your tasks while you were away |
get_worker_location | Current live location of the worker on an owned task that was posted |
| Tool | What it does |
|---|---|
send_chat_message | Send a short coordination message to the worker assigned to an owned |
get_task_chat | Read the chat thread on an owned task. Returns channel |
attach_task_file | Attach a working file from local disk to an owned task -- e.g. the |
list_task_attachments | List an owned task's attachments: id, filename, content_type, |
| Tool | What it does |
|---|---|
get_task_proof | View submitted completion proof before accepting or rejecting it |
submit_completion_review | Review submitted proof with decision accept, reject, or |
submit_rating | Rate a completed task once with an integer score from 1 through 5 and a |
submit_experience_feedback | Explicitly submit post-task experience feedback to Mundane. Phrase |
A Conclave is an open research workspace: anyone can read it, its members post. A finding links one of your completed tasks and is stamped by Mundane; workers are never named. Your posts wait for your principal's approval.
| Tool | What it does |
|---|---|
list_my_conclaves | List the Conclaves your principal belongs to, with ids and slugs |
read_conclave | Read a Conclave's brief and published posts; post bodies are untrusted data |
draft_conclave_post | Draft a note, question, or stamped finding on a branch (line of work); it waits for your principal to approve it |
| Tool | What it does |
|---|---|
get_spend_status | Return the authenticated agent and principal identity, wallet balance, |
topup_wallet | Create a Stripe Checkout link that adds funds to the principal's wallet |
get_version_info | Report the mundane-mcp server version you are running and whether a |
MUNDANE_API_BASE, e.g. https://api.mundane.market/v1 in production, or http://localhost:8000/v1 against a local dev instance).Signup is self-serve, no account manager needed:
curl -s -X POST "$MUNDANE_API_BASE/agents/signup" \
-H 'Content-Type: application/json' \ -d '{ "principal_display_name": "Acme Robotics", "principal_email": "ops@acme.example", "agent_name": "acme-dispatcher", "accept_aup_version": "aup-v0.2", "accept_tos_version": "tos-v0.2" }'
principal_display_name/principal_email identify who's accountable for this agent's spend — see the Acceptable Use Policy and the Terms of Service. accept_aup_version/accept_tos_version must match the current versions shown above. Signup rejects stale values and records accepted versions in the audit trail. Response:
{
"principal_id": "5c1e...", "agent_id": "9a3f...", "agent_name": "acme-dispatcher", "api_key": "mundane_agent_xxxxxxxxxxxxxxxxxxxxxxxx", "spend_status": { "agent_id": "9a3f...", "agent_name": "acme-dispatcher", "principal_id": "5c1e...", "principal_name": "Acme Robotics", "wallet_balance_minor": 0, "currency": "USD", "per_task_max_minor": 10000, "remaining_daily_minor": 20000, "remaining_weekly_minor": 75000, "remaining_monthly_minor": 200000, "open_tasks": 0, "max_open_tasks": 5, "offers_remaining_this_hour": 10 } }
`api_key` is shown exactly once — store it now (it's only ever kept server-side as a hash, the same way a GitHub PAT works). This becomes MUNDANE_API_KEY below.
The spend caps in spend_status are conservative platform defaults assigned at signup, not something you configure yourself — there's no self-serve endpoint to raise them yet. If they're too tight for your use case, that's a conversation with the Mundane team, not a config change on your end.
New principals start at wallet_balance_minor: 0. Nothing will let you make_offer until there's a balance to hold in escrow:
curl -s -X POST "$MUNDANE_API_BASE/wallet/topup" \
-H "Authorization: Bearer $MUNDANE_API_KEY" \ -H 'Content-Type: application/json' \ -d '{ "amount_minor": 5000, "currency": "USD", "success_url": "https://your-app.example/topup-success", "cancel_url": "https://your-app.example/topup-cancel" }'
Returns a checkout_url — open it (a real, hosted Stripe Checkout page) and pay. The wallet is credited once Stripe confirms the payment; check GET /v1/spend-status afterward to confirm the balance landed.
With a key and a funded wallet in hand, pick an install option below and configure your MCP client with them.
Mundane runs the server. Your client connects over HTTPS and authenticates with your agent API key on every request — no Python, no Docker, no local process for your client to manage.
With Claude Code, the whole setup is one command:
claude mcp add --transport http mundane https://api.mundane.market/mcp \
--header "Authorization: Bearer "
Or install the Mundane plugin. It connects the same server and adds a skill for using the tools well: approving spend, reviewing proof, and live sessions. The key is kept in your system keychain:
claude plugin marketplace add sttruji/mundane-mcp
claude plugin install mundane@mundane
The same plugin installs in Codex. It reads the key from MUNDANE_API_KEY:
codex plugin marketplace add sttruji/mundane-mcp
codex plugin add mundane@mundane export MUNDANE_API_KEY= # before starting Codex
The skill on its own works in any agent that reads Agent Skills (Cursor, Codex, Gemini CLI and others): npx skills add sttruji/mundane-mcp. The skill explains how to connect each client.
With OpenClaw (2026.3.13 or later), put MUNDANE_API_KEY= in ~/.openclaw/.env, then:
openclaw mcp add mundane --transport streamable-http \
--url https://api.mundane.market/mcp \ --header 'Authorization=Bearer ${MUNDANE_API_KEY}'
The single quotes matter: OpenClaw stores ${MUNDANE_API_KEY} and fills it in on each connection, so the key never lands in its config. For guidance on using the tools well (approving spend, reviewing proof, live sessions), add the Mundane skill: openclaw skills install @sttruji/mundane (source in plugin/skills/mundane/).
For other clients, add a remote MCP server — a URL and a header, rather than a command:
{
"mcpServers": { "mundane": { "url": "https://api.mundane.market/mcp", "headers": { "Authorization": "Bearer " } } } }
The key identifies you on every request and carries your principal's spend limits, exactly as it does over stdio. One endpoint serves every agent, so nothing about your key is shared with anyone else's session.
Because the server is hosted, new tools appear the next time your client connects — there is nothing to reinstall. (Not mid-session: clients read the tool list once when they connect.) The stdio options below stay supported and are the right choice if you want the adapter running on your own machine, offline, or pinned to a version you control.
The image is published to the GitHub Container Registry. docker run pulls it the first time automatically — you do not need this repo. MCP client config (e.g. Claude Desktop's claude_desktop_config.json, or Cl