DEVELOPERS & INTEGRATIONS
MB Connect
MB Connect lets an AI assistant you already use, such as ChatGPT or Claude, work with MB HR Documents on your behalf: looking up document types, checking what a document needs, drafting one, and rendering it to PDF or DOCX. Drafting is free and needs no MB account. The PDF or DOCX file needs a connected account and an entitlement, exactly as it does on the tool’s own page.
Server URL
https://mbresumebuilder.com/mcp
Add it in three steps
- Copy the server URL above.
- In ChatGPT, turn on Developer mode in your settings and add a custom connector (availability depends on your plan and your workspace’s policy). In Claude, open the connector settings and add a custom connector. Paste the URL. If it asks for a name, use MB Connect.
- Ask for a letter. Drafting works straight away with no sign-in. When you ask for the PDF or DOCX file, your assistant sends you to our own sign-in page to approve access, and your MB password is never shared with it.
Using Grok?
Grok needs a different address. It only offers to sign you in at the moment you add a connector, and the main address above needs no sign-in for drafting, so Grok can draft with it but never asks you to sign in and so cannot produce the file. Add this sign-in address instead and Grok asks you to sign in to MB straight away.
https://mbresumebuilder.com/mcp/account
In Grok’s connector settings choose New connector, then Custom, and paste the address. A sign-in window opens on our own page; approve the access there. If Grok says the connector is unavailable, your browser may have blocked that window: allow pop-ups for grok.com and add it again.
What we have checked: on 30 September 2026 we added it to Grok, signed in, listed the document types, drafted a letter, and asked for the file, which stopped at the plan-required message the website shows too. We have not yet seen Grok produce a finished PDF or DOCX, so treat that last step in Grok as untested. Everything you ask Grok passes through xAI, Grok’s provider.
For developers
MB Connect is a Model Context Protocol (MCP) server, the same single server for every client. Streamable HTTP transport, OAuth 2.1 with PKCE. Add it as a custom connector in ChatGPT (Developer Mode) or Claude by entering the URL, or point the MCP Inspector at it. It is not listed in either assistant’s app directory, so there is nothing to search for: you add it yourself.
A second path, /mcp/account, serves the same nine tools but answers every request that has no valid token with a 401 and the OAuth discovery challenge, including initialize and tools/list. It exists for clients that only start OAuth when their first connection is refused. Tokens are issued for /mcp either way.
What it can do
Nine tools, and this is the complete list. Three work without an account; six require you to connect your MB account first.
No account needed
- List the HR document types available
- Check which fields a given document type requires
- Draft a document from values you supply, and read the drafted text back
All 32 HR documents on this site can be drafted through your assistant without an account — offer, appointment and joining letters, experience and relieving letters, salary breakups and certificates, increment and appraisal letters, warnings, terminations, transfers, promotions, and every certificate in between. Nothing is website-only. Turning a draft into a real PDF or DOCX file is the one step that is not free: it needs a connected account and an entitlement, exactly as it does on the tool’s own page.
Where a document carries salary figures, your assistant is asked for what you actually know. For an offer or appointment letter you give the annual CTC and pick a structure — standard corporate, take-home friendly, and so on — and the same calculator this site uses works out the breakup, so the figures match what you would see here. A salary certificate is different: it reports what someone is genuinely paid, so it asks for the real figures and never models them.
Requires your connected account
- Read a company profile
- Search employees within one company
- Read one employee record
- List documents already issued
- Save a document as a draft
- Render a draft to a real PDF or DOCX file — additionally requires an active Tool Pass or Premium for that document type, the same paywall the tool’s own page enforces
Reading a company or employee and saving a draft use your HR workspace, which is included with Premium, so the account you connect needs Premium for those.
What each tool needs
Swipe the table sideways to see every column.
| Tool | Your MB account | Plan needed | Permission | What it does |
|---|---|---|---|---|
| List document typeslist_hr_document_types | Not needed | None | — | Reads the public catalog |
| Check a document's fieldsget_hr_document_requirements | Not needed | None | — | Reads the public catalog |
| Draft a documentdraft_hr_document | Not needed | None | — | Keeps the draft for 30 minutes, saves nothing to an account |
| Make the PDF or Word filerender_hr_document | Connected, with OAuth | Tool Pass or Premium | documents:render | Creates the file from a draft |
| Read a company profileget_company_profile | Connected, with OAuth | Premium | company:read | Reads one company |
| Search employeessearch_employee | Connected, with OAuth | Premium | employees:read | Reads one company's employees |
| Read one employeeget_employee | Connected, with OAuth | Premium | employees:read | Reads one employee record |
| List saved documentslist_hr_documents | Connected, with OAuth | Premium | documents:read | Reads one company's documents |
| Save a document as a draftsave_hr_document | Connected, with OAuth | Premium | documents:create | Adds a draft; never sends or issues it |
| Not available to any AI client. A person does these in the MB web app. | |||
The three no-account tools work straight away. The others run once you have connected your MB account and approved that permission on our consent screen. A Tool Pass covers the one document type it was bought for.
What it deliberately cannot do
Sending a document to a recipient, requesting a signature, and revoking an issued document are not available to any AI client. Those actions exist only in the MB web app, performed by a person. Drafting is separated from delivering on purpose: an assistant can prepare work for you, but it cannot put a document in front of an employee or a signatory.
Permissions and OAuth
Connecting uses OAuth 2.1 with PKCE. Your assistant never sees your MB password — you sign in on our own page, approve a specific list of permissions, and the assistant receives a token limited to exactly those.
Permissions are deliberately narrow and separate. Reading a company profile is a different permission from searching employees, which is different again from creating a document. There is no admin or all-access permission in the system at all. Any permission that touches company data is additionally bound to the single company you select on the consent screen — a token issued for one company cannot read another, even when the same account owns both.
We also refuse to offer permissions we cannot honor. Capabilities that are reserved for future features are not shown on the consent screen and cannot be granted, so a permission you approve is always one that does something.
Swipe the table sideways to see every column.
| Permission | What it allows | Tools |
|---|---|---|
| openid | Confirm who you are | — |
| Read your email address | — | |
| company:readbound to one company | Read company profile | get_company_profile |
| employees:readbound to one company | Read employee records | search_employee, get_employee |
| documents:readbound to one company | Read HR documents | list_hr_documents |
| documents:createbound to one company | Create HR documents | save_hr_document |
| documents:render | Render HR documents to PDF/DOCX | render_hr_document |
Connecting it manually
The MCP endpoint is https://mbresumebuilder.com/mcp, over Streamable HTTP. It is one shared endpoint for every client — there is no per-customer or per-workspace URL. Authorization server details are published at /.well-known/oauth-authorization-server and the protected-resource document at /.well-known/oauth-protected-resource/mcp, so a client supporting MCP’s standard discovery needs nothing else from you.
How your data is handled
Only what a specific tool call needs is sent, at the moment the assistant makes that call. Reading an employee sends that employee’s identifier and returns their record; drafting a document sends the field values for that document. Nothing is sent in the background, and there is no bulk export.
Your resume drafts are not involved at all. They live in your browser’s local storage, and MB Connect has no access to them.
Worth being explicit about: your assistant provider sees the request and the response, because that is how the assistant reads the result. If you ask ChatGPT to draft a service certificate, the field values and the resulting document pass through OpenAI; the same is true of Anthropic when you use Claude and of xAI when you use Grok. That is inherent to using an assistant, not something particular to us — but it is your data going to a third party, so it belongs in a decision you make knowingly. Our privacy policy sets out each data flow separately.
On our side, connector activity is logged as metadata only — which tool ran, whether it succeeded, how long it took, and a request ID. Document contents, employee names, salaries, and tokens are never written to those logs, and that is enforced by an automated test, not just by policy.
Disconnecting and revoking
Two independent ways, and either one is enough:
- Remove the connector inside ChatGPT, Claude or Grok. The client stops using its token.
- Revoke the grant from our side. This invalidates the token itself, so it stops working even if a client still holds a copy. This is the stronger action — use it if you are unsure who still has access.
Access tokens are short-lived, and refresh tokens rotate on every use — an old refresh token cannot be replayed after a newer one has been issued. A revoked grant cannot be quietly resurrected.
Troubleshooting
“This tool requires a signed-in MB account”
The tool needs a permission your connection does not carry. Disconnect and reconnect, and check the consent screen lists the permission that tool needs.
The connector will not finish connecting
Confirm the server URL is exactly https://mbresumebuilder.com/mcp (for Grok, https://mbresumebuilder.com/mcp/account) with no trailing path. The client must support Streamable HTTP; the older SSE-only transport is not accepted.
A tool returns “invalid arguments”
The assistant supplied a field in the wrong shape. The error names the field and what was expected — asking the assistant to retry with that correction usually resolves it.
Rendering says an entitlement is required
Rendering a real PDF or DOCX consumes the same Tool Pass or Premium entitlement the website’s generator pages use. See pricing.
A tool says the workspace is part of Premium
The tools that read a company or employee, list documents or save a draft work on your HR workspace, which is included with Premium. The connected account needs an active Premium plan; once it has one, ask the assistant to try again. Drafting a document needs no account at all.
Support
Email support@mbresumebuilder.com. Every response from the server carries a request ID — including it lets us find the exact call in our logs without you sending us any document content or employee data.
Frequently asked questions
- What is MB Connect?
- MB Connect is our Model Context Protocol (MCP) server. It lets an AI assistant you already use — such as ChatGPT or Claude — work with MB HR Documents on your behalf: look up which document types exist, check what fields a document needs, draft one, and render it to PDF or DOCX. It is a single server at https://mbresumebuilder.com/mcp, shared by every client, so both assistants get identical tools and identical permissions.
- Which assistants can connect?
- Any client that speaks MCP over Streamable HTTP. We test against ChatGPT (Developer Mode custom connectors), Claude (custom connectors), and the official MCP Inspector. We have also connected Grok as a custom connector using the sign-in address https://mbresumebuilder.com/mcp/account: connecting, signing in and drafting worked, and we have not yet seen it produce a finished PDF or DOCX. Because there is one server rather than a per-vendor integration, other clients may work too, but we have not tested them. The three no-account tools need nothing special from a client; the tools that need your account also require the client to support OAuth 2.1 with PKCE and dynamic client registration.
- How do I add MB Connect to ChatGPT or Claude?
- You add it yourself, by URL, as a custom connector. MB Connect is not listed in ChatGPT's or Claude's app directories, so there is nothing to search for. In ChatGPT, turn on Developer mode in your settings and add a custom connector (availability depends on your plan and your workspace's policy). In Claude, open the connector settings and add a custom connector. In either one, enter https://mbresumebuilder.com/mcp. The three no-account tools work straight away. The first time you use a tool that needs your account, the assistant sends you to our own sign-in page, where you approve the permissions and pick the company; your MB password is never shared with the assistant.
- How do I add MB Connect to Grok?
- Use the sign-in address, https://mbresumebuilder.com/mcp/account, not the main one. Grok only offers to sign you in at the moment you add a connector, and the main address needs no sign-in for drafting, so Grok can draft with it but never asks you to sign in and so cannot produce the file. In Grok's connector settings choose New connector, then Custom, and paste the sign-in address. A sign-in window opens on our own page; approve the access there. If Grok says the connector is unavailable, your browser may have blocked that window: allow pop-ups for grok.com and add it again. On 30 September 2026 we added it to Grok, signed in, listed the document types, drafted a letter and asked for the file, which stopped at the plan-required message the website shows too; we have not yet seen Grok produce a finished file. Requests you make in Grok pass through xAI, Grok's provider.
- What can the connector actually do?
- Nine tools. Three need no account at all — listing document types, checking a document's required fields, and drafting a document from values you supply. Six require you to connect your MB account with OAuth: rendering a draft to PDF or DOCX, reading a company profile, searching employees, reading one employee, listing issued documents, and saving a document as a draft. That is the complete list; there is nothing hidden behind it.
- Can it send, sign, or revoke documents?
- No. Sending a document to a recipient, requesting a signature, and revoking an issued document are deliberately not exposed to any AI client. Those actions exist only in the MB web app, where a human performs them directly. Drafting and creating are separated from sending and signing on purpose: an assistant can prepare work for you, but it cannot deliver a document to an employee or put anything in front of a signatory.
- What permissions am I granting?
- You approve specific, named scopes on our own consent screen before anything is shared — never a blanket 'allow this app' toggle. Scopes are narrow and separate: reading a company profile is a different permission from searching employees, which is different again from creating a document. There is no admin or all-access scope in the system. Any scope touching company data is also bound to the one company you pick on that screen, so a token issued for one company cannot read another, even when the same account owns both.
- What data leaves my browser when I use the connector?
- Only what the specific tool call needs, at the moment the assistant makes it. Reading an employee sends that employee's identifier and returns their record. Drafting a document sends the field values for that document. Your resume drafts are never involved — they live in your browser's local storage and the connector has no access to them. Your assistant provider (OpenAI, Anthropic or xAI) will also see the request and response as part of your conversation with it, because that is how the assistant reads the result.
- How do I disconnect or revoke access?
- Two independent ways, and either is sufficient. Remove the connector inside ChatGPT, Claude or Grok, which stops the client using its token. Or revoke the grant from our side, which invalidates the token itself so it stops working even if the client still holds it. Revoking from our side is the stronger action; use it if you are unsure whether a client still has a copy. Access tokens are short-lived and refresh tokens rotate on every use, so a revoked grant cannot be quietly resurrected.
- Do I need a paid plan?
- Drafting is free and needs no account. Every other tool needs a signed-in MB account. Rendering a document to a real PDF or DOCX also consumes the same Tool Pass or Premium entitlement the website's own generator pages consume, and the tools that read a company or employee, list documents or save a draft use your HR workspace, which is included with Premium, so the account you connect needs an active Premium plan for those — the connector does not create a cheaper path around the paywall, and it does not create a more expensive one either.
- It says my tool needs a scope I thought I granted. What now?
- Disconnect and reconnect the connector, and check the consent screen lists the permission the tool needs. This usually means the original connection requested a narrower set of scopes than the tool you are now calling requires. If it persists, contact support with the request ID from the error — every response carries one, and it lets us find the exact call without you sending us any document content.