Skip to main content

AI assistant connections

Your assistant, your practice, your permissions.

SA-ArchPro publishes a Model Context Protocol connector so the AI assistant you already use can read your practice and project information and draft working data for you, under your own permissions, with every action recorded.

Set-up stepsDeveloper details

What it is

A governed window, not a back door.

The Model Context Protocol (MCP) is an open standard that lets an AI assistant call a named set of tools on a service you authorise. SA-ArchPro’s connector exposes a fixed catalogue of 41 tools. Each one runs as the member who connected the assistant, is checked against that member’s SA-ArchPro role, and is written to the practice’s audit trail under their identity. Anything not in the catalogue does not exist to the assistant, which is a stronger guarantee than a setting that could be switched. It works with Claude, ChatGPT, Grok and any other MCP-capable client.

Before you start

Two switches, then one approval per person.

1. Platform switch

SA-ArchPro operates this one. The connector ships dark and is enabled on the platform by SA-ArchPro. If you cannot find the settings below, it has not been enabled yet.

2. Practice switch

A practice owner or admin opens Practice Settings → AI Assistant Access and turns on Allow personal AI assistants. This is practice-wide consent. Turning it off stops every connection at once; the connections are kept, and work again when it is turned back on.

3. Each member

Each member then generates or approves a connection under My Account → AI Assistant Connections, and approves the consent screen when their assistant asks.

Information an assistant retrieves leaves SA-ArchPro and is handled under that assistant provider’s own privacy terms. Approving a connection is a disclosure decision; only connect an assistant you trust with your practice’s information.

Connect from your assistant

Paste one address, sign in, approve.

The connector address is the same for every assistant:

https://mcp.sa-archpro.com/mcp

The exact menu names may differ as each product evolves; the shape of the flow does not.

Claude

  1. On claude.ai open Settings → Connectors.
  2. Choose Add custom connector and paste the address above.
  3. Choose Connect, sign in to SA-ArchPro and approve.

Also works in Claude Desktop, and in Claude Code with claude mcp add --transport http sa-archpro https://mcp.sa-archpro.com/mcp

ChatGPT

  1. Open Settings → Connectors (Developer mode or Apps, depending on your plan).
  2. Choose Create, enter the address above as the MCP server URL, and select OAuth.
  3. Choose Connect, sign in to SA-ArchPro and approve.

Grok

  1. On grok.com open Connectors.
  2. Choose New connector → Custom and paste the address above.
  3. Connect, sign in to SA-ArchPro and approve.

What your assistant can do

41 tools, grouped by what they touch.

Reads return what the member can already see in SA-ArchPro. Writes create working data a person can correct in the app: drafts, tasks, time, appointments, register entries and templates. Tools marked fee-gated answer only when the member’s role holds fee permission, and every fee figure is a percentage, never an amount.

Practice7

  • Who am Iget_meThe signed-in person this connection acts for, their role, and the server time.
  • Get practice profileget_practice_profileThe practice’s registered name, SACAP registration and address. No financial data.
  • Get practice summaryget_practice_summaryProject counts, hours logged in the last 30 days and invoicing progress, as percentages only.
  • Practice overspendget_practice_overspendHours spent on the practice itself rather than on projects, by category and person. Fee-gated.
  • List stage deliverable templateslist_deliverable_templatesThe standard stage-deliverable breakdowns used to set up new projects.
  • Create a stage deliverable templatecreate_deliverable_templateAdd a template that shapes future projects. Existing projects are unaffected.
  • Update a stage deliverable templateupdate_deliverable_templateAmend a template. Existing projects are unaffected.

Projects5

  • List projectslist_projectsLightweight project cards: title, number, SACAP stage, status and client name.
  • Get projectget_projectOne project in detail: stages appointed, site address, milestones. Client by name only.
  • Get project statusget_project_statusA rollup of stage, progress, hours, task counts, open risks and milestones.
  • Get project teamget_project_teamConsultants, contractors and suppliers on a project, by name and discipline. No contact details.
  • Get project fee summaryget_project_fee_summaryEarned value, cost and invoicing by stage, as percentages only. Fee-gated.

Tasks and time11

  • Get project tasksget_project_tasksTasks with status, assignee and due date, plus the stage deliverables they sit under.
  • Create a project taskcreate_taskAdd a task. It starts in To Do.
  • Update a project taskupdate_taskAmend a task’s title, due date, assignee, priority, estimate or stage.
  • Move a task across the boardset_task_statusMove a task between To Do, In Progress, Blocked and Done, with the same time tracking the board runs.
  • Log time against a projectlog_timeRecord time on the member’s own timesheet. Never anyone else’s.
  • Amend a timesheet entryupdate_time_entryAmend one of the member’s own entries.
  • Get my timesheet summaryget_my_timesheet_summaryThe member’s own hours over a date range, by project and week.
  • Get project timesheet summaryget_project_timesheet_summaryHours on a project by person and week. Fee-gated.
  • What the caller is working on nowget_active_workWhether overtime is running and which tasks are tracking time right now.
  • Start overtimestart_overtimeKeep In Progress tasks tracking after office hours. Confirmed with the member first.
  • End overtimeend_overtimeStop after-hours tracking for the day.

Documents8

  • List project documentslist_project_documentsNames and metadata of files on a project. Metadata only, never the file.
  • Get document metadataget_document_metadataName, type, size and upload date of one file. No contents, no download link.
  • Search project documentssearch_project_documentsFind files by name across a project or the practice. Contents are not searched.
  • List document templateslist_document_templatesThe document types the practice can generate and the inputs each needs.
  • List generated documentslist_generated_documentsGenerated documents with number, type, status and revision. Metadata only.
  • Get generated documentget_generated_documentOne generated document’s number, status and revision history. Not the rendered file.
  • Generate a draft documentgenerate_documentCreate a new document as a draft through the normal workflow. Fee proposals are excluded.
  • Revise a draft documentrevise_documentCreate a new working revision of a document. History is append-only.

Contacts and quotes3

  • List practice contactslist_contactsClients, consultants, contractors and suppliers by name and an opaque handle only.
  • List quoteslist_quotesQuotes and their lifecycle state. No fee, total, rate or instalment is returned.
  • Get quoteget_quoteOne quote’s number, title, state and dates. No financial information.

Risks3

  • List a project’s risks and RAID entrieslist_project_risksThe risk register: risks, assumptions, issues, dependencies and decisions.
  • Add a risk or RAID entrycreate_riskAdd one entry to the register.
  • Update a risk or RAID entryupdate_riskAmend one entry, including its probability and impact.

Calendar and email2

  • Create a calendar appointmentcreate_calendar_eventPut an appointment in the practice calendar. Confirmed with the member first.
  • Draft an emaildraft_emailSave a draft in the member’s Email Portal. It cannot send; the member reviews and sends in SA-ArchPro.

User Guide2

  • Search the User Guidesearch_user_guideFind the Guide topics that explain how to do something in SA-ArchPro. Product documentation, no practice data.
  • Read a User Guide topicget_user_guide_topicOne topic’s steps and tips, and who in the practice it applies to.

What it can never do

Absent is stronger than switched off.

Absent, not gated

There is no tool to send, sign, issue, approve, void or delete anything, and none that returns a document’s bytes or a download link. No permission, role, setting or flag reaches these. They remain actions a registered professional performs in SA-ArchPro, because documentation issued out of a practice carries that person’s professional liability.

Gated by role

Fee, quote and timesheet figures are returned only when the connecting member’s SA-ArchPro role holds the relevant permission. A refusal there is a permission question a practice owner can answer; it is the same rule the app applies to that member.

No personal details

Client, consultant, contractor, supplier and staff personal details, including email addresses, telephone numbers and ID numbers, are never exposed. Contacts are referenced by name and an opaque handle, and SA-ArchPro resolves addresses on its own side when an email draft is saved.

Never wider than you

The assistant acts as the connected member and can do nothing that member cannot. It cannot see another practice’s data, act for another person, log time on anyone else’s timesheet, or price a commission.

Security and revocation

Standard OAuth, short tokens, one switch to end it.

OAuth 2.1 with PKCE

Every connection is authorised through OAuth 2.1. PKCE with the S256 method is mandatory, clients are public (there is no client secret to leak), and the consent screen is served by SA-ArchPro itself, never by the assistant.

Token lifetimes

Access tokens last one hour. Refresh tokens last 30 days from first issue, after which the member is asked to consent again. Access also ends when the account is disabled or the member’s role changes.

Audited and revocable

Every write is recorded in the practice audit trail under the member’s identity. A member revokes their own connection under My Account; an owner or admin stops every connection at once by turning off the practice switch.

For developers

Discovery, scopes and registration.

MCP endpoint
https://mcp.sa-archpro.com/mcp (Streamable HTTP)
Authorisation server metadata
https://mcp.sa-archpro.com/.well-known/oauth-authorization-server
Protected resource
https://mcp.sa-archpro.com/.well-known/oauth-protected-resource/mcp
Consent screen
https://sa-archpro.com/mcp/consent
Scopes
mcp:read mcp:write
Client type
Public clients only. PKCE S256 is mandatory; there is no client secret.
Registration
Dynamic client registration (RFC 7591) and Client ID Metadata Documents are both supported.
Token lifetimes
Access token 1 hour. Refresh token 30 days from first issue, then re-consent.
Tool catalogue
41 tools, returned by tools/list in a deterministic order.

How connections are handled is set out in the Privacy Policy and the Terms of Service. Questions and security disclosures go to Support.

Start your free trial