CDPGuidesSupport

SDKs and MCP

Language SDKs and an MCP server that wrap the Ours Privacy Platform REST API for Node.js, Go, and AI assistants.

Prefer not to call the REST API directly? The Ours Privacy platform ships with language SDKs and an MCP server that wrap every endpoint documented in this section. All are generated from the same OpenAPI specification. The SDKs and MCP server accept either a Platform API key or an OAuth access token issued by Ours Privacy as the bearer credential. MCP clients that support MCP authorization, such as Claude, connect with OAuth by signing in; no client ID is needed.


Available wrappers

ToolBest forDocs
MCP ServerDriving your account from Claude, ChatGPT, Codex, and other AI assistantsMCP Server (platform)
Node.js / TypeScript SDKBackend services, scripts, and Next.js / Node automationNode.js SDK (platform)
Go SDKGo services and infrastructure toolingGo SDK (platform)
OpenAPI specGenerating your own client in any languagePlatform OpenAPI Schema

For a high-level comparison of all SDK families, including client and ingest SDKs, see the SDK Overview.


When to pick which

  • AI assistant in the loop? Use the MCP Server. Connect an MCP client to https://ai.oursprivacy.com/mcp with OAuth or an API key, then ask about analytics, heatmaps, and consent and build sources, destinations, Tag Manager tags, consent banners, and experiments in plain language. OAuth needs an organization admin to turn on OAuth connections first; API keys work with any client that can send a header.
  • Writing application code? Use the Node.js or Go SDK. Both are typed, auto-generated, and track the OpenAPI spec.
  • Need a language we don't ship? Generate a client from the OpenAPI spec.
  • Want answers without connecting an outside client? The built-in AI Assistant answers questions about your configuration and analytics inside the dashboard, with no API key or setup.

Next Steps

How is this guide?

On this page