Bring Direct Mail
to LlamaIndex
Learn how to connect AMcards to LlamaIndex and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the AMcards MCP Server?
Connect your AMcards account to any AI agent and take full control of your automated physical relationship management and high-fidelity gifting workflows through natural conversation.
What you can do
- Physical Card Orchestration — Programmatically dispatch personalized greeting cards with custom messages directly to any address without leaving your chat
- Drip Campaign Intelligence — Enroll leads or clients into automated card-sending sequences to maintain a perfectly coordinated relationship lifecycle in real-time
- Template Management Architecture — Access and monitor your complete library of card templates to ensure your high-fidelity brand voice is consistently applied
- Delivery & History Tracking — Retrieve detailed historical records of sent cards and monitor their delivery status directly through your agent for instant reporting
- System Monitoring — Access account-level profile metadata and verify API connectivity directly through your agent to maintain high-fidelity operations
How it works
1. Subscribe to this server
2. Retrieve your Access Token from your AMcards dashboard (Settings > API)
3. Start sending real mail and gifts from Claude, Cursor, or any MCP client
No more manual logging into mailing portals to send thank-you notes. Your AI acts as your dedicated relationship engineer and physical mail coordinator.
Who is this for?
- Sales Professionals — instantly send personalized 'Thank You' cards after a meeting using natural language commands
- Customer Success Teams — automate the dispatch of appreciation gifts and follow-ups without leaving your workspace
- Real Estate Agents — orchestrate long-term high-fidelity drip campaigns to maintain top-of-mind awareness through simple AI queries
Built-in capabilities (7)
com service API. Verify AMcards API connectivity
Retrieve card sending history
List greeting card templates
List active webhooks
List automated drip campaigns
Send a personalized greeting card
Start a drip campaign for a user
Why LlamaIndex?
LlamaIndex agents combine AMcards tool responses with indexed documents for comprehensive, grounded answers. Connect 7 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 AMcards tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain AMcards tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query AMcards, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what AMcards tools were called, what data was returned, and how it influenced the final answer
AMcards in LlamaIndex
AMcards and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AMcards 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 AMcards in LlamaIndex
The AMcards 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 7 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
AMcards for LlamaIndex
Every tool call from LlamaIndex to the AMcards MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my AMcards Access Token?
Log in to your account, navigate to Settings > API, and generate a new Access Token for your integration.
Can I include a gift with the card?
Yes! If your chosen template ID includes a gift (like brownies), the system will automatically process the high-fidelity gifting workflow.
How do I check if a card was delivered?
Use the get_card_sending_history tool to retrieve the high-fidelity status log of all your previous card shipments.
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 AMcards 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