
Gateco
ai.gatecoPublished by gateco.aiv1.13.0Updated Oct 24, 2026
Permission-aware retrieval for AI systems: policy-enforced access to organizational knowledge.
Overview
Gateco MCP server gives an assistant policy-enforced, permission-aware retrieval over organizational knowledge, so only content a given principal may see…
- What you can do
- Run permission-aware retrieval over connectors using vector, keyword, hybrid or grep search modes
- Ask grounded questions and get synthesized answers with policy-filtered citations
- List connectors with readiness levels, list principals and groups, and resolve a principal by email or provider subject
- Dry-run an access simulation to check what a principal would be allowed to see
- When to use it
- Use it when an assistant must answer questions from company documents while respecting per-user access policies, and you want retrieval gated by Gateco without writing custom code. It fits teams already using Gateco connectors and identity data.
- Requirements
- Local Python package installed with uvx or pip (gateco[mcp]) and started as a local process. A Gateco account and a GATECO_API_KEY with the retrieve scope; the access-check tool instead needs a stored user session from gateco login. GATECO_BASE_URL is optional and defaults to the hosted API. Network access to the Gateco API.
Installation
In SourceWeft
- Open Gateco in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Source: README.md at commit d188b83
Tools
0Version history
3- v1.13.0LatestOct 4, 2026
- v1.12.1Sep 27, 2026
- v1.11.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts