Remote endpoint
AdsSyncs is a remote MCP server. Everything runs at one public URL — you don't host anything yourself.
Endpoint
https://mcp.adsyncs.net/mcp
- Transport — Streamable HTTP (MCP spec, 2025-06-18 revision).
- Authentication — OAuth 2.0 Authorization Code + PKCE (see Authentication).
- Hosted on — Google Cloud Run,
us-central1region, behind Cloud Load Balancing. - TLS — TLS 1.2+ enforced. HSTS preloaded.
That single URL is the only thing your AI client needs. mcp-remote (which our installer wires up) bridges your local client to it.
Discovery endpoints
For MCP clients and reviewers verifying the server, these auxiliary URLs are public:
| Path | Purpose |
|---|---|
GET /version | Returns build metadata (gitSha, builtAt, version). Used by smoke tests. |
GET /.well-known/oauth-authorization-server | OAuth 2.0 Authorization Server Metadata (RFC 8414). |
GET /.well-known/oauth-protected-resource | OAuth 2.0 Protected Resource Metadata (RFC 9728). |
POST /mcp | The MCP transport itself. Requires a valid bearer token. |
There is intentionally no /healthz — Cloud Run reserves that path. Use /version for liveness checks.
What the server exposes
Per the MCP spec, every MCP server can declare tools, resources, and prompts. AdsSyncs ships all three:
- Tools — 111 total across 4 ad platforms. See Tool catalog.
- Resources — Stable read-only data (workspace info, connected providers, account lists). See Resources & prompts.
- Prompts — Pre-baked workflows (weekly report, search-term cleanup, account audit). See Resources & prompts.
Every tool carries a tier marker in _meta["ads/tier"] (read / transform / mutation). Write-tier tools are disabled by default per provider; the workspace owner enables them in the dashboard.
Rate limits
| Limit | Value |
|---|---|
| Per workspace | 600 requests / minute |
| Per provider per workspace | 120 requests / minute |
| Burst | 30 requests / second (token-bucket) |
When a limit is exceeded the server returns standard MCP 429 errors. Upstream platform quotas (Google Ads API, Meta Marketing API, etc.) also apply — we surface those as quota_exceeded errors with the upstream error code attached.
Uptime & status
- Status page — status.adsyncs.net
- Target uptime — 99.9% monthly
- Deploy cadence — Continuous, with auto-rollback if
/versionsmoke test fails on the new revision.
The endpoint supports protocol version negotiation. Clients send the requested protocol version on the initial handshake and the server replies with the highest mutually-supported version. We currently support MCP 2024-11-05, 2025-03-26, and 2025-06-18.