How do I generate an API Key in Copilot?

Log in to your Copilot (Assembly) dashboard. Go to **Settings > API** and click 'Generate API Key'. Copy the key and paste it below.

Can the agent see my internal portal messages?

Yes, if granted access via the API Key, the agent can list and retrieve messages sent through the client portal to help you keep track of communications.

Is the billing data secure?

Absolutely. This integration uses standard API protocols and does not store your payment information. It only retrieves statuses and metadata provided by the Copilot API.

Copilot CRM (Assembly) MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Copilot CRM (Assembly)
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Copilot CRM (Assembly) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "copilot-crm-assembly": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Copilot CRM (Assembly) MCP Server

Integrate Copilot (now rebranding to Assembly), the leading client portal and CRM platform for service businesses, directly into your AI workflow.

Claude Desktop is the definitive way to connect Copilot CRM (Assembly) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Client Management — List, retrieve, and update client profiles and company associations.
Billing Automation — Monitor invoices, check statuses, and pull payment details via chat.
Portal Discovery — Search for files, messages, and custom fields within your client workspace.

The Copilot CRM (Assembly) MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Copilot CRM (Assembly) to Claude Desktop via MCP

Follow these steps to integrate the Copilot CRM (Assembly) MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Copilot CRM (Assembly)

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Copilot CRM (Assembly) MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Copilot CRM (Assembly) through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Copilot CRM (Assembly) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Copilot CRM (Assembly) MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Copilot CRM (Assembly) MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Copilot CRM (Assembly) to Claude Desktop via MCP:

create_client

Creates a new client record with identity properties (name, email) and optional company linkages. Create a new client in the portal

get_client_details

Resolves granular profile data, including contact information, associated company linkages, and system-level metadata. Get detailed information about a specific client

list_clients

Resolves client identity properties including unique identifiers, names, emails, and account status across the portal system boundary. List all clients in your Copilot CRM

list_companies

Resolves corporate entity properties such as company IDs, legal names, and primary contact associations. List all companies in your Copilot CRM

list_custom_fields

Resolves custom field definitions, including field keys, data types, and display labels used across various entities. Retrieve definitions for custom fields used in CRM

list_files

Resolves file metadata including filenames, storage paths, upload timestamps, and access permissions. List files uploaded to the Copilot portal

list_forms

Resolves form definitions, including titles, submission endpoints, and configuration metadata. List intake or feedback forms available

list_invoices

Resolves billing data including amounts, due dates, payment status, and client/company bill-to associations. List all invoices and their statuses

list_portal_messages

Resolves portal message threads, including sender/receiver identity, message content summary, and timestamps. List messages sent through the client portal

update_client

Modifies specific attributes like name or account status while preserving other entity properties. Update existing client details

Example Prompts for Copilot CRM (Assembly) in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Copilot CRM (Assembly) immediately.

"List all active clients in my CRM."

"Check the status of my pending invoices."

"Search for any files uploaded by 'Acme Corp'."

Troubleshooting Copilot CRM (Assembly) MCP Server with Claude Desktop

Common issues when connecting Copilot CRM (Assembly) to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Copilot CRM (Assembly) + Claude Desktop FAQ

Common questions about integrating Copilot CRM (Assembly) MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.