Connect TrialStack Catalyst to Codex

Connect Codex to ask questions about your TrialStack data and prepare governed changes from a Codex conversation.

You need a TrialStack account with Catalyst access. Use this connection address when Codex asks for the MCP server URL:

https://api.trialstack.com/mcp

You sign in with your own TrialStack account. Your existing organizations and permissions determine what Codex can access.

Connect from the Codex app

1. Open Settings and select MCP servers.
2. Add a Streamable HTTP server and enter the connection address above.
3. Save the server and restart Codex.
4. Select Authenticate, sign in to TrialStack, review the requested access, and approve the connection.
5. Type /mcp and confirm that TrialStack Catalyst is connected.

Connect from the CLI

codex mcp add trialstack-catalyst \
  --url https://api.trialstack.com/mcp
codex mcp login --scopes user:org:read trialstack-catalyst

Use the CLI option only if you manage Codex from a terminal. The Codex app, CLI, and IDE extension share the connection for the same installation.

Optional: install the Catalyst plugin

The TrialStack Catalyst plugin adds the connection, starter requests, and instructions that help Codex use Catalyst consistently. Installing the plugin does not give Codex additional TrialStack access.

Make your first request

Use TrialStack Catalyst to list the organizations I can access. Do not make changes.

Then select a returned organization and request a read:

Use [organization name] and list its trials. Treat an empty result as valid data.

If the organization list appears, the connection works. An empty trial list can still be correct when the selected organization contains no matching records.

For a change, ask Codex to prepare a preview without applying it. Review the preview and approve it only in your next message. See Model Context Protocol (MCP) for organization selection, tools, governed changes, and troubleshooting. See Agent Skills for the portable guidance bundled with the plugin.