Install
$ agentstack add mcp-ariobarin-glossa ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Glossa
Glossa lets ChatGPT work inside one local coding workspace that the user explicitly exposes.
ChatGPT
-> OAuth protected MCP relay
-> authenticated outbound worker connection
-> one local Git worktree or explicit directory
Glossa is an execution bridge, not an agent. ChatGPT owns the model, conversation, planning, and approvals. The local worker owns file containment and command execution.
Why Glossa
Codex and ChatGPT Work share usage. Glossa connects the regular Chat surface to one local workspace without putting another model, planner, or agent in the middle.
Status
Glossa is a Windows-first open beta. The managed relay is live at https://mcp.glossa.sh/mcp. A valid Glossa login activates access automatically.
Install the open-beta CLI with Node 24:
npm install --global @ariobarin/glossa@beta
Then expose one workspace. Glossa opens Google sign-in automatically when needed:
Set-Location C:\path\to\a\project
glossa
glossa start . is the explicit form. You can run additional workers in other terminals to expose more workspaces from the same computer. Use glossa status to verify login, relay access, enrolled devices, and active workers.
Starting glossa authorizes connected clients to modify files inside that root and run commands with the full environment and permissions of the Windows account that launched it. Press Ctrl+C to disconnect.
ChatGPT
Glossa is not listed in the public plugin directory yet, so add it as a custom app in Developer Mode during the open beta. Follow the quickstart to connect the managed Glossa endpoint.
See the [open beta guide](docs/open-beta.md) for safe setup, verification, and troubleshooting.
Local development
Node 24 and Docker are required. Start local Postgres, create .env when missing, build, and migrate with:
npm run dev:setup
npm run dev
Stop local Postgres with npm run dev:down.
Glossa uses the managed relay by default. See [self-hosting](docs/self-hosting.md) if you prefer to operate your own relay, database, identity configuration, and CLI build.
Documentation
- [Open beta guide](docs/open-beta.md)
- [Self-hosting](docs/self-hosting.md)
- [Architecture](docs/architecture.md)
- [Security model](docs/security.md)
- [API and protocol](docs/protocol.md)
- [Managed identity operations](docs/managed-identity.md)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ariobarin
- Source: ariobarin/glossa
- License: MIT
- Homepage: https://glossa.sh
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.