Connect Mason to your AI assistant

Before you connect

You need an authorized Mason account and access to the PM you want to connect. A connector does not create a Mason account or grant access to another company. A workspace owner may need to enable custom connectors or install Mason for the workspace first.

Read the connector privacy notice before connecting: requested data, including resident and owner information, is returned to your chosen AI host.

Mason server URL:

Connect Claude

1. Open Claude → Customize → Connectors. If Mason is listed, select it. Otherwise choose Add → Custom → Web and paste the server URL above.
2. On Team or Enterprise, an Owner may need to add Mason first.
3. Choose Connect and sign in to Mason. Check the selected PM and requested permissions, then approve the connection.
4. Start a conversation with Mason enabled and ask which Mason account is connected.

Connect ChatGPT

1. Open the Mason plugin in ChatGPT and choose Connect. If your workspace blocks it, choose + → Add custom MCP server instead, name it Mason, paste the server URL above, select OAuth, and create and install the plugin.
2. If these controls are unavailable, ask your workspace administrator.
3. Sign in to Mason, check the selected PM and permissions, and approve the connection.
4. Start a new conversation with Mason enabled and ask which Mason account is connected.

Understand permissions

mason.read allows retrieval of your connected PM’s data. It cannot save notes, change records, schedule work, or send messages. mason.write, together with mason.read, also allows the PM-chat operations available for your account, including record and workflow changes, scheduling, messages, group management, and calls.

Successful write calls take effect immediately. Your AI host controls confirmations; Mason does not show a second approval page for each change. Workflows can notify people. Mason still enforces account permissions and communication safeguards. Stop Mason blocks external SMS, email, and group messages; calls have their existing call safeguards. Scheduled or queued outreach is not proof of delivery.

The host’s requested scopes determine what you can approve. An existing read-only connection cannot gain write access through a prompt or token refresh. To change scopes, reconnect and approve the new consent request.

Try a task

• “Which Mason user and property manager am I connected as?”
• “Summarize my open maintenance work orders and explain which need attention.”
• “Show the recent vendor and tenant communication for this work order.”
• With write access: “Add an internal note to this work order saying the inspection is complete.”

Be specific about the work order and intended change. If a write times out or its result is uncertain, check Mason before repeating it to avoid duplicate effects. The connector does not process purchases or transfer money.

Disconnect or troubleshoot

In Mason, open Settings → Connected apps and revoke the connection. Its tokens stop working. Disconnecting does not delete existing Mason records or data already returned to the host; use that host’s controls to manage its stored conversations.

If sign-in fails, confirm your Mason account has access to the selected PM. If data belongs to another PM, reconnect to that PM with an account authorized for it. If a tool requires write permission, inspect the scopes on your connection and reconnect if appropriate. A stopped communication requires a PM’s review of the stop in Mason.

Support

Contact hello@thisismason.com with your AI host, PM name, approximate time, and the error message. Do not send passwords, access tokens, full conversation transcripts, or unnecessary resident information.

Connector privacy notice · Terms of service