Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
emisar
Overview
Description from the maker (original English)
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://emisar.dev/api/mcp/rpcRun this in your terminal
claude mcp add --transport http emisar https://emisar.dev/api/mcp/rpcOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"emisar": {
"url": "https://emisar.dev/api/mcp/rpc"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"emisar": {
"type": "http",
"url": "https://emisar.dev/api/mcp/rpc"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://emisar.dev/api/mcp/rpcMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain emisar.dev (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32398 servers in this category
- Published to the registry more recently than 91% of the other 32398 servers in this category
- Basic checks equal to or better than 100% of the other 32398 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is emisar safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.56.0) reached the registry 3 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
AI Deprecations
by aideprecations.com
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
emisar
Leave the agent working. Keep production authority bounded.
emisar gives MCP-capable agents a catalog of declared infrastructure actions instead of a shell. Policy decides what runs, what waits for a person, and what is denied. A small outbound-only runner checks the action again on the host before it executes anything.
Start with the public pack catalog and let emisar suggest the packs that match a host. Add your own actions without adding another MCP server to every client.
Start with one host
You need an emisar account, a Linux host with systemd, and sudo. GitHub CLI with gh attestation verify --bundle checks the release signature. Without GitHub CLI, the installer asks before it continues with only the checksum. With --yes, it warns and continues. Allow outbound HTTPS to emisar.dev:443, registry.emisar.dev:443, tuf-repo-cdn.sigstore.dev:443, and tuf-repo.github.com:443. The last two serve the public trust roots used to authenticate release checksums. No GitHub login is required.
GitHub is the optional release fallback. If you want that fallback, also allow api.github.com:443, github.com:443, and release-assets.githubusercontent.com:443.
- In the console, choose Connect a runner. Copy the generated command; it contains a fresh, single-use enrollment key.
- Run it on the host:
curl -fsSL https://emisar.dev/install.sh \| sudo EMISAR_ENROLLMENT_KEY=emkey-enroll-... bash
The installer authenticates the signed release checksum and verifies the archive against it. It then creates the service, installs host-matched starter packs, and starts the runner.
- Confirm the runner is online in the console, then dispatch
linux.uptimewith a reason. You are done when the output appears and the run is present in the audit trail. - Open AI agents and connect your client. Remote MCP clients use OAuth; local stdio clients can use the
emisar-mcpbridge and its browser approval flow.
The complete walkthrough, including expected output and troubleshooting, is at emisar.dev/docs/quickstart. An agent can perform and certify the setup with the public install-emisar skill.
How an action runs
AI client| MCP: discover actions, request one with typed arguments v emisar control plane | authenticate, scope, apply policy, wait for approval when required v outbound-only runner | verify pack hash, validate arguments, enforce local limits v declared host command stream redacted output, journal the attempt, update fleet audit
The action pack defines the contract: the executable, argv shape, argument schema, risk, timeout, output limits, redaction, and side-effect description. The model selects from that contract; it does not invent a command line for the runner to execute.
Adding a pack adds capabilities behind the same MCP surface. Operators do not need to deploy another tool server or reconfigure every agent when the catalog changes.
What holds the boundary
- The runner opens an outbound TLS WebSocket and exposes no inbound listener. Commands return through that established connection.
- Cloud input is limited to declared actions and typed, schema-bounded arguments. The runner rejects unknown actions and arguments.
- Packs are content-addressed: a hash of their contents identifies them. The control plane pins the trusted pack hash, and the runner recomputes it from disk before execution. New or changed custom packs wait for trust.
- The control plane evaluates runner scope, risk policy, action overrides, standing grants, and conditional approval before dispatch.
- On the host, the runner clamps execution options to the pack's limits and runs the declared binary and argv. The runner redacts output before it leaves the host, and Emisar keeps the redacted output in run history.
- The control-plane audit includes denied and pending requests. Every runner also writes its execution attempts and local refusals to a hash-chained JSONL journal.
- A runner can optionally require bridge-attested dispatch: intent signed by the customer-authorized MCP bridge with an Ed25519 or ECDSA P-256 leaf key. The control plane then cannot invent or widen a permitted call.
Read the exact guarantees, limitations, and threat model in .agent/kb/specs/security-model.md.
How emisar fits into your stack
Use declared actions for agent access and SSH for interactive administration. Run the agent in a sandbox such as co:op, grant the runner the OS permissions its actions need, and ship lasting configuration changes through your deployment workflow.
The runner executes permitted actions with its service user's OS permissions; it does not isolate those processes. Permitted destructive actions still have real effects. Review action definitions, pack trust, policy, runner settings, and host permissions together when deciding what the agent may do.
The staging-only shell pack is the explicit break-glass (emergency-only) exception to the declared-action model. It is critical-risk, default-denied, never suggested, and should not be installed on production runners.
Find the right surface
| Goal | Start here |
|---|---|
| Install, upgrade, harden, or diagnose a host | runner/README.md |
| Connect Claude, ChatGPT, Cursor, Codex, or another MCP client | Connect a CLI agent |
| Inspect or develop the stdio bridge | mcp/README.md |
| Browse, install, or author action packs | packs/README.md |
| Let an agent install emisar, connect a client, or author a pack | skills/README.md |
| Review architecture and trust boundaries | .agent/kb/architecture.md |
| Review protocol contracts | .agent/kb/specs/wire-protocol.md and .agent/kb/specs/mcp-api.md |
| Contribute to the control plane | portal/README.md |
| Review the production GCP infrastructure | infra/README.md |
Repository layout
portal/ Elixir/Phoenix control plane, operator console, website, and MCP APIrunner/ Go host runner and operator CLI mcp/ Go stdio-to-HTTP MCP bridge packs/ Versioned action-pack catalog skills/ Standalone customer skills for coding agents infra/ Production Terraform for emisar on Google Cloud run Root contributor command for development, tests, gates, and operations dev/ Development Compose topologies, images, configs, and fixtures tools/ Go implementations behind the contributor command and CI dist/ Tracked distribution packages plus ignored generated build output .agent/kb/ Repository architecture, specifications, runbooks, and rules
Each top-level project has its own AGENTS.md with its architecture, security rules, and verification gate. Run ./run help for the complete list of contributor commands.
Develop locally
The recommended path needs only Coop and Docker on the host. It installs every tool version the repository pins in the isolated project image:
./run bootstrap # works before Go is installedcoop build # build the pinned project image once coop run -- ./run setup # sidecars, deps, migrations, browser tooling coop shell # enter the development box
Then, inside the shell:
./run seed # explicit, idempotent demo data./run serve # live reload at the URL printed by Coop
or: ./run serve --iex
For native development, install the exact versions in .tool-versions with asdf. You also need Git, Coop, Docker, the PostgreSQL client, ShellCheck, jq, GNU Bash (with read -N), GNU coreutils, Chrome/Chromium, and ImageMagick. On macOS, Apple's bundled Bash and BSD utilities cannot run all pack regression checks:
brew install bash coreutils jqexport PATH="$(brew --prefix coreutils)/libexec/gnubin:$(brew --prefix bash)/bin:$PATH"
./run setup checks all prerequisites before starting services; ./run doctor reports every detected version and any mismatch to fix. On macOS, run ./run certs trust once for this workspace after setup.
The fast loop runs Phoenix in the current environment and keeps only PostgreSQL and Keycloak in the workspace-isolated Coop dependency stack.
./run urls prints this workspace's distinct Portal, metrics, Postgres, and Keycloak URLs. Coop forks inherit the same setup but receive different ports and volumes. Setup, serve, and reset never apply seeds unless you ask for them.
Use ./run status for a read-only view of the current workspace, ./run logs [db|keycloak] for its exact sidecar logs, and ./run psql for its development database. Every canonical gate (./run gate ) prints its current phase and elapsed time; a failure names the phase that stopped it.
The root docker-compose.yml remains the slower packaged topology with the release Portal image, seeded demo data, three runners, MCP, and signing. Start it with ./run smoke; it serves http://localhost:4010. See portal/README.md and dev/README.md.
License
This repository is dual-licensed:
runner/,mcp/, andpacks/are open source under the Apache License 2.0. You can inspect, build, package, and operate the on-host components independently.- Everything else, including
portal/, is source-available under the Business Source License 1.1. Non-production use is free. Production use is permitted only as needed to operate the Apache-licensed components or the hosted service under the Additional Use Grant. Other production use requires a commercial license. Each version converts to Apache 2.0 on its Change Date.
See contributing, security, and the CLA. For commercial licensing, contact licensing@emisar.dev.