Integrate / Claude

Organization configuration

A rollout pattern for using Synter with Claude while keeping credentials, accounts, and write authority scoped to the workspace that needs them.

1. Choose the connection

For Claude Desktop, the independently documented path is local STDIO MCP. Create a Synter API key for the target workspace and add:

{
  "mcpServers": {
    "synter": {
      "command": "npx",
      "args": ["-y", "@synterai/mcp-server"],
      "env": { "SYNTER_API_KEY": "syn_your_workspace_key" }
    }
  }
}

Restart the client after changing its MCP configuration. See installation options for remote MCP notes.

2. Apply least privilege

  • Use a workspace-scoped key, not one shared across unrelated clients or business units.
  • Connect only the ad accounts needed for the team's role.
  • Keep the key in the MCP environment configuration; never paste it into a chat or repository.
  • Rotate the key when ownership changes or a device is retired.

3. Set the operating boundary

Put that boundary in the organization's usage guidance and in each brief. Do not assume a client-level “always allow” setting is an adequate spending control.

4. Roll out in stages

  1. Pilot: one workspace, one non-critical account, and a small operator group.
  2. Test reads: connected accounts, spend, and date-range reporting. Compare results with the platform UI.
  3. Test writes safely: dry-run or paused-draft creation with a strict budget cap.
  4. Review: confirm account routing, key ownership, approval behavior, and logs.
  5. Expand: issue separate keys per workspace and document an owner and rotation process.

This guidance does not depend on, or claim support for, a Claude organization admin API.