B
Bevel-Software/Hexis
Org-wide skills, tools, permissions and identity for agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"bevel-software-hexis": {
"url": "https://demo.bevel.software/api/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"bevel-software-hexis": {
"type": "http",
"url": "https://demo.bevel.software/api/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http bevel-software-hexis https://demo.bevel.software/api/mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
Git-backed control plane for AI-agent skills, tools, context, permissions and
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
identity. Self-hosted and MCP-native.
One place where your company's AI plugins, tools and knowledge live: centrally
managed, reviewed and access-controlled, and usable from any AI agent. The
open-source core of the Bevel platform.
## Why Hexis?
Used by teams at
Read more about the learnings that we made which led to Hexis here: Our Medium Article
### For teams
One place where engineers and non-technical people alike can browse and load
plugins, propose suggestions, and manage access.
### For enterprises
Every skill, tool manual and permission is a file in a git repository you own,
so the audit trail is the storage layer: who changed what, when, who approved
it, and how to undo it. An agent can only do what the person running it can do,
resolved per file, and it never holds the credentials it uses. Runs on your
infrastructure, behind your own SSO.
### Why it's different from MCP gateways:
MCP gateways are uni-directional; users can consume plugins, skills or tools but there is no mechanism here for users to propose changes or share new skills and MCP servers. You can do this via GitHub in the back, but this is not accessible to non-technical users and there is no fine-grained access control for either viewing or the review process.
Hexis can do all of the above specified capabilities for distribution, and has this bidirectionality needed for management.
In Hexis, skills and tool manuals are reviewable files. Anyone can propose a
change; on protected branches it reaches the owners of the files it touches and
ships only once they approve. Agents propose too: one that hits a broken skill
mid-task can suggest the fix, and a person decides whether it lands.
## Contents
See Hexis in action
Connect Hexis to Cline
Try the live demo
Managed hosting
Deploy with Docker
Links and images in knowledge pages
Local development
Configuration reference
Skills in Cowork and claude.ai
Troubleshooting
Repository layout
FAQ
Watch the full walkthrough: connect an agent, use company context, review
proposed changes, and manage team access.
## See Hexis in action
### Propose and approve skill changes
Anyone can propose a new skill or improve an existing one. On protected
branches, owners review the exact change and approve it before it becomes
available to the team's agents.
### Use your team's skills in Claude
Connect Claude to Hexis over MCP, then ask normally. Claude can discover and
load the approved skill instructions and company context your role can access,
without copying prompts between tools.
### Connect Hexis to Cline
Cline can connect directly to Hexis as a remote Streamable HTTP MCP server.
Install the public demo connection from the Cline CLI:
sh
cline mcp install hexis --transport http https://demo.bevel.software/api/mcp --yes
Complete the OAuth sign-in in your browser when prompted. Cline then discovers
the skills, tools and context your Hexis role can access. For your own Hexis
deployment, replace demo.bevel.software with your deployment's host.
### Share skills with the right people
Add teammates to roles or grant access directly when needed. Everyone connects
to the same workspace, while each person and their agent only sees what they
One place where your company's AI plugins, tools and knowledge live: centrally
managed, reviewed and access-controlled, and usable from any AI agent. The
open-source core of the Bevel platform.
## Why Hexis?
Used by teams at
Read more about the learnings that we made which led to Hexis here: Our Medium Article
### For teams
One place where engineers and non-technical people alike can browse and load
plugins, propose suggestions, and manage access.
### For enterprises
Every skill, tool manual and permission is a file in a git repository you own,
so the audit trail is the storage layer: who changed what, when, who approved
it, and how to undo it. An agent can only do what the person running it can do,
resolved per file, and it never holds the credentials it uses. Runs on your
infrastructure, behind your own SSO.
### Why it's different from MCP gateways:
MCP gateways are uni-directional; users can consume plugins, skills or tools but there is no mechanism here for users to propose changes or share new skills and MCP servers. You can do this via GitHub in the back, but this is not accessible to non-technical users and there is no fine-grained access control for either viewing or the review process.
Hexis can do all of the above specified capabilities for distribution, and has this bidirectionality needed for management.
In Hexis, skills and tool manuals are reviewable files. Anyone can propose a
change; on protected branches it reaches the owners of the files it touches and
ships only once they approve. Agents propose too: one that hits a broken skill
mid-task can suggest the fix, and a person decides whether it lands.
## Contents
See Hexis in action
Connect Hexis to Cline
Try the live demo
Managed hosting
Deploy with Docker
Links and images in knowledge pages
Local development
Configuration reference
Skills in Cowork and claude.ai
Troubleshooting
Repository layout
FAQ
Watch the full walkthrough: connect an agent, use company context, review
proposed changes, and manage team access.
## See Hexis in action
### Propose and approve skill changes
Anyone can propose a new skill or improve an existing one. On protected
branches, owners review the exact change and approve it before it becomes
available to the team's agents.
### Use your team's skills in Claude
Connect Claude to Hexis over MCP, then ask normally. Claude can discover and
load the approved skill instructions and company context your role can access,
without copying prompts between tools.
### Connect Hexis to Cline
Cline can connect directly to Hexis as a remote Streamable HTTP MCP server.
Install the public demo connection from the Cline CLI:
sh
cline mcp install hexis --transport http https://demo.bevel.software/api/mcp --yes
Complete the OAuth sign-in in your browser when prompted. Cline then discovers
the skills, tools and context your Hexis role can access. For your own Hexis
deployment, replace demo.bevel.software with your deployment's host.
### Share skills with the right people
Add teammates to roles or grant access directly when needed. Everyone connects
to the same workspace, while each person and their agent only sees what they
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/bevel-software-hexis/)
- Source
- awesome · https://github.com/Bevel-Software/Hexis
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.