Use Maypop from your AI assistant

Maypop is an MCP server. Connect it to an AI assistant that supports remote MCP servers and the assistant can work in your Maypop account, with your permission: catch you up on what’s new, post in your groups, share apps, and build apps in Studio without you opening Maypop.

Server URL: https://api.app.maypop.ai/mcp

New to this?

MCP — the Model Context Protocol — is an open standard that lets an AI assistant use other services. You add Maypop to your assistant once, approve what it may do, and then just ask in plain language: “What’s new in my groups?” or “Build me a packing list app for our trip.”

What an assistant can do

• Catch you up — what needs your attention, unread groups, new notifications, invitations, recent changes to apps shared with you.
• Chat in groups — read and send messages, react, edit or delete your own messages, create groups, invite people, manage members.
• Share apps — share with people and groups, change who can open the link, set roles, allow remixing.
• Build in Studio — create a new app, edit or remix one, answer the agent’s questions as it builds, and publish when you ask.
• Find apps and creators on Explore.
• Connect integrations to your account and link them to apps.
• Check your plan and credits.

The full list is in the tool reference.

Connect

First, sign in at app.maypop.ai in your browser — the assistant’s sign-in uses that session.

Claude (web and desktop): open Settings → Connectors → Add custom connector, name it Maypop, and paste the server URL. Step by step: Build an app with Claude.

ChatGPT: add Maypop as a connector with the server URL. ChatGPT also shows your Maypop apps and live builds as cards in the conversation. Step by step: Build an app with ChatGPT.

Claude Code:

claude mcp add --transport http maypop https://api.app.maypop.ai/mcp

Then run /mcp in Claude Code to sign in.

Other clients: add a remote (streamable HTTP) MCP server with the URL above. Maypop signs you in with OAuth, so any client that supports OAuth for MCP servers works.

When you connect, Maypop shows a consent screen listing what the assistant may do. Approve it, and you’re done.

Permissions

The consent screen asks for access to:

Permission	Lets the assistant
Read your account	see your profile, groups, apps, and notifications
Groups	send messages, create and manage groups
Notifications	mark notifications read and archive them
Build apps	start Studio builds (uses your credits)
Publish apps	publish a finished build as a new version
Share apps	change who can open your apps
Integrations	connect services and link them to apps
Profile	change your username

Remove the connector in your assistant to revoke access. If Maypop adds a permission later, reconnect to grant it.

How builds work

A build runs in a Studio workspace in the background, exactly like one you started in Maypop — you can open it in Studio and watch. The assistant follows its progress, relays the agent’s questions to you, and tells you when it’s done.

• New apps are private, and while only you can open an app, finished builds are published automatically.
• Once an app has an audience, edits wait as a draft until you tell the assistant to publish — see Iterations and publishing.
• Builds cost credits at your Studio rates and count toward your plan’s Studios at a time. If all your slots are busy, the assistant can list your running Studios and stop one with your OK.

Reading, chatting and sharing are free.

Good to know

• The assistant acts as you, with your roles. It can’t do anything in Maypop you couldn’t do yourself.
• It reads app metadata — names, descriptions, who can open them — never the data stored inside apps or their source code.
• It never sees passwords, tokens or integration credentials; connecting a service always finishes in your browser.