Hosted MCP server/Marketing

NotFair MCP server

Hosted at notfair.co·Streamable HTTP

NotFair is an approval-gated Google Ads MCP server with hosted OAuth and logged, reviewable writes for campaigns, keywords, budgets, bids, ads, and assets. The documented install is the Claude directory entry (claude.ai/directory/notfair, then Connect and OAuth); Claude Code users have a separate plugin guide. The provider does not publish a tool count, so an exact number is not claimed here. For a first check, list the connected Google Ads accounts and customer IDs without changing anything.

notfair.co Streamable HTTP OAuth 2.1 (PKCE); install from the Claude directory Server not checked yet Reviewed 2026-11-16
About

Where it fits

Google Ads managers who want approval-gated, logged changes to campaigns and budgets.

  • List connected Google Ads accounts and customer IDs read-only.
  • Adjust budgets or bids with approval gates.
  • Review logged writes after a change.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

NotFair Claude connector

Install from Claude's directory and connect with OAuth. Claude Code users should follow NotFair's plugin guide instead of adding the raw endpoint.

  1. Open the NotFair directory entry

    In Claude, open claude.ai/directory/notfair and choose Connect.

  2. Authorize with OAuth

    Sign in to NotFair and approve access. No MCP URL, client ID, or secret is entered by hand.

  3. Run a read-only check

    Ask: List my connected Google Ads accounts and show the customer ID for each. Do not change anything.

  4. Change campaigns only afterwards

    Once the read-only check passes, use the approval-gated write tools; every change is logged.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://notfair.co/api/mcp/notfair
Host
notfair.co · /api/mcp/notfair
Transport
Streamable HTTP
Authentication
OAuth 2.1 (PKCE); install from the Claude directory
Server name
notfair
Listing type
Community or directory listing

The installer uses the server name notfair. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that notfair appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List connected Google Ads accounts and customer IDs read-only. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

NotFair documentationhttps://notfair.co/google-ads-claude-connector-setup-guide