ScopeGate MCP Server

ScopeGate MCP server exists for a simple reason — assistants are far more useful when they can act on ScopeGate directly instead of describing what you should do. Granular permission gateway for MCP agents. Per-agent scopes for Google Drive, Gmail, Calendar.

What you get

AI Access Proxy Layer. Connect external services (e.g. Google), define granular permissions, and receive an MCP endpoint URL for use in AI agents. Acts as a permission gateway — exposing only the specific capabilities you authorize, more granular than native OAuth scopes.

What the assistant can call

Once ScopeGate is connected, these are the calls the assistant has available:

• Framework — Next.js 16 (App Router)
• Language — TypeScript
• Database — PostgreSQL + Prisma 7
• Auth — Better Auth (database-backed sessions, Prisma adapter)
• MCP — @modelcontextprotocol/sdk (Streamable HTTP)
• pnpm — PostgreSQL
• 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

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 3 environment variables: DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ - pnpm - PostgreSQL

Choosing this one

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ScopeGate's toolset — Framework, Language, Database and 11 more — is a fair guide to whether it matches your workflow. It is maintained by alifanov; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch ScopeGate.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the scopegate mcp server does with a few real requests.