Log inSubmit server
Sapiom Js logo

Sapiom Js

by sapiom

Build, validate, deploy, and inspect Sapiom agents through a local MCP server for coding agents.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Sapiom Js

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-322": {
      "command": "npx",
      "args": [
        "-y",
        "@sapiom/agent-studio@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y @sapiom/agent-studio@latest

npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'ini@7.0.0', npm WARN EBADENGINE required: { node: '^22.22.2 || ^24.15.0 || >=26.0.0' }, npm WARN EBADENGINE current: { node: 'v20.9.0', npm: '10.1.0' } npm WARN EBADENGINE }

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 3d ago.

Overview

The sapiom/sapiom-js MCP server exposes Sapiom agent-development operations to coding agents through the local `@sapiom/mcp` package. It supports scaffolding, testing or validation, deployment, and inspection of Sapiom agents from an MCP-compatible client. Reach for it when you want a coding agent to manage Sapiom projects without manually invoking the CLI. It is separate from Sapiom’s remote capability MCP, which handles paid tool calls.

Use cases

  • Scaffold a Sapiom agent from a coding client
  • Validate an agent bundle, manifest, and graph
  • Deploy an agent through an MCP workflow
  • Inspect and operate Sapiom agent projects

Key features

  • Local developer MCP server
  • Agent project scaffolding
  • Local agent validation
  • Agent deployment
  • Agent inspection and operations
  • TypeScript SDK monorepo

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @sapiom/agent-studio@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars21Stargazers on the source repository.
npm downloads1.9kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Sapiom Js works

What sapiom/sapiom-js does

The sapiom/sapiom-js MCP server provides a local developer interface for building and operating agents on Sapiom. It is implemented by the @sapiom/mcp package and is intended for use from a coding agent. The server complements the Sapiom TypeScript SDK, which also includes packages for defining typed agent graphs, calling Sapiom capabilities, and running command-line workflows.

An agent in the Sapiom model is a typed graph of steps. Each step performs work and returns a directive that determines the next step. The surrounding SDK includes helpers such as defineAgent, defineStep, goto, and terminate, while the MCP layer gives a coding agent a way to work with the resulting projects.

How it works

The sapiom/sapiom-js MCP server runs locally over the standard MCP command pattern.

Terminal
claude mcp add sapiom-dev -- npx -y @sapiom/mcp

After registration, a coding agent can use the developer MCP to scaffold an agent, check its project, deploy it, and inspect it. The local surface is named sapiom-dev, and its operations use the sapiom_dev_* namespace.

This server should not be confused with Sapiom’s remote capability MCP. The local server is for development and agent operations. Remote capability services are used for paid tool calls such as sandboxes, repositories, coding models, search, and file storage. The repository documentation identifies these as two distinct MCP surfaces.

Setup and configuration

Install and register the MCP server with an MCP-compatible coding client using the package runner command above, or configure the equivalent command in another client. The repository also provides a CLI path for the same development lifecycle:

Terminal
npx @sapiom/cli agents init my-app
cd my-app
npx @sapiom/cli agents check
npx @sapiom/cli agents deploy

The SDK is written in TypeScript and organized as a monorepo. The MCP package is @sapiom/mcp; it is separate from @sapiom/tools, the typed client used by application code to call Sapiom capabilities.

Tools and capabilities

The sapiom/sapiom-js MCP server supports the developer workflow described in the repository:

  • Scaffold a Sapiom agent project.
  • Validate an agent locally, including its bundle, manifest, and graph.
  • Deploy an agent to Sapiom.
  • Inspect or operate Sapiom agents from a coding agent.

For programmatic capability access outside MCP, @sapiom/tools creates an authenticated client with SAPIOM_API_KEY. Its documented examples create repositories, run coding models against a repository, use sandboxes, and push changes. Those capabilities belong to the SDK client and remote Sapiom services, not necessarily to the local developer MCP.

Limitations and notes

The repository labels the SDK as beta and places it in the v0.x range, so APIs may change before version 1.0. The local MCP is aimed at development workflows rather than being described as the remote paid-capability service. Use the local server to help a coding agent build and operate Sapiom agents; select the remote capability MCP when the requirement is to expose paid Sapiom tools.

The README names Claude Code as a supported setup target. It does not provide a complete per-tool schema or enumerate every sapiom_dev_* operation, so tool-level behavior should be verified against the package documentation and the installed version.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sapiom Js

sapiom/sapiom-js is an MCP server that connects coding agents to the Sapiom agent platform through the local `@sapiom/mcp` package. Its main tools support scaffolding, validating, deploying, and inspecting Sapiom agents. It is separate from Sapiom’s remote capability MCP for paid tool calls.

Install it through the package runner with `npx -y @sapiom/mcp`, then register that command in your MCP client. The README gives Claude Code’s command as `claude mcp add sapiom-dev -- npx -y @sapiom/mcp`.

It can scaffold, validate, deploy, and inspect Sapiom agents from a coding agent.

Yes.

No. The local `@sapiom/mcp` package is the developer surface for building and operating agents. Sapiom’s remote capability MCP is a separate service for paid tool calls such as sandboxes, repositories, coding models, search, and file storage.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSapiom Js AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-322?style=directory)](https://allmcps.com/mcp/mcp-322)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-322"><img src="https://allmcps.com/api/badge/mcp-322?style=directory" alt="Sapiom Js on AllMCPs" /></a>