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
Openglass MCP
Overview
Description from the maker (original English)
Look up any AI agent before you act; register, attest actions, run sealed sessions.
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://mcp.openglass.glass/mcpRun this in your terminal
claude mcp add --transport http openglass https://mcp.openglass.glass/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openglass": {
"url": "https://mcp.openglass.glass/mcp"
}
}
}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": {
"openglass": {
"type": "http",
"url": "https://mcp.openglass.glass/mcp"
}
}
}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://mcp.openglass.glass/mcpMenu 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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account federico2001, which owns the repo
- … 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 18329 servers in this category
- Published to the registry more recently than 54% of the other 18329 servers in this category
- Basic checks equal to or better than 100% of the other 18329 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 Openglass MCP 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.2.0) reached the registry 40 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, Excaliself
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 2 days ago
Install
Excaliself
by maciekzygmunt
Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.
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.
OpenGlass
A neutral witness for agent-to-agent interactions. See docs/SPEC.md and CLAUDE.md.
Run locally
docker compose up --build -d --waitcurl -k https://localhost/health # {"status":"ok","checks":{"mongo":"ok","s3":"ok"}}
Caddy serves https://localhost with a certificate from its internal CA. -k skips verification. To trust the CA instead:
docker compose cp caddy:/data/caddy/pki/authorities/local/root.crt ./caddy-root.crtcurl --cacert caddy-root.crt https://localhost/health
| Service | URL | Notes |
|---|---|---|
| web | https://localhost/ | Next.js |
| api | https://localhost/health, /v1/* | Fastify. Runs migrate on every start. |
| mcp | https://localhost/mcp | |
| mongo | mongodb://localhost:27017/openglass?directConnection=true | mongo:7, single-node replica set rs0 |
| minio | http://localhost:9001 (console) | bucket openglass-records, Object Lock on. User openglass / openglass-dev-secret. |
| mailpit | http://localhost:8025 | Catches all outgoing email |
MinIO no longer publishes official images, so compose uses the maintained community build pgsty/minio, pinned to a release.
See it in action
examples/witnessed-negotiation is a runnable, end-to-end demo: two agents register, get claimed, negotiate a purchase order over a witnessed session, close it, and independently verify the resulting record — against the real API, not a mock. See examples/README.md.
Risk policy
/spec/openglass-policy is a small, versioned, vendor-neutral YAML format for classifying an agent's action as low/medium/high risk — deciding *when* an action is worth a witnessed record, separate from the attestation mechanism itself (docs/SPEC.md §12). Reference evaluators: core-js (@openglass/core) and core-py (openglass-core), kept in sync by a shared set of test vectors. See docs/POLICY.md for the guide.
Integrations
otel-js/otel-py (openglass-otel) plug into an already-OpenTelemetry-instrumented agent: a SpanProcessor reads GenAI spans, classifies each against an openglass-policy, and opens an attestation for the risky ones — no OpenGlass-specific code in the agent itself. See examples/otel-integration for a runnable demo. langchain-py (openglass-langchain) does the same for LangChain tool calls via a BaseCallbackHandler — see examples/langchain-integration. /integrations/_template is the starting point for a new framework-specific integration, including the conformance tests every integration must pass.
The public /integrations page is the request board: a card per framework (from a static catalog, apps/api/data/integrations.yaml), voting and a request form (gated on the existing owner login, not GitHub OAuth — see the PR that added this for why), and an admin view at /integrations/admin to update status. Admin access needs the ADMIN_EMAILS env var set (comma-separated owner emails) — nobody is an admin until it is.
scripts/adoption-review.ts is a runnable report over that board's live data (vote leaderboard, the 3 frameworks to prioritize next, new requests) — run it yourself or from your own cron, whenever you want it, rather than it running unattended:
node --experimental-strip-types scripts/adoption-review.tsoptionally: OG_ADMIN_SESSION_COOKIE="og_session=..." to include the request queue (admin-only)
Develop and test
corepack enablepnpm install pnpm -r build pnpm -r typecheck pnpm -r test # starts a throwaway mongo:7 container (needs Docker)
Same tests, different MongoDB
The database is configured by MONGODB_URI and nothing else. With MONGODB_URI unset, the tests start a throwaway mongo:7 container. With it set, they run against that server instead. Each test file uses its own og_test_ database and drops its collections afterwards.
# the local compose MongoMONGODB_URI='mongodb://localhost:27017/openglass?directConnection=true' pnpm -r test
an Atlas free-tier cluster: only the URI changes
MONGODB_URI='mongodb+srv:// : @ .mongodb.net/openglass?retryWrites=true&w=majority' pnpm -r test
For the Atlas run:
- The database user needs
readWriteAnyDatabaseanddbAdminAnyDatabase. Tests create per-file databases, andmigraterunscollModto set validators. - Your IP must be on the cluster's access list.
The production app user only needs readWrite and dbAdmin on the openglass database.
Schema changes
- Collections are defined in
packages/db/src/models. Each has a Zod model, a$jsonSchemavalidator generated from that model, and named indexes.migrateapplies all of them idempotently on api start, under a lock. - Data changes go in versioned scripts:
pnpm --filter @openglass/db migration:create, which writes topackages/db/migrations.
Deploy
main is built, pushed to ECR and deployed to a single EC2 instance by .github/workflows/deploy.yml. The AWS resources and first-time setup are in infra/README.md.