
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 分