emma_get_group — Emma MCP by usefulapi MCP Tool
emma_get_group
(emma get group) is one of 19 tools on the
Emma MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call emma_get_group from your client
- Claude Code Emma MCP by usefulapi emma_get_group run in your project directory
- Claude Desktop Emma MCP by usefulapi emma_get_group ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Emma MCP by usefulapi emma_get_group ~/.cursor/mcp.json
- VS Code Emma MCP by usefulapi emma_get_group .vscode/mcp.json
- Zed Emma MCP by usefulapi emma_get_group ~/.config/zed/settings.json
- Windsurf Emma MCP by usefulapi emma_get_group ~/.codeium/windsurf/mcp_config.json
- Cline Emma MCP by usefulapi emma_get_group ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Emma MCP by usefulapi emma_get_group ~/.gemini/settings.json
- Grok Emma MCP by usefulapi emma_get_group .mcp.json (in your project root)
- ChatGPT Emma MCP by usefulapi emma_get_group Settings → Connectors → Advanced → Developer mode
- Claude.ai Emma MCP by usefulapi emma_get_group Settings → Connectors → Add custom connector
- LangChain Emma MCP by usefulapi emma_get_group pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http emma https://emma.usefulapi.io/mcpOther tools on this server
- emma_list_groups
- emma_list_group_members
- emma_list_members
- emma_get_member
- emma_find_member_by_email
- emma_get_member_groups
- emma_get_member_mailings
- emma_list_fields
- emma_get_import
- emma_list_mailings
- emma_get_mailing
- emma_list_mailing_members
- emma_get_response_summary
- emma_get_mailing_response
- emma_list_mailing_links
- emma_list_mailing_activity
- emma_list_searches
- emma_get_search_members
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.