Workspace369 (one word, 369) is a client-work platform with a public MCP server and HTTP API; it is not Workspace 365.
Workspace369 publishes a remote MCP server. MCP, the Model Context Protocol, is the open standard AI apps use to connect to tools and data. Once your workspace is connected, you can ask an AI app in plain language to look up a client, draft an invoice, book a job, reply to a lead, or check which workflows will fire, and it happens in your workspace.
Every action runs as you. An AI app can never see or change more than you can in the app yourself.
What an AI app can do
Through the connection an AI app can:
- Look up clients, inbound requests, notes, projects, tasks, invoices, proposals, payments, time entries, calendar events, booking pages, and team availability.
- Create and update clients, notes, projects, tasks, boards, calendar events, reminders, time entries, catalog services, draft invoices, and draft proposals.
- Record invoice payments, invoice finished jobs, and record whether a proposal was accepted or declined.
- Ask to send an invoice or a proposal to its client, reply to a lead, send an SMS or email from the inbox, or text up to 30 recipients at once. These wait for your approval in the app.
- Search inbox messages, read task comments, review a workflow's definition and run history, test a workflow on sample data, and turn a workflow off.
Every tool, with the access it requires, is listed in the MCP tools reference.
What an AI app cannot do
Some actions are deliberately not available through MCP. They stay in the Workspace369 app:
- Delete clients, invoices, proposals, projects, tasks, or events. Cancelling an event and archiving a request are the strongest actions available.
- Invite, remove, or suspend team members, or change anyone's permissions.
- Create, edit, or turn on a workflow, or retry a failed run. A workflow runs a list of steps that a connected app cannot show up front, so these are done in the app or with AI AutoPilot. A workflow that is already on keeps running when its trigger happens, including a trigger caused by a change made through a connected app.
- Create, edit, or publish intake forms, because their consent wording is a compliance record.
- Create or rename custom fields or client pipeline stages. An app can fill in the custom fields you already defined and move a client between your existing stages.
- Send marketing campaigns.
- Upload files. An app can attach files that already exist in workspace storage, and only through AI AutoPilot today.
How access works
Four things decide what a connected app can do:
- A workspace admin has turned MCP on. MCP is off for every workspace until someone with the Manage MCP connections permission enables it. See Enable MCP and manage connected apps.
- Your own permissions. Each call is checked against the module permissions your role grants, and members limited to specific clients see only those clients. If you cannot view prices, amounts are hidden from the app too.
- The access you granted the app. When you connect, you choose a level for each area the app asks for, such as None, View, or Edit for Clients. An app never gets more than you approved.
- The workspace's Token balance. Every successful call is paid for in Tokens from the same balance as in-app AI. Refused and failed calls are free.
How MCP access is controlled and billed explains each check, the Token cost of each kind of call, and what the activity log records.
Which apps work
Any app that supports remote MCP servers over the Streamable HTTP transport can connect. Claude (web and desktop), ChatGPT, Cursor, Windsurf, and VS Code with Copilot are the common ones. Connecting uses your Workspace369 sign-in, so there is no API key to copy for these apps.
Scripts and headless agents that cannot open a sign-in page use a personal access token instead.
Where to find MCP in Workspace369
| You want to | Go to |
|---|---|
| Turn MCP on for a workspace, approve specific apps, see every member's connections, read analytics and the activity log | Settings, then AI, then AI Connections (MCP) |
| Connect your own AI app, see your own connections, create a personal access token | Settings, then AI, then AI Connections (MCP): Your AI apps and Personal access tokens |
MCP and AI AutoPilot
AI AutoPilot, the assistant built into Workspace369, uses the same tools with the same permission checks. The differences are where you use it and how sends are confirmed:
- AI AutoPilot runs inside the app and always shows a confirmation card before it sends anything to a client, turns a workflow on, retries a failed workflow run, or changes a teammate's availability. Tool calls inside an AI AutoPilot conversation are not charged separately; the conversation is.
- A connected AI app runs outside Workspace369, so sends are held for your approval in the Workspace369 app instead, unless you turned on Send without asking for that connection. Each tool call is charged in Tokens, and the scopes you granted limit what it can reach.
Next steps
- An admin enables MCP: Enable MCP and manage connected apps.
- Each member connects their app: Connect an AI app to your workspace.
- Try a read-only prompt first, such as "Which invoices are overdue?", before asking the app to create or send anything.