SDK | PatchOps

Quickstart

From install to first call.

Install the SDK

Add the SDK to your project. Pick your language.

@patchops/sdk

Terminal

npm install @patchops/sdk

Authenticate

patchops login

Terminal

# Browser OAuth — stores a refreshable session
patchops login

# ...or use a personal access token
patchops config set-token po_pat_xxxxxxxx

Call connectors from your app

Both SDKs wrap the same MCP surface: list tools, run structured connector calls, and read back results, logs, and timing.

@patchops/sdk

TypeScript

import { PatchOpsMcpClient, PatchOpsInvokeClient } from "@patchops/sdk";

// Reuse the access token from your CLI session or OAuth flow.
const mcp = new PatchOpsMcpClient({
  baseUrl: "https://patchops.ai",
  accessToken,
});

await mcp.initialize();
const { tools } = await mcp.listTools();

// Structured connector call: connector + method + args.
const invoke = new PatchOpsInvokeClient({
  baseUrl: "https://patchops.ai",
  accessToken,
});

const wells = await invoke.invoke({
  connector: "welldatabase",
  method: "getOperatorWells",
  args: { county: "Loving", operator: "Mitsui" },
});

console.log(wells.result);

What you get

Typed clients

TypeScript and Python clients wrap the MCP surface. No transport layer to write.

Same surface as the CLI

List tools and run structured connector calls identically across both languages.

Bring your own auth

Reuse the access token from your CLI session, or wire in your own OAuth flow.

Next steps

CLIRun and test locally API referenceEndpoints and schemas ConnectorsBrowse what you can reach