
Gateco
ai.gateco由 gateco.ai 发布v1.13.0更新于 Oct 24, 2026
Permission-aware retrieval for AI systems: policy-enforced access to organizational knowledge.
概览
Gateco MCP 服务器为助手提供受策略约束、按权限过滤的组织知识检索,只有指定主体有权查看的内容才会到达模型。
- 可以做什么
- 以向量、关键词、混合或 grep 模式在连接器上执行权限感知检索
- 提出有依据的问题并获得带策略过滤引用的合成答案
- 列出连接器及其就绪级别,列出主体与群组,并按邮箱或身份提供方主体解析主体
- 试运行访问模拟,查看某主体会被允许看到哪些内容
- 适用场景
- 当助手需要基于公司文档回答问题、同时遵守每位用户的访问策略,并且希望无需编写代码即可由 Gateco 把关检索时使用。适合已在使用 Gateco 连接器与身份数据的团队。
- 运行要求
- 本地 Python 包,通过 uvx 或 pip 安装 gateco[mcp] 并以本地进程启动。需要 Gateco 账户和具备 retrieve 权限范围的 GATECO_API_KEY;访问检查工具则需要通过 gateco login 保存的用户会话。GATECO_BASE_URL 可选,默认使用托管 API。需要能访问 Gateco API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Gateco,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Gateco Python SDK
Official Python client for the Gateco API — permission-aware retrieval for AI systems.
[PyPI version] [Python 3.10+] [GitHub]
The problem it solves
Without Gateco, when an employee asks your AI assistant "What is the CEO's salary?", the RAG pipeline returns the salary from a leaked HR document.
With Gateco:
Gateco sits between your AI agent and your vector store. Every retrieval is evaluated against your access policies before any content reaches the model.
Installation
For MCP server support (Claude Desktop, Cursor, etc.):
Authentication
Gateco API keys use the format gck_<env>_<random> (e.g. gck_live_abc123...).
Generate keys via the dashboard or via client.api_keys.create(name="my-service").
The API key is sent as the X-API-Key header on every request. Set it via the
GATECO_API_KEY environment variable when using the CLI or MCP server. The key takes
precedence over a stored login.
No credential at all? Since 1.13.0 a client constructed with no api_key, no
GATECO_API_KEY and no access_token reads the session that gateco login stored in
~/.gateco/credentials.json (and its base_url), and writes refreshed tokens back. One
login on a machine serves the CLI, the MCP server and your own scripts; do not copy the
file between machines, because refresh rotates and the two copies would revoke each other.
Which routes accept an API key
A key carries explicit scopes, chosen when it is created (Settings > API Keys, every plan).
Everything not listed here needs a user session (gateco login or client.login(...));
a key sent there gets 401 AUTH_JWT_REQUIRED, and a key without the needed scope gets
403 API_KEY_SCOPE_MISSING.
Session only: policies, connector create/update/delete and their search and ingestion configs, identity providers, API-key management, audit, retrieval history, billing, the access simulator, classification suggestions.
Quick Start
Async (recommended for production services)
Synchronous (scripts and notebooks)
Available Namespaces
Every namespace, and every method on it, is available on both AsyncGatecoClient (async) and GatecoClient (sync); tests/test_sync_parity.py fails the build if the two drift.
Retrieval Search Modes
API Key Management
Relationship-Based Access Control (REBAC)
Use relation.<name> as a policy condition field to gate access on the existence of a tuple:
Onboarding Status
Principal Resolution
Grounded Answer Synthesis (Team+)
Policy Creation
Policy validation rules:
- Condition fields must use
resource.,principal., orrelation.prefix. Bare field names (e.g.,"classification") are rejected with 422 — they silently resolve against the principal rather than the resource. - Policies with empty
resource_selectorsrequireapply_to_all_resources=Truein the request body to opt into matching all resources explicitly.
Retrieval Diagnostics
Connector Preflight Check
Dashboard Activation Metrics
Pagination
List endpoints return a Page object. Use list_all() for automatic async pagination:
Rate Limits
Three endpoints enforce per-org-per-minute limits:
Exceeded limits raise RateLimitError. The SDK retries automatically with exponential backoff (configurable via max_retries). Limits are org-scoped and reset on process restart (in-memory implementation).
Error Handling
CLI
The gateco command is installed with the SDK and uses the same credentials.
--classification accepts public, internal, confidential, restricted;
--sensitivity accepts low, medium, high, critical (gateco ingest --help lists them).
MCP Server (Model Context Protocol)
The optional MCP server lets AI agents (Claude Desktop, Cursor, etc.) perform permission-aware retrieval without any custom code.
Claude Desktop Configuration
Available MCP Tools
All tools return markdown-formatted text. Denied content is never exposed — only denial reasons and counts are shown.
Development
Links
来源:README.md,提交 d188b83
工具
0版本历史
3- v1.13.0最新Oct 4, 2026
- v1.12.1Sep 27, 2026
- v1.11.1Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分