GET CONNECTED / WINDOWS POWERSHELL

Your first company lookup.

Connect Codex CLI to BridgeHub, then ask for an SEC company profile with traceable sources.

BridgeHub needs no end-user account, virtual key, or OpenAI API key. Codex has its own installation, sign-in, and account-access requirements.

Prepare Codex CLI

Use Windows PowerShell with Node.js and npm installed. This project requires Node.js 22.14 or newer. Install Codex CLI following the official installation guide, then open a new PowerShell window.

codex --version
codex

On first launch, follow Codex’s sign-in flow using an account with Codex access. Complete any Windows setup prompts. When ready, exit Codex with /quit to run the connection command below.

Choose where to connect

Local demo · on your computer

Open PowerShell in the BridgeHub project folder. For a first-time checkout, run npm ci, copy .env.example to .env.local, and set SEC_CONTACT_EMAIL to the operator’s real contact email. Keep that file private. If setup is already complete, just run:

npm run dev

Keep this terminal running. Open http://127.0.0.1:3000 to read the website. In a second PowerShell window, add the MCP endpoint:

codex mcp add bridgehub --url http://127.0.0.1:3000/api/mcp

Local development does not require Redis. The address refers to your own computer; it cannot connect another person to your server. If the server chooses another port, use that port in the command.

Public demo · hosted service

Use this configured public endpoint instead of localhost. You do not need the BridgeHub project or a local development server.

codex mcp add bridgehub --url https://bridgehub-mvp.vercel.app/api/mcp

If bridgehub already exists, inspect it with codex mcp get bridgehub. To switch endpoints, remove that entry with codex mcp remove bridgehub, then run the desired add command. Other MCP entries remain unchanged.

Check the connection

codex mcp list
codex

The list confirms saved configuration. In a fresh Codex session, enter /mcp to check the active connection. Confirm BridgeHub exposes us_search_sec_company. BridgeHub requires no MCP OAuth login; an unsupported-authentication label by itself is not a connection failure.

These commands follow official Codex MCP guidance. Follow any tool-use approval prompts shown by your Codex configuration.

Ask for Apple

Use BridgeHub’s us_search_sec_company tool to search AAPL. Summarize the company profile and include the official source URLs and retrieval times.

Look for a real tool invocation and Apple’s CIK 0000320193. The response should include profile provenance and, for AAPL search, directory provenance. Filing counts and timestamps can change. A reply from model memory alone does not verify the connection.

If something goes wrong

Codex or endpoint unavailable

If codex is not recognized, finish the official CLI installation and reopen PowerShell. If PowerShell blocks an installed script, try its codex.cmd launcher when present. For local connection errors, confirm the dev server is running and the address includes /api/mcp. Restart Codex after changing configuration.

Tool not visible

Check codex mcp get bridgehub and /mcp. A saved server entry does not prove it is reachable. Managed Codex installations may restrict MCP servers; check with your administrator if policy blocks the connection.

Request limits

rate_limited is BridgeHub’s shared limit of 10 searches per rolling minute. Wait for the indicated delay. upstream_rate_limited comes from SEC. BridgeHub also allows at most five SEC request starts per rolling second and waits only within a 30-second lookup budget.

Data unavailable or incomplete

service_unavailable means the operator must check shared storage. SEC blocking, timeouts, and unavailable data have separate error categories. Retry later when marked retryable; a persistent block needs an operator check. For partial, read the warnings and failed CIKs before using the results.