Six servers ready to add. Any other in one JSON entry.

The library holds servers we keep pointed at the vendor's own MCP endpoint. Adding one writes a reference into your project, not a copy of its config, so it does not drift. Each person authorizes it with their own identity, and every call through it takes the same eleven steps as any other.

Marketing Reporting in every new account

Google Analytics 4, Search Console and Bing Webmaster, one set of metrics. Built by us.

reports, funnels, the one write →

Linear oauth

Issues, projects and comments, created under the caller's own name.

what the gateway adds →

Notion oauth

Pages, databases, comments and search across a workspace.

a read-only Notion in one preset →

GitHub oauth

Repositories, issues, pull requests, files and security alerts.

pin the owner, allow the PR →

Sentry oauth

Errors, issues and events, with triage as the write.

a goal you can measure with it →

Context7 no sign-in

Current documentation for a library, straight into the prompt.

reads only, logged anyway →

A library entry is a reference, not a config.

Adding a server from the library writes one line into the project file. The concrete config is resolved from the library every time the project loads. Two things about a reference can change: enabled, to switch it off without removing it, and presets, to narrow it for everyone. Any other edit is refused with a code, and removing it is always allowed.

One cost: a library reference cannot carry its own list of read-only tool names. Which tools count as reads is what the vendor declares. If you need to add names yourself, add the same URL as a custom server instead.

"mcpServers": {
  "marketing-reporting": {
    "type": "library",
    "entry": "com.safe-mcp/marketing-reporting"
  },
  "linear": {
    "type": "library",
    "entry": "app.linear/linear",
    "presets": ["triage"]
  }
}

Shape from the project file format.

What the gateway adds to every one of them.

one identity per personeach member authorizes the server with their own account; what the server does carries their name

the recordevery call is logged with its full arguments before it runs, and the result after

a narrower surfacepresets hide tools, restrict argument keys, pin values, overlay a schema

the goal gatea write with no goal in force is refused; reads always run

the evidence gatea write that earlier sat in intervals where the goal went the wrong way is refused with the evidence

testing modeevery non-read-only tool blocked before it runs, still logged

Anything else takes one JSON entry.

Any MCP server reachable over HTTP is a custom entry in the same file: its URL, headers or OAuth, and the names of its read-only tools. Your Google Ads server, your Meta server, your CRM. Presets and assignments apply to it exactly as they do to a library server.

Start with the one that is already there.

get started Marketing Reporting →

A new account starts with Marketing Reporting added and one project. Sign in with Google once more to authorize it.