Amcards
AMCards enables users to create personalized greeting cards, automate mailing campaigns, strengthen customer relationships using a convenient online platform for individualized connections
Verdict
Common use cases
- Check card inventory before a holiday campaign
- Find donor contact details during outreach planning
- Filter contacts by last name for segmented mailings
- Verify card designs available for upcoming events
- Pull contact lists into campaign briefs
Integration
- Vendor
- Amcards
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
amcards
Tools
- Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, an
- Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields su
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations section. 2. Click 'Add Integration' and select Amcards from the list. 3. You'll be prompted to enter an API key—log into your Amcards account, go to Settings or API Access, and generate a new key with read permissions for cards and contacts. 4. Paste the key into Switchy and click 'Connect'. 5. To test, open any Space and type '@Amcards get my contact list' or '@Amcards show all cards'—if the MCP responds with data, the connection is live. 6. From now on, @mention Amcards in any message to invoke its tools; the AI will route your request to the appropriate endpoint and return results inline.
What teammates see: by default, memories from Amcards are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Cards
@Amcards show me all the cards in my account. I want to see what designs we have available for our Q2 donor thank-you campaign.Open in a Space →
Find Contact by Name
@Amcards find contacts with the last name 'Martinez'. I need their email addresses for the event invitation list.Open in a Space →
Pull Recent Contacts
@Amcards get the last 20 contacts added to my account. I want to confirm the import from our CRM went through correctly.Open in a Space →
Filter by Email Domain
@Amcards retrieve all contacts with email addresses ending in '@nonprofit.org'. We're segmenting our outreach by sector.Open in a Space →
Audit Contact Count
@Amcards how many contacts do I have in total? Also show me a sample of 10 so I can check data quality.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Amcards show me all the greeting cards I've sent in the last 30 days, grouped by recipient
Based on your Amcards account, you've sent 12 cards in the last 30 days. Here's the breakdown: 4 cards to Sarah Johnson (birthday card on Jan 5, thank-you card on Jan 12, two sympathy cards on Jan 18 and Jan 22), 3 cards to the Martinez family (holiday card on Jan 3, wedding card on Jan 15, congratulations card on Jan 20), 2 cards to David Chen (get-well card on Jan 8, birthday card on Jan 25), and single cards to three other recipients. All cards show 'delivered' status except the Jan 25 card which is still in transit.
This example uses the Get Cards tool to retrieve historical send data. The MCP returns card metadata (recipient, type, date, status) but not the card content itself. Useful for tracking your sending history, but grouping and date filtering depend on what fields Amcards exposes in their API response—some accounts may have limited historical visibility.
@Amcards find all contacts with the last name 'Williams' and show me their mailing addresses
I found 3 contacts with the last name 'Williams' in your Amcards account: Jennifer Williams at 742 Maple Street, Portland OR 97214; Robert Williams at 88 Lakeview Drive, Austin TX 78701; and Susan Williams at 1523 Oak Avenue, Denver CO 80202. All three contacts have verified mailing addresses on file. Jennifer and Robert were added to your account in 2023, while Susan was added in early 2024.
This demonstrates the Get Contacts tool with a last name filter. The tool supports pagination (limit/skip parameters) and multiple filter types (first name, last name, email). Contact data quality depends on what you've entered into Amcards—incomplete records will return partial information. No write capability shown here; this is read-only contact retrieval.
@Amcards pull my complete contact list and draft a plan for sending holiday cards to everyone I haven't contacted in over 6 months
Your Amcards account contains 47 contacts. Cross-referencing with your card-sending history, 19 contacts haven't received a card from you in the last 6 months: the Anderson family, Beth Cooper, Carlos Diaz, and 16 others. Suggested approach: send a general holiday card to the 12 contacts you haven't written in 6-9 months (they'll appreciate the reconnection), and consider more personalized messages for the 7 contacts with no card history beyond 12 months—these relationships may need a warmer touch than a standard greeting. I can help you draft personalized messages if you share context about any of these contacts.
This synthesis example combines both tools (Get Contacts + Get Cards) with AI reasoning to identify relationship gaps. The MCP provides raw data; the AI does the analysis and planning. This workflow is read-only—Amcards MCP doesn't currently support sending cards directly, so execution would happen outside Switchy. Most valuable for strategic planning rather than automated sending.
Use-case deep-dives
When Amcards MCP makes sense for seasonal client outreach
A 3-person consulting shop sends physical cards to 80 clients every December. They keep contact details in a CRM but want AI to draft personalized messages based on project history stored in Notion. The Amcards MCP pulls the contact list and card inventory, then an agent cross-references Notion to write custom notes for each card. This works if your contact list is under 200 and you send cards once or twice a year. Beyond that scale, you're better off exporting a CSV and using Amcards' web dashboard directly. The MCP's value is the AI personalization step, not bulk card management. If you need this workflow more than quarterly, connect Amcards to your workspace and let an agent handle the entire send cycle in one prompt.
Using Amcards MCP to close the referral loop with physical mail
A 6-person sales team tracks referrals in HubSpot and wants to send handwritten-style thank-you cards within 48 hours of a closed deal. An agent monitors the CRM via another MCP, identifies new referrals, then uses Amcards to queue a card with a custom message. The two-tool setup (Get Contacts, Get Cards) is enough to check inventory and trigger sends without leaving the AI workspace. This breaks down if you're sending more than 20 cards a week—Amcards' API isn't built for high-volume transactional mail, and you'll hit rate limits or need manual card restocking. For low-frequency, high-touch gestures where the AI writes the message based on deal context, the MCP is a clean fit. Add it to Switchy if physical mail is part of your sales playbook but not your primary channel.
When Amcards MCP is overkill for post-event outreach
A 10-person marketing team runs quarterly trade shows and wants to send cards to booth visitors. They have a spreadsheet of 300 contacts per event and plan to use AI to personalize messages based on conversation notes. The Amcards MCP can retrieve contacts and card stock, but uploading 300 new contacts and managing card inventory through the API is slower than using Amcards' web interface directly. The MCP shines when contact lists are already in Amcards and you need AI to draft messages on the fly, not when you're doing bulk imports. If your event follow-up is a repeating playbook with stable contact lists under 50, the MCP works. Otherwise, handle the upload manually and use Switchy for the message-writing step only. Skip this integration if your primary use case is one-time bulk sends after events.
Frequently asked
What does the Amcards MCP do in Switchy?
It lets your AI agents retrieve greeting cards and contact lists from your Amcards account. The MCP exposes two tools: one pulls all cards you've created, the other fetches contacts with optional filters like name or email. Useful if you're automating card campaigns or syncing contact data into workflows without manually exporting CSVs.
Do I need an Amcards API key to connect this MCP?
Yes. The MCP uses API key authentication, so you'll need to generate one from your Amcards account settings before connecting it in Switchy. No OAuth dance—just paste the key once and you're done. Make sure the key has read access to cards and contacts.
Can the Amcards MCP send cards or create new contacts?
No. The two tools are read-only: they retrieve existing cards and contacts. If you need to send cards or add contacts, you'll have to do that directly in Amcards or use their full API outside of this MCP. This integration is for pulling data into Switchy, not pushing changes back.
Why use this MCP instead of exporting Amcards data manually?
The MCP lets your AI agents query Amcards on demand—no manual exports, no stale spreadsheets. If you're building workflows that need up-to-date contact lists or card inventory, the MCP keeps that data live. For one-off exports, the Amcards dashboard is faster.
Who on my team should connect the Amcards MCP?
Whoever owns your Amcards account and can generate an API key. Since the MCP only reads data, you don't need admin privileges—just enough access to view cards and contacts. Once connected, any Switchy workspace member can use the tools in their prompts.