INTEGRATIONS / MODEL CONTEXT PROTOCOL
Membership context for your AI tools.
VeritableRoll’s MCP integration brings member searches, renewal explanations and controlled submissions into compatible AI workflows, using your staff permissions.
Production connection available. Connect Codex, Claude or ChatGPT with your VeritableRoll staff account. Reads, reports and review submissions use your existing organisation and branch permissions.
Ask about the record. Keep the decision accountable.
The Model Context Protocol (MCP) gives AI applications a standard way to use tools and retrieve context from other systems. In VeritableRoll, that context is the membership register, its requirements and its recorded renewal history.
For example, an authorised branch officer could ask a connected assistant to find a member by number, inspect a recorded renewal and explain the missing evidence. Where submissions are enabled, the officer could then ask it to submit supplied evidence for central review.
| Staff task | MCP action | Result |
|---|---|---|
| Find member 0000042 | search_members | Return matching memberships within the officer’s permitted branches. |
| Explain the recorded renewal | explain_renewal | Return the checks, recorded evidence, central review and any issued term. |
| Submit an updated evidence reference | submit_renewal_evidence | Create a submission for staff review, with retry protection. |
This is an illustrative sequence, not a live AI chat. The assistant’s explanation should be checked against the returned record. Authorised staff remain responsible for approval and issuance in the workspace.
Explore the renewal workflow in the fictional product demo →
Eight tools, with a defined purpose.
The interface separates finding and understanding records from submitting changes for review.
| Tool | What it does | Access |
|---|---|---|
list_organisations | List the organisations the signed-in staff account can access. | Read |
search_members | Search by name, member number or source reference, with up to 50 results per page. | Read |
get_membership | Inspect a membership, preserved source identifiers and published branch requirements. | Read |
explain_renewal | Explain a recorded renewal using its evidence, rules, review and issued-term information. | Read |
management_report | Summarise accessible membership, renewal, payment and event activity for a date range. | Read + reports |
get_member_edit_context | Retrieve editable values, available grades and the current record version. | Read + submit + branch editing permission |
propose_member_correction | Create a correction proposal for staff review without immediately changing the register. | Submission access; submissions enabled |
submit_renewal_evidence | Submit supplied evidence or CPD totals for independent central review. | Submission access; submissions enabled |
Fifty search results is a page size, not a membership allowance. Your organisation’s plan and branch permissions still apply.
Your existing access rules travel with the request.
- Staff identity first. Every request authenticates the staff account and checks its current organisation and branch grants. Ordinary member-portal accounts cannot use these staff tools.
- Separate permissions. Read access is required throughout. Reporting and submissions need additional OAuth scopes. A scope never grants access to another organisation or an unrelated branch.
- Controlled changes. Correction proposals and evidence submissions go into review. MCP cannot approve renewals, issue terms, assert payments, grant exceptions, send email or erase member records.
- A recorded operation. Organisation-specific tool calls record the actor, tool and outcome. These access receipts exclude prompt text and tool-result contents; submitted evidence remains part of the normal review history.
A connected AI provider receives the data returned to its client. Before connecting it, your organisation should approve that provider’s data handling and choose the access the workflow needs. See our service and processing terms and branch approval guide.
Connect your AI app.
Use your existing staff sign-in. Start with read and reporting access; add review submissions only when your organisation needs them.
| Access | What it allows | Review |
|---|---|---|
| Read and reports | Find memberships, explain renewals and read management reports. | Cannot submit corrections or evidence. |
| Submit for staff review | Read and report, retrieve editable context, propose corrections and submit supplied evidence. | Requires branch editing permission. Every proposed change or evidence submission enters staff review. |
Choose one connection per app. The read-only client is restricted by the sign-in provider: requesting an extra submission scope cannot upgrade it. To change access, reconnect using the other client and review the new consent screen.
Codex
- Add the connection. Add the following entry to your Codex
config.toml. If a VeritableRoll entry already exists, update it rather than adding a duplicate.
[mcp_servers.veritableroll]
url = "https://members.veritableroll.com/mcp"
scopes = ["veritableroll:read", "veritableroll:reports"]
[mcp_servers.veritableroll.oauth]
client_id = "veritableroll-codex"
callback_port = 4387
callback_url = "http://127.0.0.1:4387/callback"
- Sign in and consent. Run
codex mcp login veritableroll, then complete the VeritableRoll staff sign-in in your browser and approve the requested permissions. Your password stays with the sign-in provider. - Start with your organisations. Open a new Codex conversation and ask: “List the VeritableRoll organisations I can access.” Then choose an organisation and ask about a member or renewal.
- Enable proposals when needed. Add
veritableroll:submitto the scopes and sign in again to approve it. The account also needs branch editing permission. Corrections and evidence enter staff review; they cannot approve or issue a renewal.
A VeritableRoll operator account manages the service; it does not automatically receive access to customer registers. Connect an account that has staff access to the organisation you want to work with.
For submission access, use scopes = ["veritableroll:read", "veritableroll:reports", "veritableroll:submit"] and run codex mcp login veritableroll --scopes veritableroll:read,veritableroll:reports,veritableroll:submit. Complete the additional consent in your browser. See the Codex configuration reference.
Claude
- In Claude, open Customize → Connectors → Add custom connector.
- Name the connection VeritableRoll — Read and reports or VeritableRoll — Submit for review. Enter
https://members.veritableroll.com/mcpas the server URL. - Choose Sign in now and Use your own OAuth client. Enter the corresponding client ID below. Leave the client secret and request headers empty; keep Streamable HTTP.
- Add the connector, sign in to VeritableRoll and approve the displayed permissions. Enable the connector in the conversation where you want to use it.
| Access | OAuth client ID |
|---|---|
| Read and reports | veritableroll-claude-read |
| Submit for staff review | veritableroll-claude-submit |
Claude uses the permissions of the selected client, shown during consent. It also requests offline access to keep the connection working between conversations. Disconnecting or revoking the app’s authorization ends that connection; signing out of the website alone does not. A workspace owner may need to add the connector first. See Claude’s connection documentation.
ChatGPT
- In ChatGPT, open Plugins → Add → Create custom MCP server. Your workspace must allow custom MCP connections.
- Name the connection for your chosen access level and enter
https://members.veritableroll.com/mcpas the server URL. Choose OAuth. - Open Advanced OAuth settings. Select User-Defined OAuth Client, enter the client ID below, leave the client secret empty and set Token endpoint auth method to none.
- Keep
veritableroll:readandveritableroll:reportsselected. For the read-only client, deselectveritableroll:submit. For submission access, select all three. - Turn off OIDC enabled in these advanced settings. This connection uses the three VeritableRoll scopes; it does not need the separate email/domain-claiming scopes.
- Create the private plugin, complete VeritableRoll sign-in and consent, then install or enable it for your conversation.
| Access | OAuth client ID |
|---|---|
| Read and reports | veritableroll-chatgpt-read |
| Submit for staff review | veritableroll-chatgpt-submit |
The registered callback is https://chatgpt.com/connector_platform_oauth_redirect. Keep the discovered VeritableRoll authorization and token endpoints. See OpenAI’s custom MCP setup guide.
Try the connection
Start with: “List the VeritableRoll organisations I can access.” Choose an organisation, then ask for a member or recorded renewal. For submissions, supply the actual correction or evidence reference and check the pending review in the workspace.
If no organisations appear, your account needs a staff grant; operator access alone does not provide access to customer registers. If a submission is denied, check both the connection’s access level and your branch editing permission. Disconnect the app to remove its saved connection; an administrator can revoke your staff grant for immediate server-side access removal.
Connection details for technical teams
Resource: https://members.veritableroll.com/mcp. Discovery: https://members.veritableroll.com/.well-known/oauth-protected-resource/mcp.
Transport: Streamable HTTP, with authenticated POST requests and JSON responses. Authorisation: OAuth authorisation code with PKCE S256, staff authentication and consent. Access tokens expire after five minutes; the client can refresh its authorised session.
Scopes: veritableroll:read, with veritableroll:reports or veritableroll:submit added where required. These scopes never expand the staff account’s branch permissions.
Production acceptance exercised real sign-in, token refresh and all eight tools using fictional records. Checks included branch isolation, restricted readers, pending submissions and access revocation. No customer records were used.
Common questions
Can I connect my AI assistant now?
Yes. Follow the Codex, Claude or ChatGPT setup above using an active VeritableRoll staff account. Each person signs in and consents to their chosen access level. These are custom connections; a public app-directory listing is separate.
Will this renew memberships automatically?
The tools can explain a recorded case and submit supplied evidence for review. Approval and issuance remain separate actions for authorised staff in the workspace.
Does the public demo expose our member data?
The public demo is a separate fictional simulation. It has no access to your register or the authenticated MCP interface.
Is there a separate MCP price?
MCP access uses your existing VeritableRoll staff account. Your AI application’s charges and terms are separate. Contact us if you need a different client or a wider integration.