# Integrations

> Search Console and GA4 per project with read-only scopes requested at connection time, DataForSEO behind a port, Polar as merchant of record, and an MCP server for agents.

Source: https://netweft.com/integrations

Nothing is connected by signing in. Google access is requested at the moment a project connects it, and both Google scopes are read-only.

## Google Search Console

Per project. Read-only, requested at connection time rather than at sign-in.

Real queries, clicks and impressions for the project's own site, read straight from Google. It sits beside the rank record rather than replacing it: one is what Google reports about a property, the other is what was observed at a position on a date.

## Google Analytics 4

Per project. Read-only, requested at connection time rather than at sign-in.

Sessions, engaged users and key events for the project. Connected separately from Search Console, so a workspace that wants one and not the other grants one and not the other.

## DataForSEO

Per workspace. Server-side, through a port with a mock implementation behind it.

Where netweft's real SEO data comes from — keyword metrics, SERP positions, backlink summaries, domain overviews. The provider sits behind a port, cached and rate limited per workspace. A mock implementation serves deterministic fixtures with no credentials, which is what lets the product run offline; nothing above the port knows which one answered.

## Polar

Per workspace. Merchant of record. netweft never sees or stores a card number.

Subscriptions, top-ups and invoices. Polar is the merchant of record, so the checkout, the tax handling and the receipts are theirs, and the only thing netweft stores is which plan a workspace is on and what it has left.

## MCP, for agents

Per workspace. Scoped API key, read-only over stored rows.

An MCP server at POST /mcp, so an agent can read a workspace without a person in the loop. 25 tools across 6 scopes, none of which writes, starts a crawl or spends a credit.