INTEGRATION DIRECTORY
Choose the interface that fits your product, AI client, or development stack. Each path uses the same scoped Tidelight services.
Requests, scopes, and evidence stay on the same service boundary.
START WHERE YOU BUILD
Use an API, an MCP transport, or a package maintained for your stack.
Make versioned, server-side requests with project-scoped credentials. Start research jobs, check their status, read supported market instruments when available, and receive job webhooks.
api.tidelight.app/v1AccessProject-scoped bearer tokenUse Tidelight’s hosted Streamable HTTP MCP endpoint. Authenticate with a scoped bearer key or OAuth 2.1 with PKCE when the client supports it.
mcp.tidelight.app/mcpAccessScope-filtered MCP toolsThe published Node.js bridge connects a local stdio MCP client to the hosted Tidelight service. The service validates credentials, filters tools by scope, and applies quotas.
@tidelight/mcpTransportLocal stdio → hosted Streamable HTTPStart from a maintained client package, React interface, or command line workflow. The package guides include install commands, examples, release details, and source links.
Explore packagesCLIENT COMPATIBILITY
The hosted service supports Streamable HTTP, bearer authorization, and OAuth discovery. MCP Inspector 2.11.0 has a recorded authenticated production connection and scoped market-tool call. Each client’s setup and authorization flow can differ, so follow its own connection settings and verify access using the scopes on your project key.
READY TO CONNECT
The console keeps credentials, requests, research jobs, and access history together.