Build with Claude and ChatGPT

Auto Appy has an MCP server, so AI assistants can work in your account: list workflows, build and edit them, connect saved accounts, test steps and run workflows, with your approval. New to MCP? Read What is MCP? first; it takes five minutes.

In the course

• SRArjun builds a workflow by describing it to Claude. Lesson 5: Build by talking to Claude →

Animated explainerHow an AI assistant uses Auto Appy through MCP

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.

Connect your assistant

You’ll need: an Auto Appy account and an assistant that supports remote MCP servers. Auto Appy’s server address is:

https://api.autoappy.com/mcp

Claude (web, desktop, mobile)

1. In Claude, open Settings → Connectors (on some plans it’s under Customize) and choose Add custom connector.
2. Name it Auto Appy and paste the server address. Leave the advanced OAuth fields empty.
3. Click Add, then Connect. A window opens on autoappy.com. Sign in if asked.
4. On Connect Claude to Auto Appy, tick the permissions you want and click Allow access.
5. Start a new chat (assistants load a connector’s tools when a chat starts) and ask away.

Claude Code

1. In your terminal, add the server:

   claude mcp add --transport http autoappy https://api.autoappy.com/mcp

2. Start Claude Code and run /mcp. Choose autoappy and sign in; your browser opens Auto Appy’s Allow access page.

3. Start a new session to load the tools.

Other assistants

Any assistant that supports remote MCP over HTTP can connect.

• If it supports OAuth sign-in, give it the server address only. Auto Appy supports automatic client registration and PKCE, so it signs in like Claude does.
• If it only takes a token, create one in Auto Appy (Settings → MCP connections → Create connection) and send it as a header. A typical configuration file looks like this:

{
  "mcpServers": {
    "autoappy": {
      "url": "https://api.autoappy.com/mcp",
      "headers": { "Authorization": "Bearer aa_mcp_YOUR_TOKEN" }
    }
  }
}

Auto Appy is tested with Claude. ChatGPT, Cursor and others should work wherever they support remote MCP servers, but menus differ between apps.

The permissions you can give

The Allow access page lists three permissions. Untick any you don’t want.

Permission	Lets the assistant
Read workflows	List workflows, read their steps and notes, see run history and saved account names.
Build and edit workflows	Create workflows, add and configure steps, connect steps, attach a saved account by name, rename, write notes, and change Live/Paused/Draft.
Run and do things for you	Test a step, run a workflow, or run a one-off app action (such as sending one WhatsApp message) with a saved account.

It can’t see your passwords or the credentials inside your connections. Allowing access also turns on MCP access for your account.

Things to ask

• “List my workflows and show which ones failed this week.”
• “Build a workflow: when my Typeform is submitted, add a row to my ‘Leads’ sheet and WhatsApp the person our welcome template.”
• “Give me the webhook URL for ‘Welcome new leads’ and send it a test lead named Asha.”
• “In ‘Daily sales report’, change the email subject to include today’s date.”
• “Pause ‘Order sync to sheet’ until Monday.”
• “Send a WhatsApp to +91 98200 12345 from the Sales account saying the order has shipped.”

Approve with care

Your assistant shows each action before it runs. Read it: a step test or run is real (messages are really sent). Keep your assistant’s approval setting on (in Claude, tools default to Needs approval) for anything that sends messages or changes data, at least until you trust a workflow.

See and control access

Settings → MCP connections shows every connected assistant (Claude appears as an OAuth connection), the workflows you’ve exposed as tools, approvals waiting for you, and an activity log. Revoke a connection to disconnect that assistant immediately. Signing out of Auto Appy does not disconnect assistants.

autoappy.com/settings/mcpSample data

×

MCP server referenceTokens, limits and settings.

MCP tools referenceEvery tool, what it does, and the permission it needs.