SDKs and MCP
Language SDKs and an MCP server that wrap the Ours Privacy Platform REST API for Node.js, Go, the command line, and AI assistants.
SDKs and MCP
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 and authenticate with the same Platform API keys.
Available wrappers
| Tool | Best for | Docs |
|---|---|---|
| MCP Server | Driving your account from Claude, ChatGPT, Codex, and other AI assistants | MCP Server (platform) |
| Node.js / TypeScript SDK | Backend services, scripts, and Next.js / Node automation | Node.js SDK (platform) |
| Go SDK | Go services and infrastructure tooling | Go SDK (platform) |
| CLI | One-off commands, shell scripts, CI/CD pipelines | CLI (platform) |
| OpenAPI spec | Generating your own client in any language | Platform 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 Claude Code, Claude Desktop, ChatGPT, or Codex to
https://ai.oursprivacy.com/mcpand manage destinations, mappings, and experiments through natural language. - Writing application code? Use the Node.js or Go SDK. Both are typed, auto-generated, and track the OpenAPI spec.
- Scripting from the shell or CI? Use the CLI — every resource is reachable as a subcommand.
- Need a language we don't ship yet? Generate a client from the OpenAPI spec.
Next Steps
- Platform SDKs overview — the full SDK landing page with install snippets.
- Authentication — create the API key the SDKs and MCP server need.
- Quickstart — the same operations against the raw REST API.
How is this guide?