sapiom/mcp

Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.

Connector by sapiom · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 21

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sapiom-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.

Use cases: agent-orchestration

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools: 7 read · 12 write · 2 delete · 6 not yet classified
Secrets: None asked for
Install scripts: None found
Runs as: Node.js package

Tools by what they do 27

Read from the source code; the running server may list different tools.

Read 7 · Look things up without changing anything.

sapiom_dev_agents_check
sapiom_dev_agents_cron_preview
sapiom_dev_agents_inspect
sapiom_dev_agents_link
sapiom_dev_app_list
sapiom_dev_sandbox_check
sapiom_status

Write 12 · Create, change, send or run things.

sapiom_authenticate
sapiom_dev_agents_clone
sapiom_dev_agents_deploy
sapiom_dev_agents_run
sapiom_dev_agents_run_local
sapiom_dev_agents_schedule
sapiom_dev_agents_schedule_cancel
sapiom_dev_agents_schedule_inspect
sapiom_dev_agents_schedule_secret
sapiom_dev_app_publish
sapiom_dev_sandbox_configure
sapiom_send_feedback

Delete 2 · Delete, drop, revoke or wipe things.

sapiom_dev_app_delete
sapiom_logout

Not yet classified 6 · We could not tell from the name and description.

sapiom_dev_agents_emit_event
sapiom_dev_agents_scaffold
sapiom_dev_agents_signal
sapiom_dev_app_settings
sapiom_dev_map
sapiom_dev_sandbox_preview

Network hosts it talks to 7

api.sapiom.ai · found in code
api.sapiom.dev · found in code
app.sapiom.ai · found in code
app.sapiom.dev · found in code
apps.sapiom.ai · found in code
docs.sapiom.ai · found in code
github.com · found in code

Files it touches

Your home directory (~)
Any path the agent passes to its tools

Tools (27)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

sapiom_authenticate
Authenticate this local Sapiom developer MCP (sapiom-dev) by opening a browser login flow. Run this when a networked agent tool (link/deploy/run/inspect/signal) reports that authentication is required.
sapiom_dev_agents_check
Validate an agent locally: typecheck, bundle and import index.ts, derive the manifest, and check the step graph. Needs no Sapiom account or service call to validate; author-written top-level side effects still run when the definition is imported. Returns the agent name, step count, the manifest (which contains the full step graph for visualization), and any warnings — graph warnings, plus one per project file (AGENTS.md, the sapiom-agent-authoring skill) whose platform-rules stamp differs from the copy the Sapiom API currently serves, from a best-effort anonymous read of that endpoint's header…
sapiom_dev_agents_clone
Materialize a Sapiom agent locally. Given a template id (from the gallery) it forks the template into a repo you own; given an existing fork id it re-clones that fork; given a deployed agent's definitionId it clones the engine's live build-repo source directly (no fork step, always current) and pre-links the checkout. Either way it mints a short-lived, repo-scoped clone credential, git-clones the repo into <dir>, and writes sapiom.json recording the provenance. After cloning: read the project's AGENTS.md, install its dependencies, then _check → _run_local. Before cloud work, authenticate and r…
sapiom_dev_agents_cron_preview
Validate a cron expression and preview its next occurrences, creating nothing. Use before sapiom_dev_agents_schedule to confirm a cron + timezone fire when you expect (cron syntax is easy to get subtly wrong).
sapiom_dev_agents_deploy
Deploy the linked agent: bundle the current local source (including uncommitted source), push a synthesized build tree, trigger a metered cloud build, and wait for it to finish. The project must be linked (sapiom.json) and a git repo with at least one commit.
sapiom_dev_agents_emit_event
Emit one custom event for this tenant. It fans out by type to every active 'event' trigger the tenant armed and starts 0..N NEW runs; it never resumes a paused run (use sapiom_dev_agents_signal for that). Events start, signals resume. Returns { receiptId, outcome: 'matched' | 'unmatched', duplicate, fireIds }: 'unmatched' is a success, not an error — it means nothing subscribes to this type, so check it for a typo or arm a trigger with sapiom_dev_agents_schedule (kind 'event'). `fireIds` are trigger fires, not execution ids; read the receipt to get from a fire to the run it started. Pass id to…
sapiom_dev_agents_inspect
Inspect a cloud execution (its steps and errors) by executionId, a build by buildRunId, or list recent executions when neither is given. On a failed step, pull its input here to reproduce the failure locally with run_local. When inspecting an execution, the result includes a `webappUrl` to open that run in the webapp. By default the execution is returned COMPACT: identity/status/timestamps + a per-step summary (name/order/attempt/status/error-message) with a `has` flag-set and a `sizes` hint (char counts of the omitted input/output/logs/events/sharedState bodies). Full step bodies are NOT inc…
sapiom_dev_agents_link
Resolve a hosted agent by name (or create it with create:true) and cache its id in the project's sapiom.json. Run this before deploy.
sapiom_dev_agents_run
Start a real (cloud) execution of the linked agent. Use sapiom_dev_agents_inspect to follow it.
sapiom_dev_agents_run_local
Execute an agent on the local machine, running the author's actual step code with every ctx.sapiom.* capability call resolved from stubs (no Sapiom account, capability request, or capability spend). Author code is ordinary local code: its own filesystem, process, environment, and network effects remain real. Returns { outcome, output, steps[], unusedStubs[], stubWarnings[] }. outcome is 'completed' | 'failed' | 'paused' | 'running'. A step that pauses on a launch handle — pauseUntilSignal(handle, { resumeStep }) on agents.launch, models.launch, models.coding.launch, or a contentGeneration laun…
sapiom_dev_agents_scaffold
Scaffold a new Sapiom agent project into <dir>. Produces a TypeScript project with a starter agent in index.ts and its dependencies installed (best-effort; if the install was skipped offline, run `npm install` in <dir>). After scaffolding, the author writes step definitions and uses sapiom_dev_agents_run_local to test them.
sapiom_dev_agents_schedule
Create a trigger for a deployed agent — one of four kinds. 'schedule_cron' (+ cron, optional timezone) runs it on a recurring schedule; 'schedule_once' (+ at) runs it once at a future time; 'event' (+ eventType) runs it every time this tenant emits that event type via POST /v1/workflows/events, or the platform emits a 'sapiom.*' event (list in the server instructions, section 'Triggers'); 'webhook' runs it every time an external system POSTs to a public hook URL — the result returns that URL plus a shown-once signing secret and the HMAC-SHA256 scheme the sender must use. Use 'webhook' when an …
sapiom_dev_agents_schedule_cancel
Cancel a trigger of any kind by id. Stops all future fires: a recurring schedule won't re-arm, a pending one-off won't run, an event trigger stops matching, a webhook stops accepting POSTs (401 from then on). Irreversible — recreate to re-arm (a recreated webhook gets a new URL + secret). For a webhook whose secret leaked but whose URL should keep working, rotate with sapiom_dev_agents_schedule_secret instead.
sapiom_dev_agents_schedule_inspect
Inspect triggers of any kind (cron, one-off, event, webhook). With scheduleId: returns one trigger's config, next fire time (schedules), eventType (event), publicId / secretVersion / graceUntil / revokedAt (webhook — never the secret, which is shown only at create/rotate), and recent fire history (each with the run's executionId, and the inbound receiptId for event/webhook fires) — use this to debug a misbehaving trigger, then inspect a failed run's executionId with sapiom_dev_agents_inspect. With definition (slug) and no scheduleId: lists that agent's triggers.
sapiom_dev_agents_schedule_secret
Webhook-trigger secret lifecycle. 'rotate' = planned hygiene: mints a new secret (returned ONCE, with the hook URL beside it so the sender can be reconfigured in one step) while the previous secret keeps verifying for a 24h grace. 'complete_rotation' = the sender has moved; end the grace now so the old secret stops verifying immediately. 'revoke' = compromise: the hook rejects every request from now on and any open grace dies with it — irreversible, create a new webhook trigger to hand the sender a fresh URL + secret. Only valid on kind 'webhook'.

Show 12 more tools

sapiom_dev_agents_signal
Resume a paused cloud execution by delivering a named signal (matched by name + correlationId, NOT by executionId — so one call resumes every run waiting on that pair). Signals resume; they never start a run — to start one, emit an event with sapiom_dev_agents_emit_event. Read `message` in the result whenever it is present: `matched` counts the runs that actually resumed, so it under-reports a partial fanout and a 0 does not prove nothing was waiting.
sapiom_dev_app_delete
Delete a published App Link. The https://apps.sapiom.ai/{org}/{slug} URL stops resolving (anyone holding it gets a 404), any webhook receiver at its /hook path stops answering, and the slug is freed for reuse. Address the link by slug or appLinkId. This is destructive: ask the user before calling it, then pass confirm: true. Needs the org.write permission; when the credential lacks it the error names the permission — tell the user, do not retry.
sapiom_dev_app_list
List your organization's App Links (durable https://apps.sapiom.ai/{org}/{slug} apps published with sapiom_dev_app_publish): slug, URL, visibility, whether webhooks are on and the /hook URL when they are, daily spend cap, wake rate limit, wake status. Use it to find a link before sapiom_dev_app_settings or sapiom_dev_app_delete, or to answer "what have we published?". Read-only; needs org.read.
sapiom_dev_app_publish
Description is built at runtime.
sapiom_dev_app_settings
Change how a published App Link is exposed: turn webhooks on or off (webhooksEnabled), change visibility, set or clear the daily spend cap, set the wake rate limit. Webhooks are OFF by default on every link; once on, third parties POST to https://apps.sapiom.ai/{org}/{slug}/hook/<path> — the /hook prefix is stripped and the body forwarded byte-exact, so Slack/Stripe/GitHub signature checks run inside the app. Address the link by slug or appLinkId and send only the fields to change. These settings need the org.write permission (sapiom_dev_app_publish's publish authority is not enough): when the…
sapiom_dev_map
The agent map: which agents call, launch, schedule or trigger each other, grouped into systems, with every agent's steps. Computed from code each call; nothing about agents or edges is stored. Pass `root` (a project folder; default the working directory) and optionally a git `ref` to draw that version, or pass `agents` to map your own description without scanning. Systems are connected components over code-proven calls, events, signals and timers; shared vault keys, databases and connectors show as `shared` chips and never join agents. Every edge carries the code location that proves it; calls…
sapiom_dev_sandbox_check
Validate the sandbox preview resources in the project's sapiom.json without deploying. Returns { ok, sandboxes, issues }; `issues` lists actionable validation problems to fix before previewing.
sapiom_dev_sandbox_configure
Create or update a sandbox preview resource in the project's sapiom.json. Fill the typed arguments instead of hand-writing JSON — the config is validated and written under resources.<name> (type: "sandbox"). Returns the stored config. Use sapiom_dev_sandbox_preview afterwards to deploy it.
sapiom_dev_sandbox_preview
Deploy a web-app preview from the current project to a Sapiom sandbox and get a live URL. Reads sapiom.json (a `type: "sandbox"` resource), provisions the sandbox if needed, uploads the local code, builds, starts, and exposes a public URL. Returns { name, url, status, logs }. A `failed` status carries build/start logs (not an error) so you can fix and retry. The URL is TEMPORARY — it expires with the sandbox's `ttl`. For a link that is permanent, shareable, or meant for a teammate, use sapiom_dev_app_publish instead.
sapiom_logout
Log out of Sapiom by removing cached credentials for the current environment.
sapiom_send_feedback
Send the user's feedback about Sapiom — a bug, a rough edge, a feature request, or praise — to the Sapiom team. Reach for this when the user says something like "this is broken", "tell Sapiom", "file feedback", or "this should work differently": confirm the wording with them, then send their words as `message`. NEVER put file contents, code snippets, logs, stack traces, environment variables, API keys, or any other secret in `message` or `context` — both fields are plain prose only. Package version, platform, environment, and timestamp are attached automatically; do not restate them.
sapiom_status
Check authentication status for this local Sapiom developer MCP (sapiom-dev). Returns whether you're authenticated and which organization.

Compare and alternatives

Featured in

Best MCP servers for deployment

Signals

Stars: 21
Forks: 32
Open issues: 22
Contributors: 21
Last commit (this folder): Oct 22, 2026 (6 days ago)
Last release: Oct 9, 2026 (19 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name: io.github.sapiom/mcp
Version: 0.20.0
Auth: No auth
Packages: npm @sapiom/mcp
License: MIT
Repository: github.com/sapiom/sapiom-js
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql

Cite this page

sapiom/mcp. Agent Mart. https://agentmart.dev/connectors/sapiom-mcp (last updated 2026-10-24)