Compare · Email
Resend vs Plunk MCP Server
Resend exposes 136 tools and adds about 47,896 tokens to every model turn. Plunk exposes 42 tools and adds about 14,491. Resend costs 3.3× as much context. Measured by connecting to each server and counting its tool list, not from the README.
 Resendresend |  Plunkuseplunk | |
|---|---|---|
| Context tax | ~47,896 tok/turn | ~14,491 tok/turn(leaner) |
| Tools | 136 | 42 |
| Cost per 1,000 turns (Claude Sonnet 5.5, uncached) | $95.79 | $28.98 |
| Security score | 97/100 | 97/100 |
| Cold start | 947 ms | 255 ms |
| Runs | Local (stdio) | Local (stdio) |
| Needs keys | None declared | None declared |
| Freshness | Active | Active |
| GitHub stars | 576 | 5.5k |
| License | MIT | AGPL-3.0 |
| Official MCP registry | No | No |
Install in Claude Code
Tools
By name, from each server's live tool list. The same name can still behave differently.
Only in Resend · 136
- get-tiptap-json-content
- connect-to-editor
- disconnect-from-editor
- create-api-key
- list-api-keys
- update-api-key
- remove-api-key
- create-automation
- update-automation
- get-automation
- duplicate-automation
- remove-automation
- get-automation-runs
- create-broadcast
- send-broadcast
- list-broadcasts
- get-broadcast
- cancel-broadcast
- duplicate-broadcast
- remove-broadcast
- compose-broadcast
- update-broadcast
- list-broadcast-clicked-links
- list-broadcast-recipients
- create-contact-import
- get-contact-import
- list-contact-imports
- create-contact-property
- list-contact-properties
- get-contact-property
- update-contact-property
- remove-contact-property
- create-contact
- list-contacts
- get-contact
- update-contact
- remove-contact
- add-contact-to-segment
- remove-contact-from-segment
- list-contact-segments
- +96 more
In both · 0
- none
Only in Plunk · 42
- plunk_list_contacts
- plunk_get_contact
- plunk_unsubscribe_contact
- plunk_subscribe_contact
- plunk_create_contact
- plunk_update_contact
- plunk_delete_contact
- plunk_send_email
- plunk_verify_email
- plunk_track_event
- plunk_list_templates
- plunk_create_template
- plunk_list_campaigns
- plunk_create_campaign
- plunk_send_campaign
- plunk_get_campaign
- plunk_test_campaign
- plunk_cancel_campaign
- plunk_get_campaign_stats
- plunk_list_segments
- plunk_create_segment
- plunk_list_domains
- plunk_check_domain
- plunk_list_workflows
- plunk_get_workflow
- plunk_check_workflow
- plunk_list_workflow_fields
- plunk_list_workflow_executions
- plunk_get_workflow_execution
- plunk_create_workflow
- plunk_update_workflow
- plunk_duplicate_workflow
- plunk_delete_workflow
- plunk_add_workflow_step
- plunk_add_workflow_steps
- plunk_update_workflow_step
- plunk_delete_workflow_step
- plunk_connect_workflow_steps
- plunk_disconnect_workflow_steps
- plunk_set_workflow_enabled
- +2 more
Questions
- Which uses fewer tokens, Resend or Plunk?
- Plunk: its tool definitions take about 14,491 tokens per turn against 47,896 for Resend (3.3× more). Tool definitions are resent on every model turn.
- Do Resend and Plunk have the same tools?
- No tool names overlap: Resend has 136 tools and Plunk has 42.
- Are Resend and Plunk hosted or local?
- Resend: local (stdio). Plunk: local (stdio).
Token counts use the o200k tokenizer on each server's tool definitions as an agent receives them; clients that load tools lazily pay less. Prices are Claude Sonnet 5.5 input at $2/MTok. Want to check one yourself? Run npx mcpskillhub test <package> — how it works.