Connect PulseLake to an AI assistant.

PulseLake has distinct Model Context Protocol (MCP) connections for tenant workspace operations and for research, simulation and process-assessment workflows. Choose the route your workspace needs; these connections are not interchangeable.

Choose the connection for your task

Tenant workspace operations

For PulseLake ExperienceOps in a tenant workspace, open the PulseLake ExperienceOps connection page and follow its current setup instructions. This is a separate tenant-oriented route; it is not the research connector below.

Research, simulation and process assessment

These are separate remote connectors for Persona/research, World Simulation research and Process Assessment. Use the specific server URL assigned to your account:

General research connector: https://ai-consultants.pulselake.co/oauth/pulselake-mcp
Simulation research connector: https://ai-consultants.pulselake.co/oauth/simulation-research-chat
Process Assessment connector: https://ai-consultants.pulselake.co/oauth/process-assessment

Do not substitute one route for another. Access depends on your account and service configuration. If you are unsure which to use, ask the PulseLake team.

Authorize a research or assessment connector

In an AI client that supports remote HTTP MCP with OAuth, add a remote server or connector. Client menus and labels vary.
Paste only the research or assessment URL assigned to your task. Let the client perform OAuth discovery and registration.
Review the requested permissions in the authorization screen. Continue only if the account and access requested are appropriate for your work.
Complete authorization in the browser opened by your client, then return to the client and check that the connection is available.
Start with a low-risk task and confirm that the resulting information is appropriate before relying on it.

The public OAuth discovery documents for these connectors advertise Authorization Code with PKCE (S256) and refresh-token support. The client should handle discovery and authorization; actual permissions are shown during consent and may depend on the account and operation. Read the MCP authorization specification for the protocol background. Do not copy access tokens, refresh tokens, authorization links or passwords into a chat.

Review access before you authorize

The public OAuth metadata currently lists persona:run, research:run, workflow:read and workflow:run. The scopes a client requests for a given operation can differ. Read the live consent details and grant only what you recognize and need; ask your workspace administrator if the request is unexpected.

Do not place private API keys or OAuth tokens in prompts, screenshots, support messages or source code. If a client asks you to paste a secret manually, stop and contact hello@pulselake.co for guidance.

If the connection does not appear

Confirm the full address, including the /oauth/pulselake-mcp path.
Check that your client supports remote HTTP MCP and OAuth discovery.
Review the client’s displayed authorization message. Do not bypass a certificate, identity or permission warning.
If the service is unavailable or the authorization request looks unexpected, contact PulseLake with the client name and a description of the issue. Do not send credentials or tokens.

Client interfaces and the access enabled for a particular account may differ. The ExperienceOps setup page has its own tenant-oriented instructions. See the PulseLake FAQ or contact the team if a connector is not available to your account.