Agent setup

Connect RegNewsWire

On a fresh machine today, use the native Codex or Claude Code commands below. The email-code helper is ready for local release testing but is not installable from npm until the package is published.

After npm publication: email-code helper

The helper keeps one MCP refresh credential for this exact origin, saves it with user-only permissions, and does not write into Codex or Claude Code OAuth caches.

Ask which email to use, then run:

npx --yes @regnewswire/agent@0.1.0 request-code --email <EMAIL> --origin https://regnewswire.com --json

Ask the user to paste the short-lived six-digit code into the agent conversation, then pass it only through stdin to this separate operation:
```
npx --yes @regnewswire/agent@0.1.0 verify-code --code-stdin --origin https://regnewswire.com --json
```
Do not require a separate/private terminal or HTML widget, and never echo, retain, log, or put the code in command arguments, shell history, source files, or URLs.

Configure the current client with one complete command:

npx --yes @regnewswire/agent@0.1.0 setup --client codex --origin https://regnewswire.com --json

npx --yes @regnewswire/agent@0.1.0 setup --client claude-code --origin https://regnewswire.com --json

Then start a fresh client session if tools do not reload in place.

Call usage_get and help through MCP, then search one company plus one recent artifact.

New-account creation is controlled per environment. A closed environment returns a clear error; existing invited accounts can still sign in. The npm package must be published before these commands are available from a fresh machine.

Server endpoint

Recommended today: native remote MCP

Command syntax was checked on 2026-09-09 with Codex CLI 0.153.0 and Claude Code 2.1.258. A release-origin sign-in and tool-call acceptance test is still required before claiming full client compatibility.

Codex CLI

Add the hosted server with the Codex native MCP command.

codex mcp add regnewswire --url https://regnewswire.com/mcp --oauth-client-registration dcr --oauth-resource https://regnewswire.com/mcp

Run the command in your terminal.
Complete email-code sign-in and consent in the browser window the client opens.
Start a fresh client session if the RegNewsWire tools do not appear.
Call help, then search for one company and one recent artifact to verify authenticated access.

The installed Codex CLI confirms this command syntax. Adding the server starts its native OAuth flow.

Codex CLI MCP documentation

Claude Code

Add the hosted server at user scope with the Claude Code native MCP command.

claude mcp add --transport http --scope user regnewswire https://regnewswire.com/mcp
claude mcp login regnewswire

Run the command in your terminal.
Complete email-code sign-in and consent in the browser window the client opens.
Start a fresh client session if the RegNewsWire tools do not appear.
Call help, then search for one company and one recent artifact to verify authenticated access.

The installed Claude Code CLI confirms these command forms. The login command opens its native OAuth flow.

Claude Code MCP documentation

Other MCP clients

RegNewsWire requires Streamable HTTP, MCP 2026-07-28, OAuth Dynamic Client Registration, and browser sign-in. A client that exposes those features may be able to use https://regnewswire.com/mcp, but compatibility has not been established for every client or directory.

Accounts and invitations

The helper can create a Free account where agent signup is enabled. Native/browser signup may remain invitation-only.
Free accounts include 100 successful research operations per UTC calendar month, shared across web and MCP. Checking usage is free. Email alerts require paid or complimentary access.
Complimentary access needs no card or subscription and continues unless the invitation is revoked. Paid access is US$50 per month.

A coding agent asks the user to paste the short-lived email code into the conversation and passes it directly to the verifier through stdin without storing it. Permanent OAuth credentials stay in the helper's origin-scoped credential file and must never be pasted into chat, command arguments, logs, or source-controlled files.