Bring Client Management
to LlamaIndex
Learn how to connect Assembly to LlamaIndex and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Assembly MCP Server?
Assembly
The Assembly MCP Server allows AI agents to interact with your Assembly platform data seamlessly.
What you can do
- Retrieve clients, companies, and users.
- Access workspaces and CRM details.
- Manage notes and internal data.
How it works
Connect your Assembly account via your API Key to manage your professional service data dynamically.Built-in capabilities (10)
Get details for a specific client
Get details for a specific company
Get a specific note
Get details for a specific user
Get a specific workspace
List all Assembly clients
List all Assembly companies
List Assembly notes
List all Assembly users
List all Assembly workspaces
Why LlamaIndex?
LlamaIndex agents combine Assembly tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Assembly tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Assembly tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Assembly, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Assembly tools were called, what data was returned, and how it influenced the final answer
Assembly in LlamaIndex
Assembly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Assembly to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Assembly in LlamaIndex
The Assembly 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Assembly for LlamaIndex
Every tool call from LlamaIndex to the Assembly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Assembly tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
