mcp-whatsms
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_FILE | No | Log file path (optional) | |
| MCP_MODE | No | MCP mode flag | true |
| NODE_ENV | No | Node environment | production |
| CACHE_TTL | No | Cache TTL in milliseconds | 300000 |
| CLIENT_ID | No | Client ID | default |
| LOG_LEVEL | No | Log level | info |
| ENABLE_CACHE | No | Enable caching | true |
| REQUIRE_HTTPS | No | Require HTTPS | true |
| CACHE_STRATEGY | No | Cache strategy | lru |
| REQUEST_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| WHATSMS_BASE_URL | No | Base URL for WhatSMS API | https://whatsms.descomplicar.pt/api |
| WHATSMS_API_SECRET | Yes | Your WhatSMS API token (obrigatório) | |
| MCP_DEPLOYMENT_MODE | No | Deployment mode: local or remote | local |
| RATE_LIMIT_REQUESTS | No | Rate limit requests per window | 1000 |
| MAX_CONCURRENT_OPERATIONS | No | Maximum concurrent operations | 10 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Descomplicar-Marketing-e-Tecnologia/mcp-whatsms'
If you have feedback or need assistance with the MCP directory API, please join our Discord server