The MCP Connector lets you configure Eternal Pro by asking. Connect it once and you can audit a questionnaire for faults, add or reword intake questions, reorder sections, build and manage questionnaires, edit your email templates, change firm settings, style and assemble your document exports, manage translations, assign clients to staff and create clients — all in conversation, from the Claude app.
This is separate from the Claude integration on the same page. The connector uses your own Claude subscription, so there is no API key to buy and no per-request cost from us. It works whether the Claude integration above it is enabled or disabled.
Before you start
- You must be a Firm Administrator. Nobody else can connect, and nobody else can approve a connection.
- You need a Claude account that supports custom connectors. Any current paid plan does; check Anthropic's plan pages if you are unsure.
- The connector is switched on by default. Generating a token is the deliberate act that opens the door, so there is nothing to enable first unless someone has previously turned it off.
What Claude can and cannot see
This matters, so it is stated plainly rather than buried.
Claude cannot see any client's answers, contacts, assets, documents, passwords, emergency card or vault. There is no operation that returns them. The connector is a configuration surface, not a data surface — a connected Claude can rebuild your questionnaire from scratch but cannot tell you a single thing a client has entered into it.
That is a property of the interface rather than a rule Claude is asked to follow. The scope is enforced on our side:
- No operation reads client data. Every one of the connector's operations is a thin wrapper around a function the Intake Editor already calls, and the whole surface is the intake definition plus firm-level configuration.
- Settings are filtered before they are offered. Per-client keys are excluded, and so are whole families of personal data by pattern — passkey credentials, emergency card and medical detail, QR card state, reminder state. A key added to one of those families tomorrow is excluded the day it appears, not the day someone notices.
- Secrets are out of reach in both directions. Your Anthropic key, integration tokens and every other stored credential are excluded from the settings tools, so Claude can neither read them nor overwrite them.
- The one client-facing lookup returns no client identity. Resolving a client turns an address or site id you already hold into a site id, its matters, who it is assigned to and whether it is restricted. It never returns the client's name, and an unknown address and a known address with no site give the identical answer, so it cannot be used to probe which addresses exist at your firm.
Claude can:
- Read and change your intake questions, sections and questionnaires
- Audit a questionnaire for faults, read-only
- Read and change firm-level settings from a defined allowlist
- Read and change your firm email and message templates
- Read and change document export styling, fixed attachments and header or footer images
- Read and override interface translations
- Change which questionnaire a client matter uses, assign a client to staff, and restrict a client site
- Create new clients, which emails them sign-in details straight away
One exception worth naming: if you upload a Word document as a styling reference, that file is stored and reused. Only its styling is applied, never its words — but never send a reference document that contains real client information.
Connect
- In Eternal Pro, go to Integrations → Claude and scroll to Configure your intake from Claude.
- Check that Status reads Enabled. If it reads Disabled, click Enable Claude intake configuration.
- Click Generate access token.
- Copy the token immediately. It is shown once and never again. Copy the Server URL shown beside it too.
- In the Claude app, open Settings → Connectors and choose Add custom connector.
- Paste the Server URL, give it a name you will recognise (for example Eternal Pro — Smith & Partners), and paste the token where Claude asks for it.
- Start a new chat and ask Claude for an overview of your intake. If it comes back with your questionnaires and what is in them, you are connected.
If Claude sends you to a browser approval page instead of asking for a token, that is the same flow from the other end. You will see a consent screen naming the application and your firm address, listing exactly what access is being granted. Read it, confirm the address is yours, then click Approve. If you did not start that request, close the page and do not approve it.
The status line, explained
| What you see | What it means |
|---|---|
| Enabled + Token issued 2 weeks ago | Fully working. |
| Enabled with a warning badge | Switched on, but no token exists yet. Generate one. |
| Disabled | Claude cannot read or change anything here, even holding a valid token. |
| No access token issued | Nothing has ever been connected from this administrator account. |
What the connector covers
Ten areas. Part 3 of this series gives you the phrasing to use for each; this is the map.
| Area | What it covers |
|---|---|
| Health check | A read-only audit of a questionnaire for the faults that actually break one: dead-end navigation, orphaned or self-referencing parents, blank questions, colliding choice ids, removed structural pages and orphaned overrides. Ask Claude to check your intake for problems before a launch, or after a big reorganisation. |
| Overview | One request summarising every questionnaire you have: question counts, estimated completion time and section structure. |
| Questions | Add, reword, duplicate, reorder, move, promote a nested heading back to top level, rewrite choice lists, hide, restore and permanently purge. |
| Questionnaires | Create one by duplicating an existing one, rename, delete, reset to baseline while keeping the questions your firm added, and set which one new clients receive. Export a questionnaire as a portable definition and import it back as a new one — the practical way to move a questionnaire between profiles or hand a tested one to another install. |
| Clients and matters | Create a client, resolve one you already hold an address for, change which questionnaire a matter uses, see your firm staff, assign a client site to one of them, and restrict a client site so only Firm Administrators can reach it. |
| Firm settings | A curated, labelled list of firm configuration — firm contact details shown on the intake, welcome messages, default interface mode, vault directory names and every client feature toggle. Also clearing the cached question set so the next page load refetches it. |
| Templates | Read and rewrite your firm email and message templates, including a find-and-replace across all of them at once. |
| Document exports | Far more than fonts. Set headings, sizes, colours and weights; upload a Word document as the styling reference; copy the questionnaire design onto another export type; add fixed .docx or .pdf pages to every packet front or back and reorder them; put a logo in a header or footer; and remove any of it. Covers all three export types — questionnaire, inventory and generated documents. |
| Translations | For multilingual firms: list the interface strings for one of your languages with the shipped translation, override any of them in your own wording, and clear an override to go back. Available once translations are switched on for your account. |
| Progress bar | Read and change the intake progress bar colours and height. This one is account-wide rather than per questionnaire, so it affects every client you have. |
| Roadmap and support | Browse the Eternal Pro roadmap — popular, new, planned and shipped — post a suggestion on your firm's behalf, or open a support ticket without leaving the conversation. |
A note on administrator accounts
If you hold the firm's own Firm Administrator account — normally the principal — everything above is yours to run. There is nothing in the connector you have to call us to do on your behalf.
If your firm has set up additional administrator accounts for staff, those accounts can connect and can work on questions, questionnaires, templates, the curated firm settings and client creation, but a handful of operations stay with the Firm Administrator account: document exports, translations, the staff roster and client assignment, restricting a client site, the progress bar, clearing the cached question set, and the roadmap. Asking from one of those accounts returns a clear refusal saying so rather than failing quietly.
Security and revoking access
Treat the token like a password. Anyone holding it can change your intake. Do not paste it into a shared document, a ticket or a chat thread.
Three controls, and they do different things:
- Generate a new token — immediately revokes the previous one. Use this if a token may have been exposed and you still want the connector working.
- Revoke access — kills the issued token(s). Claude can no longer change anything until a new token is generated.
- Disable Claude intake configuration — the firm-level kill switch. Refuses every request instantly, including from tokens that are still technically valid. Use this when you want everything off now and will sort out the details later.
Two independent checks gate every single request, not just the first one. The transport is authenticated, and the acting user is re-resolved to a real administrator account on your install on every call — so a stolen relay credential still cannot act as somebody who is not an administrator, and every change lands in the trail attributed to a named person.
Every request through the connector is written to your Audit Trail, along with token issue, revocation and connector approval events. That includes reads and refusals, not only writes — a read matters because one request can export an entire questionnaire, and a refusal matters because a blocked attempt is exactly the thing an audit trail exists to show.
Guardrails built into the connector
These are enforced on our side, not left to Claude's discretion:
- Anything consequential is refused on the first attempt. Purging a question, deleting or resetting a questionnaire, importing over an existing one, creating a client, changing a matter's questionnaire, restricting a client site, every document export change, posting a roadmap suggestion and opening a support ticket all come back the first time with a plain statement of what will happen and who to check with. Only a second, explicitly confirmed request writes anything. Claude cannot skip that step; the refusal comes from us.
- Client creation is rate limited per firm. Because creating a client emails them sign-in details straight away, Claude reads the name and address back to you before creating anyone.
- Support email is rate limited too, and the confirmation step asks you to check the message carries no client names or details — support does not need them and must not receive them.
- Roadmap suggestions are matched for duplicates first. The unconfirmed first call runs the matcher and names the existing requests that look similar, so you vote on one of those rather than filing a second copy.
- Settings are allowlisted. The connector reaches a curated, labelled list of firm configuration, and a wider set of genuinely configuration-shaped keys for the Firm Administrator — but never secrets and never per-client data.
- Structural questions are protected. A handful of built-in questions the intake logic depends on cannot be deleted, and one is pinned in place and refuses any attempt to move it, because it is only ever reached by a jump from the legal-name confirmation and its position is load-bearing.
- Rewriting choices preserves stored answers. When the existing choice ids are passed back, answers already given against those choices stay attached. Claude reads the current choice list before rewriting it for exactly this reason.
- Deletion is reversible by default. Deleting a question hides it and can be undone. Only an explicit purge is permanent, and it says so.
- Bulk edits preview first. A find-and-replace across your templates reports exactly what it would change and waits for your confirmation before writing anything.
- Uploads are size-capped and checked before they are decoded. A file too large to send this way is refused with a pointer to the Designer page, which has no such limit.
Don't want to connect an external app?
You do not have to. The Intake Editor has a prompt control built into its toolbar that runs the same operations, so you can describe a change and have it applied without connecting anything. The connector is for people who would rather work in a longer conversation, or who want Claude to hold context across a larger reorganisation.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| Claude says it is not authorised | The token was revoked, superseded by a newer one, or the firm switch is off. Check the status line, then generate a fresh token. |
| Every request is refused despite a valid token | Status is Disabled. Click Enable Claude intake configuration. |
| You lost the token | It cannot be retrieved. Generate a new one and update the connector in Claude. |
| "Only a Firm Administrator can..." | Working as intended. You are connected from an additional administrator account, and that operation stays with the firm's own Firm Administrator account. Connect from that account, or use the page directly. |
| "Translations are not switched on for this account" | Translations are switched on at the account level first, in Super Settings. Once they are on, the translation operations become available. |
| Claude refuses a change and asks you to confirm | Not an error. Consequential operations are designed to refuse the first call and state the effect. Read it, say yes, and Claude repeats the request. |
| Claude says a limit has been reached | A rate limit, counted per firm. Wait for the window to roll, or finish the batch from the relevant admin page. |
| A file is rejected as too large | The connector caps uploads well below the Designer page's own limit. Upload that file on the Designer page instead. |
| "Only a firm administrator can connect Claude to this intake" | You are signed in to WordPress as a non-admin account. Sign in as your admin account and retry the link. |
| "This connection link has expired" | Approval links are short lived. Start the connection again from Claude. |
| "That connection link points somewhere unexpected" | The link was altered in transit and was correctly refused. Never re-follow it — start again from Claude, and tell us if it happens twice. |
| Connector worked, now silently does nothing | Another administrator may have revoked or regenerated. Check the Audit Trail. |
| Claude says an operation exists but cannot run it | Start a fresh conversation. A long session can leave Claude working from a stale view of the available tools. |
Claude can also open a support ticket for you from inside the conversation if something looks wrong — just say so.
Next article in this series: Part 3 of 3 - What you can ask Claude to do in Eternal Pro
Previous article in this series: Part 1 of 3 - Setting up the Claude Integration in Eternal Pro
How to import clients from Lawmatics using a Zapier webhook ?
How to import clients from MyCase using a webhook ?
How to sync client intake data to Lawcus?
united states
