Developer Tools
wraps.dev
Provides access to Wraps documentation and estimates monthly email infrastructure costs on Wraps and AWS.
ENDPOINT 1
https://wraps.dev/mcp
MCP server metadata
- Name
- wraps
- Version
- 1.0.0
Public Wraps documentation and pricing tools. Use search_docs to find how to do something with Wraps, get_doc to read a full page as markdown, and estimate_cost instead of doing Wraps + AWS SES cost arithmetic by hand. No authentication is required and no tool here can change anything. To operate a deployed email stack (send history, delivery events, domain status, suppressions, guarded sending), install the stdio server `npx -y @wraps.dev/mcp`, which uses the caller's own AWS credentials.
Known tools 4
search_docsSearch the full Wraps documentation (CLI, TypeScript SDKs, infrastructure, guides) and return the matching sections as markdown.
Inferred read-onlyestimate_costEstimate the real monthly cost of running email on Wraps + AWS: the flat Wraps platform fee for the plan, and the itemized AWS bill (SES, EventBridge, SQS, Lambda, DynamoDB, dedicated IP, WAF).
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.wraps]
url = "https://wraps.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"wraps": {
"type": "http",
"url": "https://wraps.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: wraps
Remote MCP URL: https://wraps.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"wraps": {
"url": "https://wraps.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"wraps": {
"type": "http",
"url": "https://wraps.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "wraps",
"transport": "streamable-http",
"url": "https://wraps.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.