
ScopeGate
io.github.alifanov由 GitHub 帳號 alifanov 發布v1.0.1更新於 Oct 24, 2026
Permission gateway for AI agents: scoped MCP endpoints over 27 services, audited and revocable.
發布方自己的服務:Scope (AEC) - Preview
概覽
為 AI 代理打造的權限閘道:針對 27 項服務提供依動作授權的 MCP 端點,具備稽核紀錄與一鍵撤銷。
- 可以做什麼
- 透過受限的 MCP 端點呼叫已連接的第三方服務,例如 Gmail、行事曆、雲端硬碟、Slack、Notion、Jira、HubSpot、Salesforce、Stripe、Airtable 等
- 只能執行該端點勾選的特定動作,例如僅讀取郵件而不能寄送郵件
- 依專案檢視稽核紀錄:誰呼叫了哪個工具、結果與耗時,並可匯出
- 重新產生端點金鑰即可立即撤銷存取,服務連線本身仍保留
- 依專案組織服務連線、端點與權限
- 適用情境
- 當代理需要存取真實帳號(郵件、行事曆、CRM、付款等),而你希望把它限制在少數明確動作、而非授予寬泛的 OAuth 權限,且需要紀錄與快速切斷存取的手段時適用。
- 執行需求
- 可使用 scopegate.dev 的遠端端點並以 OAuth 登入,或自架:以 Docker Compose 一鍵啟動(內含 PostgreSQL),或以 Node.js 20.19+/22.12+/24+ 搭配 pnpm 與 PostgreSQL 執行。連接真實服務需在 .env 中為各供應商填入 OAuth client id/secret;自架需設定 DATABASE_URL、BETTER_AUTH_SECRET、BETTER_AUTH_URL、ADMIN_EMAIL 與 ADMIN_PASSWORD。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 ScopeGate,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
ScopeGate
Never hand an AI agent a full OAuth scope again.
ScopeGate sits between your agents and the accounts they reach — yours or your clients'. You connect a service once, tick the exact actions an agent may call, and hand it an MCP endpoint that can do nothing else. Every call is logged; one click kills the key without touching the connection.
- Per-action permissions —
gmail:read_emailsyes,gmail:send_emailno. Finer than any provider's OAuth scopes. - Audit trail — who, which tool, what outcome, how long. Per project, exportable.
- One-click revocation — regenerate an endpoint key; the service connection stays.
- Tokens never leave — AES-256-GCM at rest, refreshed automatically, agents only ever see
sg_….
Run it yourself in one command:
Open http://localhost:3000 — the admin login is printed in the container logs on first boot. Details in Quick Start.
Tech Stack
- Framework: Next.js 16 (App Router)
- Language: TypeScript
- Database: PostgreSQL + Prisma 7
- UI: Tailwind CSS v4, shadcn/ui
- Auth: Better Auth (database-backed sessions, Prisma adapter)
- MCP:
@modelcontextprotocol/sdk(Streamable HTTP) - Package Manager: pnpm
Quick Start (self-hosted)
Full feature parity with the hosted cloud version — nothing is cut for self-host.
Open http://localhost:3000. No .env file needed: a local
Postgres and a fresh BETTER_AUTH_SECRET are provisioned automatically, and the
generated admin login is printed once in the app container logs on first boot
(look for Generated admin login) — search it with docker compose logs app | grep -A4 "First run".
The password is also saved to the app_data volume so it survives restarts.
To connect real services (Gmail, LinkedIn, GitHub, …), copy .env.example to .env
and fill in the OAuth client id/secret for the providers you want — every block is
independent and optional, a provider without credentials simply doesn't show up.
Development Setup
Prerequisites
- Node.js 20.19+, 22.12+ or 24+ (required by Prisma 7)
- pnpm
- PostgreSQL
Setup
- Clone the repository and install dependencies:
- Copy the environment file and fill in your values:
- Run database migrations:
- Start the development server:
Open http://localhost:3000.
Project Structure
Available Scripts
How It Works
- Login — sign in with admin credentials (bootstrapped from env vars on first run)
- Create a Project — organize endpoints and services by project
- Connect a Service — add a service connection to the project
- Create an MCP Endpoint — select a service connection and pick specific permissions (e.g.
gmail:read_emails,calendar:create_event) - Use the MCP URL — plug the endpoint URL into any MCP-compatible AI agent; only the allowed actions are exposed
- Monitor — track every request in the audit log
Permissions
A permission is a single action, not a service — gmail:read_emails can be granted
without gmail:send_email. Groups are derived from src/lib/provider-registry.ts
(27 providers: Google Workspace, Google Ads & Search Console, Meta, LinkedIn,
Twitter, Slack, Notion, Jira, HubSpot, Salesforce, Stripe, Airtable, …) and listed
in src/lib/mcp/permissions.ts. Adding a provider means editing the registry —
transport, token strategy and permission groups are all derived from it.
A few Google examples:
Database Schema
- User — authentication, team membership
- Session — database-backed auth sessions
- Account — auth provider credentials (email/password)
- Project — logical grouping for services and endpoints
- TeamMember — user-project relationship with roles (owner/member)
- ServiceConnection — OAuth tokens for connected services
- McpEndpoint — MCP endpoint with API key, rate limit, active status
- EndpointPermission — allowed actions per endpoint
- AuditLog — request log with action, status, duration, errors
License
See LICENSE.
來源:README.md,提交 c2ec9b9
工具
0版本歷史
1- v1.0.1最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
其他 Scope 整合

Scope (AEC) - Preview
bid.scope官方發布者
Scope AEC 分包商採購層的預覽版 MCP 伺服器,提供狀態、服務類別、候補名單登記與專案改期功能。

Scope (Legal)
bid.scope官方發布者
讓助理把法律服務案件派發給具備資格的專業人士(送達員、法庭記錄員、紀錄調取、專家證人等),並追蹤相關案件。

Scope (Claims) - Preview
bid.scope官方發布者
Scope 理賠端專業採購的預覽版 MCP 伺服器:查看路線圖狀態、列出規劃類別、加入候補名單,並重新安排已授予專案的日期。

Scope Creep Flag Tracker
由 GitHub 帳號 mrfentmen 發布
一個本機 MCP 伺服器,根據 JSON 資料分析自由接案工作中的範圍蔓延(scope creep)標記,提供 25 個工具且沒有付費牆。

Scope Creep Flag Planner
由 GitHub 帳號 mrfentmen 發布
本機 MCP 伺服器,分析 JSON 以標記自由接案工作中的範圍蔓延,提供 25 個工具且無付費牆。