Contact is not chat is not message
A person identity, a conversation and an individual message are different provider objects. Nilyo documents those boundaries so the agent can obtain the correct ID instead of treating a display name as a send target.
The useful workflow is a chain
The agent can resolve a human reference, locate the existing chat, inspect recent messages, reason about the request and then reuse that exact chat for a supported action.
“Find my chat with Sarah and summarize the last ten messages.”
“Resolve John, read our latest conversation and draft a reply.”
“Inspect this group and list decisions with the people responsible.”
MCP keeps the user-facing experience simple
The user asks in normal language while MCP gives the model explicit operations and typed parameters underneath. Nilyo handles the provider semantics; the user does not need API documentation.
A better primitive for repeated messaging work
Explicit chat and message operations avoid repeated page rendering and visual selection for supported actions, while preserving structured results for later reasoning.
Common questions
What is a WhatsApp MCP server?
It is an MCP service exposing WhatsApp-related capabilities to compatible agents. Nilyo focuses on supported capabilities of the user’s connected account.
Do I need to run my own MCP server?
No. Nilyo is designed as a hosted connection layer for compatible agent clients.
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.