B
Bevel-Software/Hexis
Org-wide skills, tools, permissions and identity for agents
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
远端端点（Claude Desktop / Cursor / Windsurf 共用 mcpServers）
{
"mcpServers": {
"bevel-software-hexis": {
"url": "https://demo.bevel.software/api/mcp"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据，我们没有替你安装或托管它。 官方 Registry 记录：这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code（.vscode/mcp.json —— 键名是 servers，远程要 type: http）
{
"servers": {
"bevel-software-hexis": {
"type": "http",
"url": "https://demo.bevel.software/api/mcp"
}
}
}VS Code 的配置文件和另外三家不同：顶层键是 <code>servers</code>，远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code（命令行）
claude mcp add --transport http bevel-software-hexis https://demo.bevel.software/api/mcp
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-11-05；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
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
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/bevel-software-hexis/)
- 来源
- awesome · https://github.com/Bevel-Software/Hexis
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。