The other day I was listening to an interesting conversation between Yoko Li and David Soria Parra when Yoko came up with an example of her using MCP in a super creative way.
She mentioned that often while coding she would get past dinner and to answer her husband texts without exiting the IDE she would just ask Cursor to send him a message explaining why she was late without losing the flow-state she was in.
That really resonated with me and reminded me of a problem we frequently encountered at What About You. Specifically, when trying to review or debug a particular section, it wasn't uncommon for one of us to become completely lost for hours on end. Collaboration often yields solutions, yet interrupting deep focus to share the context of an issue with the team via chat feels disruptive and is often avoided.
Inspired by Yoko's approach, we integrated a WhatsApp MCP server with Cursor, enabling us to share context about coding challenges with the team directly from the IDE and request assistance without disrupting our workflow.
{
"mcpServers": {
"whatsapp": {
"url": "http://localhost:8088/mcp/"
}
}
}Reference: WhatsApp MCP by lharries
That was awesome, until one day I didn't explicitly tell Cursor the surname of the person I wanted to send the message to, and I accidentally shared the code I was stuck on with another friend who shared the same name as my Co-Founder.
So this time we decided to leverage our own creativity and our latest product, the Eunomia MCP Middleware, to protect from this risk.
from eunomia_mcp import create_eunomia_middleware
from main import mcp
middleware = [create_eunomia_middleware()]
app = mcp.http_app(middleware=middleware)
if __name__ == "__main__":
import uvicorn
uvicorn.run(app, host="0.0.0.0", port=8088)A rule was used to dynamically identify the recipient's number, ensuring Cursor's shared code context is directed exclusively to co-founders.
{
"version": "1.0",
"name": "mcp-whatsapp-policy",
"default_effect": "deny",
"rules": [
...
{
"name": "restrict-send-operations",
"effect": "allow",
"principal_conditions": [],
"resource_conditions": [
{
"path": "attributes.mcp_method",
"operator": "equals",
"value": "tools/call"
},
{
"path": "attributes.tool_name",
"operator": "in",
"value": ["send_message", "send_file", "send_audio_message"]
},
{
"path": "attributes.arguments.recipient",
"operator": "in",
"value": ["PHONE_NUMBER_1", "PHONE_NUMBER_2", "PHONE_NUMBER_3"]
}
],
"actions": ["execute"]
}
]
}Now we’re sure we can keep the flow-state without risking sending our codebase to random friends on WhatsApp, even if trying to do so explicitly, the Eunomia MCP Middleware actively block that.
Visit our GitHub for the full code example.
Or, if you’re interested in understanding more of how the Eunomia MCP Authorization Middleware works inside our enterprise-ready MCP governance system, feel free to reach out at: info@whataboutyou.ai. We’d be happy to talk!
Use MCP, but do it safely ;)