MCP server

Connect Client Portal to Claude or Codex to find client records, review outstanding work and prepare tasks from a conversation. The Model Context Protocol (MCP) connection gives your assistant tools for working with the information you can access in Client Portal.

Follow the setup below, then try a useful prompt. Already connected? Browse the tools and example prompts.

Setup

General

Use https://meetings.auditbot.co/mcp/ as the MCP server URL. This address is shared across Client Portal users and clients; choose the company and reporting period in your conversation after connecting.

Sign in with your Client Portal account and check the organisation before approving access. Your assistant uses your existing access, and task changes need a preview and your approval before they are saved.

Claude

Use these connection details:

Setting	Value
Server URL	https://meetings.auditbot.co/mcp/
OAuth client ID	client-portal-connector
Client secret	Leave blank

1. Open Customize → Connectors in Claude on the web or desktop.
2. If Client Portal is already listed, select Connect. Otherwise, add a custom web connector named Client Portal and enter the server URL above.
3. For a new connector, select OAuth sign-in and Use your own OAuth client. Enter client-portal-connector as the client ID and leave the client secret blank.
4. Complete sign-in, review the organisation and requested access, then enable Client Portal for your conversation.

On a managed workspace, an owner may need to add the connector first. Claude needs a publicly reachable server, including when you use its desktop app. See Claude's connection guide for its current setup screens.

Codex

Use the Codex CLI to configure Client Portal for the desktop app, CLI or IDE extension on the same computer.

Codex needs its own registered application ID from your Client Portal administrator. The Claude client ID above is for Claude only. In a terminal, replace YOUR_CODEX_APPLICATION_ID with the ID provided for Codex:

codex mcp add client-portal \
  --url 'https://meetings.auditbot.co/mcp/' \
  --oauth-client-id 'YOUR_CODEX_APPLICATION_ID'

Ask your administrator to register the exact callback URL shown by Codex for that application. Once it is registered, sign in:

codex mcp login client-portal --scopes mcp.read,mcp.write,offline_access

Check the organisation and requested access before approving. Restart Codex, then check the connection with /mcp. See Codex's connection guide for more setup options.

Useful prompts

Start with a read, choose your client and period, then ask for the work you need. These prompts work in both Claude and Codex.

Find your client and reporting period

Use this first to check the connection and choose the right engagement.

Show the clients I can access in Client Portal. Let me choose a client,
then show its reporting periods. Wait for my choice before continuing.
Do not make any changes.

Your assistant should return accessible clients or a clear empty result. An unexpected list or an error needs attention before you continue.

Get an engagement briefing

Catch up on the work and evidence already available for a selected client and period.

Brief me on [client] for [period]. Show outstanding work, available
evidence and recent activity, with links to the source records.
Flag missing information rather than filling in the gaps.

Prepare a follow-up task

Turn a follow-up into a task you can review before it is saved.

Prepare a task for [client] and [period] to [describe the follow-up].
Show the proposed title, owner, due date and description. Ask me for
anything missing and wait for my approval before saving.

For more examples, explore the tool tables grouped by workflow.

FAQ

Where do I find my connection details?

The shared server URL and Claude client ID are in Setup above. The client ID identifies the assistant application, not a company, and does not grant access by itself. Each person signs in with their own account. For Codex, ask your administrator for its application ID and share the callback URL it displays so they can register it.

I connected, but cannot see my client

Check the client name and the organisation you authorised. An empty list can be a valid result. If the client is also missing in Client Portal, ask your administrator to check your access.

My connection has stopped responding

Reconnect from your assistant's connector settings and complete sign-in again if requested. Check the account and organisation before approving. If it still fails, share the error message and the step where it appeared with your administrator, without passwords or tokens.

How do I know whether a change was saved?

Review the assistant's result and open the linked record in Client Portal. If the result is missing or uncertain, check the record before retrying so you do not create a duplicate. See Get help for failed or partially completed actions.