Connect an AI Assistant to Mosic

You can connect an AI assistant such as Claude Desktop to your Mosic account using the Model Context Protocol (MCP). Once connected, you can manage tasks, projects, CRM records, and more using plain English — the AI acts on your behalf using your own Mosic permissions.

What You Can Do

After connecting, you can ask the AI assistant to:

View your workspaces and navigate between them
Create, update, and complete tasks
Assign tasks to teammates and set due dates
Search across projects, tasks, pages, and documents
Manage leads, deals, and customer records (if your workspace has CRM)
Handle support tickets (if your workspace has Helpdesk)
Search and send email conversations (if your workspace has Communication)
View and manage activity logs on any record

The AI sees and does only what you have permission to do in Mosic. If you are a Viewer in a workspace, the assistant sees only that workspace’s read-only content. Your password is never shared with the AI.

What You Need

An active Mosic account that is a member of at least one workspace
Claude Desktop installed on your computer
Node.js 18 or later installed (to run the connection tool)

Connecting Claude Desktop

Step 1 — Open the Claude Configuration File

The configuration file for Claude Desktop is stored on your computer. Open a terminal and run:

macOS:

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows:

notepad %APPDATA%\Claude\claude_desktop_config.json

Linux:

nano ~/.config/Claude/claude_desktop_config.json

If the file does not exist, create it with an empty JSON object:

{}

Step 2 — Add Mosic to the Configuration

Open the file in a text editor and add the following inside the outermost braces, replacing https://your-mosic-site.com with the URL of your Mosic site (no trailing slash):

"mcpServers": {
  "mosaic": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://your-mosic-site.com/api/method/mosaic.api.mcp.endpoint.handle_mcp",
      "--allow-http"
    ]
  }
}

If you use multiple Mosic accounts (for example, one for work and one for personal projects), add a separate entry for each:

"mcpServers": {
  "mosaic-work": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://work.your-mosic-site.com/api/method/mosaic.api.mcp.endpoint.handle_mcp",
      "--allow-http"
    ]
  },
  "mosaic-personal": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://personal.your-mosic-site.com/api/method/mosaic.api.mcp.endpoint.handle_mcp",
      "--allow-http"
    ]
  }
}

Step 3 — Restart Claude Desktop

Quit Claude Desktop completely (not just closing the window) and reopen it. The Mosic connection loads automatically when Claude starts.

Step 4 — Authorize on First Use

The first time you ask Claude to work with Mosic, it opens a browser tab for you to sign in and approve the connection:

If prompted, log in to your Mosic account
Click Allow or Authorize to grant Claude access to your data
When you see a success message, close the browser tab
Claude receives your access credentials automatically and completes the task

After the first authorization, you do not need to approve again unless you revoke access or your credentials expire.

Step 5 — Verify the Connection

In a new Claude conversation, try asking:

List my Mosic workspaces

Claude connects to Mosic and shows the workspaces you have access to. If you see the list, the connection is working correctly.

What Each Role Can Do Through the AI

The AI assistant uses your exact Mosic permissions — there is no separate AI permission layer.

Your Role	What the AI Can Do
Admin	Create, read, update, and delete all documents in the workspace; manage workspace members
Editor	Create, read, and update documents; cannot delete the workspace
Member	Create and update documents you own; read all documents in the workspace
Viewer	Read-only access to all workspace documents
Guest	Limited read access to shared documents only

The AI cannot access workspaces you are not a member of.

Asking the AI to Do Things

Here are some examples of requests you can make in natural language.

Tasks and Projects

Create a task called “Review Q2 budget” in the Marketing project, assign it to sarah@example.com, and set the due date to Friday.

What tasks are assigned to me in the Engineering workspace?

Mark the “Finalize onboarding docs” task as complete.

Searching

Search for any document mentioning “API documentation” in the Customer Portal workspace.

Pages

Read the content of the “Getting Started” page in the Documentation space.

CRM

Convert the lead for “Acme Corp” into a customer.

Mark deal #1042 as won.

Show me the current pipeline view for the Sales workspace.

Support Tickets

Add an internal comment to ticket #223 saying “Awaiting customer reply per email.”

What’s the SLA status of ticket #223?

Email

Search my emails for messages from the client about the proposal.

Send a reply to the conversation about “Q3 Planning” saying we can proceed.

Activities

Show me the recent activity on the “Acme Corp” customer record.

Log a call on the lead for “Riverside Health” — 15 minutes, outbound, interested in a demo.

List all activities logged against the “Q3 Marketing Campaign” project this week.

Real-Life Ways People Use This

These are real scenarios Mosic users handle with their AI assistant every day.

Starting Your Morning

You open Claude and type:

What tasks are due today or overdue in the Design workspace?

Claude calls Mosic with your workspace ID, finds tasks with a due date of today or earlier that aren’t done, and gives you a clean list with their priority and who they’re assigned to. You start the day knowing exactly what needs your attention first.

If you work across multiple workspaces, you can ask about each one separately:

What’s on my plate in the Engineering workspace?

Running a Team Weekly

Before your team meeting, you ask:

What tasks in the Design workspace are marked as completed, and which ones are blocked?

Claude finds all completed tasks and all tasks with “Blocked” status in that workspace, grouped by stage. You get a ready-to-share summary for your meeting — no digging through lists manually.

Onboarding a New Client

When a new customer signs up, you say:

Create a customer for “Northwind Traders”, then create a project called “Northwind Onboarding” in the Sales workspace with a task list called “Kickoff Steps”, and add a task “Schedule kickoff call” assigned to me.

Claude creates the full chain — customer, project, task list, and first task — in one go. What used to be a multi-step manual process becomes a single sentence.

Following Up on a Lead

Your sales team qualifies a new lead. You ask:

Convert the lead for “Riverside Health” in the Sales workspace into a customer, then create a deal for 45,000 in the Sales pipeline.

Then as a separate request:

Mark the new deal as won.

Claude runs the conversion workflow, creates the deal, and marks it won — in two separate calls. By the time you’re back from lunch, the CRM is already updated.

Finding a Lost Email

You remember a client mentioned something in an email but cannot find it. You ask:

Search my Mosic messages in the Support workspace for any message from “paramount@example.com” mentioning “contract” or “renewal”

Claude searches across all email conversations and finds the thread instantly. You reply while the context is fresh.

Reassigning a Project Manager

A project manager goes on leave and you need to reassign their projects. You ask:

Change the manager of the “Q3 Marketing Campaign” project in the Marketing workspace to jane@example.com.

Then as a separate request:

Find all tasks in the Q3 Marketing Campaign assigned to the old manager and reassign them to jane@example.com.

Claude updates the project manager and reassigns the open tasks. Handovers that used to take an hour take a single message.

Rate Limits

To keep Mosic responsive for everyone, the AI connection has usage limits:

120 requests per minute per user across all tools
20 requests per minute for any single tool

If you hit a limit, wait about a minute and try again.

Keeping Your Account Secure

Your password stays private. The connection uses OAuth 2.1 — your password is never sent to the AI assistant or stored outside Mosic.
Access is tied to your account. The AI can only do what you have permission to do. It cannot access workspaces you are not a member of.
You can revoke access at any time. See “Disconnecting an AI Assistant” below.

Disconnecting an AI Assistant

To stop an AI assistant from accessing your Mosic account, clear its locally stored credentials:

You can also clear the local credentials cache to prevent the AI from attempting to reconnect:

macOS / Linux:

rm -rf ~/.mcp-auth/

Windows (PowerShell):

Remove-Item -Recurse "$env:LOCALAPPDATA\mcp-auth"

Troubleshooting

”Authentication failed” or “Invalid credentials”

Clear the local credentials cache and try again:

rm -rf ~/.mcp-auth/

Then ask Claude to use a Mosic tool. A browser tab opens so you can authorize again.

”Connection refused” or the request hangs

Open the Mosic URL in your browser to confirm the site is reachable.
Check that the URL in your config file is correct and uses https://.
Ask Claude to try the request again.

”Permission denied” or “Access denied to workspace”

You may not be a member of that workspace. Ask Claude to “List my Mosic workspaces” to see which workspaces you have access to.
If the workspace you expect is missing, contact the workspace admin and ask to be added.

Claude Desktop shows “MCP server not found”

Confirm the config file is at the correct path for your operating system.
Confirm the JSON is valid — no missing commas, no mismatched braces.
Make sure npx works in your terminal by running npx --version.
Restart Claude Desktop after editing the config file.

Tasks — Creating and managing tasks in Mosic
CRM — Managing customers, leads, and deals
Helpdesk — Support tickets and SLA tracking
Communication — Email channels and conversations
Activity Log — Recording and tracking interactions