Bring Direct Mail
to Cursor
Learn how to connect AMcards to Cursor 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 Cursor?
Cursor's Agent mode turns AMcards into an in-editor superpower. Ask Cursor to generate code using live data from AMcards and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
AMcards in Cursor
AMcards and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AMcards to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.