Moroccan Custom Sender ID Regulations — EnvoiSMS MCP Resource
Moroccan Custom Sender ID Regulations
is one of 3 resources on the
EnvoiSMS
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Moroccan Custom Sender ID Regulations from your client
- Claude Code EnvoiSMS Resource/Moroccan Custom Sender ID Regulations run in your project directory
- Claude Desktop EnvoiSMS Resource/Moroccan Custom Sender ID Regulations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EnvoiSMS Resource/Moroccan Custom Sender ID Regulations ~/.cursor/mcp.json
- VS Code EnvoiSMS Resource/Moroccan Custom Sender ID Regulations .vscode/mcp.json
- Zed EnvoiSMS Resource/Moroccan Custom Sender ID Regulations ~/.config/zed/settings.json
- Windsurf EnvoiSMS Resource/Moroccan Custom Sender ID Regulations ~/.codeium/windsurf/mcp_config.json
- Cline EnvoiSMS Resource/Moroccan Custom Sender ID Regulations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EnvoiSMS Resource/Moroccan Custom Sender ID Regulations ~/.gemini/settings.json
- Grok EnvoiSMS Resource/Moroccan Custom Sender ID Regulations .mcp.json (in your project root)
- ChatGPT EnvoiSMS Resource/Moroccan Custom Sender ID Regulations Settings → Connectors → Advanced → Developer mode
- Claude.ai EnvoiSMS Resource/Moroccan Custom Sender ID Regulations Settings → Connectors → Add custom connector
- LangChain EnvoiSMS Resource/Moroccan Custom Sender ID Regulations pip install langchain-mcp-adapters
Other resources on this server
EnvoiSMS also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.