
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 个工具且无付费墙。