What is MCP?
MCP, the Model Context Protocol, is a standard way for AI assistants to use apps. Before MCP, every AI tool needed its own custom connection to every app. With MCP, an app builds one “socket”, and any assistant that speaks MCP can plug in.
Think of USB-C: one plug that fits phones, laptops and chargers from different brands. MCP is USB-C for AI.
1MCP (Model Context Protocol) is a standard plug that lets AI assistants use apps. Think of USB-C, but for AI.
2Arjun at Skyline Realty asks Claude in plain words: "When a MagicBricks lead comes in, add it to the CRM and WhatsApp the brochure."
3The assistant asks Auto Appy's MCP server what it can do. Auto Appy answers with its list of tools.
4The assistant uses the tools it needs, one at a time: create the workflow, then add the steps. You approve each one.
5Auto Appy does the work and replies. The assistant tells you the workflow is ready to test.
The four words you need
Section titled “The four words you need”| Word | Meaning | In Auto Appy |
|---|---|---|
| MCP client | The AI assistant you chat with. | Claude (web, desktop, mobile), Claude Code, and other assistants that support MCP |
| MCP server | The app’s socket that the assistant plugs into. | https://api.autoappy.com/mcp |
| Tools | The actions the server offers, each with a name and a description. | autoappy_create_workflow, autoappy_add_node, autoappy_run_workflow… |
| Permissions (scopes) | What you allow the assistant to do. | Read workflows · Build and edit · Run and do things for you |
What happens when you ask for something
Section titled “What happens when you ask for something”-
You ask in plain words. “When someone fills my website form, add them to my sheet and send a WhatsApp welcome.”
-
The assistant looks at the tools. It asks Auto Appy’s MCP server which tools exist and reads their descriptions, the way you’d scan a menu.
-
It plans and calls tools, one at a time. First create a workflow, then add a step, then configure the step. Each call is a small request with the details filled in.
-
You stay in control. Your assistant shows each tool call before it runs, and asks for your approval (you can allow some tools to run without asking).
-
Auto Appy does the work and replies. The assistant reads the reply, continues, and finally tells you what it built, with a link to open it.
Is it safe?
Section titled “Is it safe?”- You sign in on Auto Appy, not in the assistant. Connecting uses the same sign in and Allow method as Google (OAuth), so the assistant never sees your password.
- You choose the permissions on Auto Appy’s Allow access screen. Untick anything you don’t want.
- It can’t see your passwords or connected app accounts. It can pick a saved connection by name, but never reads the credentials.
- Workflow runs need approval by default, and every request is logged in Settings → MCP connections → Activity.
- You can disconnect at any time by revoking the connection in Auto Appy.
What you can do with Auto Appy’s MCP
Section titled “What you can do with Auto Appy’s MCP”Arjun at Skyline Realty uses it like this (see Skyline’s Lesson 5):
- “When a MagicBricks lead for Skyline Crest comes in, add it to the CRM and WhatsApp the brochure.”
- “Which of my workflows had failed runs this week? Show me the errors.”
- “In Book and remind site visits, remind buyers three hours before instead of two.”
- “Explain what Reply to every property enquiry does and leave a sticky note with the summary.”
- “Send a WhatsApp to +91 98670 45612 from our Sales number saying the sample flat is ready.” (asks first)