envelope_send_invite — Tamgara MCP Tool
envelope_send_invite
(envelope send invite) is one of 33 tools on the
Tamgara
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call envelope_send_invite from your client
- Claude Code Tamgara envelope_send_invite run in your project directory
- Claude Desktop Tamgara envelope_send_invite ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tamgara envelope_send_invite ~/.cursor/mcp.json
- VS Code Tamgara envelope_send_invite .vscode/mcp.json
- Zed Tamgara envelope_send_invite ~/.config/zed/settings.json
- Windsurf Tamgara envelope_send_invite ~/.codeium/windsurf/mcp_config.json
- Cline Tamgara envelope_send_invite ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tamgara envelope_send_invite ~/.gemini/settings.json
- Grok Tamgara envelope_send_invite .mcp.json (in your project root)
- ChatGPT Tamgara envelope_send_invite Settings → Connectors → Advanced → Developer mode
- Claude.ai Tamgara envelope_send_invite Settings → Connectors → Add custom connector
- LangChain Tamgara envelope_send_invite pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tamgara https://api.tamgara.com/api/mcp
Other tools on this server
- info
- list_languages
- list_locales
- list_categories
- search_templates
- get_template
- fill_template
- list_providers
- get_provider
- fax_countries
- fax_ping
- fax_quote
- fax_create_checkout
- fax_confirm
- fax_status
- brief_ping
- brief_quote
- brief_create_checkout
- brief_confirm
- brief_status
- brief_cancel
- envelope_create
- envelope_status
- envelope_void
- envelope_upload_final
- inspect_pdf
- fill_pdf
- pdf_from_images
- add_cover_page
- apply_scan_answers
- account_balance
- account_topup
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.