← Field Notes

BUILD WITH TIDELIGHT 5 min read

A practical first step with Tidelight packages

Find an integration, inspect its source, and follow a version-pinned path into your stack.

Choose the interface that fits

The official package directory brings together the TypeScript SDK, MCP integration, Python client, React package, and command-line tools. Start with the workflow that matches your application and runtime rather than adding every integration at once.

Each package detail page explains its intended use, compatibility notes, registry destination, and available examples.

Check release details before installing

Package versions and installation instructions are surfaced alongside their registry links. Confirm the current release and follow the exact command shown on the package page. The public source repository remains available for review.

Credentials belong in your server environment or an appropriate protected secret store. Avoid putting project keys in browser code, source control, or logs.

Keep access scoped

Tidelight project credentials have explicit permissions. Create a key for the integration that needs it, grant only the required scopes, and rotate or revoke it from the Intelligence Cloud console when access changes.

Read the current documentation for endpoint behavior and availability before building a workflow that depends on a specific provider capability.