Your Brieff context.
In ChatGPT and Claude.

MCP stands for Model Context Protocol. It is a standard way for AI assistants to connect to software. The Brieff MCP lets an assistant such as ChatGPT or Claude read authorised Brieff information and carry out supported changes when you ask.

No. ChatGPT or Claude is the assistant you talk to. MCP is the connection that lets it work with Brieff. You describe what you need, and the assistant uses its connected tools to help.

Brieff already prepares for meetings, captures conversations and creates summaries. MCP makes that existing context available in your assistant, where you can use it for another piece of work. For example, combine a saved meeting summary with financial data, or turn a client's needs into a proposal draft.

The Brieff MCP works with ChatGPT and Claude. You need an account and workspace that allow the Brieff connection. MCP is a shared standard, but that does not mean every assistant supports the same workflows or setup.

Yes, when your assistant also has an authorised Xero connection with access to the reports you need. Ask it to bring together a saved Brieff meeting summary and a Xero profit and loss report, then draft a briefing or questions for your next meeting. Xero is connected separately and has its own setup, permissions and plan requirements. This is separate from Brieff's Xero Practice Manager integration.Xero MCP setup and requirements

Yes, with a compatible QuickBooks Online connector authorised in the same assistant. For example, Claude offers the Meridian Connector for QuickBooks from Pilot. Intuit also provides a developer MCP server that needs its own setup. The connector you choose determines the available data, supported assistant and permissions. This is a separate connection, not a direct Brieff sync.QuickBooks connector for Claude

Yes, with Brieff and Ignition connected to the same supported assistant. Use Brieff's saved meeting summary and client context to identify the agreed needs, then ask the assistant to prepare a draft proposal through Ignition's MCP connection. Review the scope, services, pricing and terms before sending. Proposal changes happen in Ignition under your Ignition permissions.How Ignition's MCP connection works

Each tool is connected and authorised separately in your assistant. Brieff supplies your client context; another connection supplies its own information or actions. Tools such as Xero, Ignition, Notion and Canva offer their own MCP connections, with their own setup and account requirements. The assistant brings them together for your request. This does not set up an automatic sync between Brieff and every other app.

Your saved Brieff summaries remain in Brieff. The assistant can read an existing summary and use it to draft a briefing, proposal outline or follow-up in your conversation. It can also synthesise available meeting sources when asked. MCP does not overwrite a generated summary or run Brieff's summary-generation process.

Work with accessible client and Internal Workspace context, meetings and available source material, Actions, Goals and recorded Goal progress, plus published Check-in responses and completion tracking. Ask for meeting preparation, a catch-up, a past discussion or work that needs attention. Answers depend on the records and sources you can access.

With explicit editing consent and the required permissions, create an individual Action, change its supported fields, assign it to an eligible person, or complete and reopen it. You can also append, insert or revise selected content in a meeting agenda or supported notes. Existing read-only connections stay read-only unless you approve an upgrade.

The private document called Internal notes cannot be edited through MCP. There is a separate document called Meeting notes in an Internal Workspace meeting; targeted edits to that document are supported, as are Client notes in a client meeting. The assistant must select the correct meeting and document before changing anything.

Use Brieff to edit private Internal notes or generated summaries, change Goals or Targets, create or schedule Check-ins, send meeting materials and reminders, delete or archive records, and make bulk changes. These operations are outside Brieff's MCP tools. Separately connected tools have their own capabilities and permissions.

Add the Brieff connection in your supported assistant, sign in with your Brieff account and select your firm. Review the access requested and choose whether to allow supported edits. Your firm or assistant workspace may require administrator approval. Start with a specific client, meeting or question.Connection setup guide

You need an existing Brieff account, access to the selected firm and an assistant account that supports the connection. Your assistant and any other tools you connect set their own plan requirements and charges. Those accounts and subscriptions are separate from Brieff.

Access follows your current Brieff membership, record permissions, firm AI connection policy and the access you approve. Connecting does not grant access to otherwise restricted clients or workspaces. Editing also requires explicit consent and permission to change the selected record.

The assistant provider receives the Brieff information returned for your authorised request. Its terms and your account or workspace settings govern that information in the assistant, including history, retention and model-training settings. Use an account your firm has approved for client information. Brieff's own AI data commitments do not replace the external provider's terms.

Yes. Review or revoke the connection in Brieff's Settings under AI connections, and remove it in your assistant too. Revocation stops subsequent authorised access. It does not erase information already in an assistant conversation; use that provider's history and retention controls for that content.