Assembly MCP for AI. Access client, company, and workspace data instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Assembly MCP manages your professional service data. It lets any compatible AI client read structured information from your Assembly platform, handling clients, companies, users, workspaces, and internal notes.
Instead of logging into multiple dashboards to gather records, you can ask your agent to list all active clients or pull the full details for a specific company record.
This is essential for building automated workflows around service account data.
What your AI can do
Get client
Gets all details for one specific client record.
Get company
Retrieves the full information set for a single company.
Get note
Fetches the content of one specific note by its ID.
Pull lists of every client record stored in Assembly.
Get specific information for any company connected to your account.
Access details about individual users, including their roles and contact information.
Check the contents and members of specific operational workspaces.
Retrieve specific notes or compile lists of all existing internal documents.
Ask an AI about this
Waiting for input…
Assembly: 10 Tools for Professional Services Data
These tools allow your agent to read specific data points—from client lists to individual company details—across the entire Assembly platform.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Assembly on VinkiusGet Client
Gets all details for one specific client record.
Get Company
Retrieves the full information set for a single company.
Get Note
Fetches the content of one specific note by its ID.
Get User
Gets all details about an individual user account.
Get Workspace
Retrieves the contents and members of a single operational workspace.
List Clients
Lists every client record available in your Assembly account.
List Companies
Provides a list of all companies linked to your platform.
List Notes
Lists metadata for all internal notes created in the system.
List Users
Returns a complete list of every user account.
List Workspaces
Lists metadata for all active workspaces.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Assembly, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Assembly. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Problem of Fragmented Data
Right now, gathering a full picture of a client is a manual chore. You open the main dashboard to see who they are. Then you switch tabs to check associated companies and click into separate sections just to find notes or user contact details. It’s constant copying, pasting, and juggling context switches.
With this MCP, your agent pulls all those data threads together automatically. Instead of switching screens, you ask a single question—like 'Give me the full profile for Client X'—and get structured, actionable data back instantly.
Getting Specific Records with `get_user`
You don’t have to guess where a piece of information lives. If you need the full record for a single person, you use `get_user`. This avoids having to scroll through dozens of list views just to find their contact details or role.
It's simple: you specify the ID, and your agent delivers the exact data payload you asked for. It cuts out the guesswork entirely.
What your AI can actually do with this
Managing client relationships means juggling dozens of different pieces of information—who the main contact is, what companies they work with, and what notes were taken last month. This MCP lets your agent read all that structured data from Assembly. You can ask it to list every active user or check out details for a specific workspace record.
It pulls together client records, company profiles, and internal notes into a single stream of information you can act on. Instead of manually navigating through tabs or running separate reports, your AI client accesses the core data directly. Vinkius hosts this MCP so that whether you use Claude, Cursor, or any other compatible agent, you get one place to manage all your professional service data.
019dd0bd-10b0-73c0-b9cc-06c94ef08a83 Here's how it actually works
The bottom line is: your AI client handles the connection and data translation, so you just talk to it.
Your agent connects to this MCP using your API key. This establishes the link to your Assembly platform data.
You prompt your AI client with a request, like 'List all companies associated with Client X.'
The agent translates that natural language command into a function call (e.g., list_companies) and receives structured data back for you to use.
Who is this actually for?
Account managers who spend half their day aggregating status reports. Consultants needing immediate access to structured client history. Operations analysts building internal process dashboards.
Checks the full details of a client using get_client and then cross-references that with notes or users to prepare a status update.
Needs to quickly list all companies (list_companies) and check which workspace they belong to before starting a meeting.
Uses the MCP to programmatically gather lists of users or workspaces to audit permissions or build automated onboarding checklists.
What Changes When You Connect
Stop switching between tabs. Instead of going to the client dashboard, then checking the notes tab, you can ask your agent to combine that information using get_client and list_notes in one query.
Build better onboarding flows. Use list_users and list_workspaces together so your agent can check who needs access and which operational area they belong to.
Audit data quickly. Need to know every company associated with a client? You don't have to click through; the MCP handles that relationship mapping for you.
Never miss a detail again. If a project note is crucial, use get_note directly instead of digging through folders to get the exact content needed for a report.
Centralized view of relationships. By using tools like list_clients, list_companies, and get_workspace, you see the entire organizational picture—who reports to whom and what projects are active.
See it in action
Client Status Report Generation
A manager needs a status report combining client names, their primary company, and the last note date. They ask their agent to use list_clients combined with get_company and then check specific notes using get_note. The agent compiles this data into a single table ready for stakeholders.
Onboarding New Team Members
A new team member needs to know their access level. They ask the agent to run list_users and check if they are added to key operational areas using get_workspace. This prevents them from having to manually verify permissions with IT.
Auditing Company Links
The finance team suspects some client accounts aren't linked correctly. They ask the agent to run list_clients and then systematically check the associated companies using get_company for every record, identifying gaps.
Project Scope Review
A consultant needs to review all materials related to a specific project. They ask the agent to find the workspace (get_workspace) and then list any associated notes (list_notes), ensuring nothing was missed before writing the proposal.
The honest tradeoffs
Treating Assembly like a spreadsheet
Trying to manually copy client names from one screen and paste them into another system, losing context or requiring multiple API calls.
Use the MCP's list_clients tool. It gathers the complete list in structured format, letting your agent process all records at once.
Forgetting which data belongs where
Searching for a client's contact info only to find an old note instead, because they weren't sure if the user or company record was up to date.
Always start by verifying the specific resource you need. If it’s about people, use get_user. If it’s about the legal entity, use get_company.
Over-relying on a single view
Assuming that because the user is visible in one workspace, they are automatically linked to all relevant companies and clients.
Run multiple queries. Check list_users first, then run get_workspace, and finally cross-reference with get_company to build a complete picture.
When It Fits, When It Doesn't
Use this MCP if your process requires combining data points from multiple Assembly entities into one single report or workflow. For example, you need the client name (list_clients), combined with the related company details (get_company), and the last conversation summary (get_note). Don't use it if all you need is to edit a record—you still have to go to Assembly to do that. Only use this MCP for reading, retrieving, listing, or auditing data points across the platform.
Questions you might have
How do I use list_clients to find all my accounts? +
Use list_clients when you need a full roster of every client in your system, giving you an overview of who is connected. This returns the basic identifying information for bulk processing.
What's the difference between list_companies and get_company? +
Use list_companies when you want a roster of all companies in your account. Use get_company when you already know the specific company ID and need all its detailed records.
Can I use list_users to see who works on a project? +
Yes, list_users gives you every user account. To find out which users work on a specific initiative, combine it with get_workspace by referencing the workspace ID.
Does get_note retrieve old notes I can't find? +
The get_note tool retrieves a specific note based on its unique identifier. If you need to search for an old topic, first run list_notes to check the metadata and IDs.
How do I use list_workspaces to see all active project areas? +
The MCP lists every workspace you have access to. After listing them, you'll need the specific ID to run get_workspace and pull detailed information about that area.
Can I use list_notes to filter for notes written within a specific date range? +
Yes, you can pass start and end parameters. This lets your agent query only the notes from a certain time frame without having to check every single record.
If I know a client's name, how do I link that data to find their associated company with get_company? +
You must first use get_client to retrieve the unique ID. Then, you pass that required ID into get_company so the MCP can pull linked records correctly.
Are the results from list_users limited by my account permissions? +
Absolutely. The MCP respects your API scope settings. It won't return data for any user outside of your organization's defined boundaries, keeping all information secure and relevant.
Where do I find my API Key? +
Your API Key can be found in your Assembly web portal under Settings > API.
What access does this MCP need? +
It requires the REST API Key, giving access to clients, companies, users, and notes.
Can I browse workspaces and internal notes through the AI agent? +
Yes. Use list_workspaces to see all workspaces and get_workspace to inspect a specific one. For notes, list_notes retrieves all entries and get_note fetches the full content of a specific note by ID.
We've already built the connector for Assembly. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.