Request access to the private preview of AppSheet MCP server to enable your apps as AI agent tools!

We talk a lot about the potential of AI, but we know that for businesses, “potential” isn’t enough. You need action. You need reliability. You need your AI to actually do work, not just talk about it. That’s why we built the AppSheet MCP Server, now in private preview.

The Missing Piece in the AI Toolkit

AI Agents are evolving rapidly. They can reason, plan, and chat, but they often struggle to take real action because they don’t have the right tools. An agent without a connection to your business data and logic is like a brilliant assistant with no computer—smart, but limited. And generic connectors to enterprise systems often fall short, failing to provide agents with enough business context or the necessary constraints on data access.

The AppSheet MCP Server changes that. It uses the Model Context Protocol (MCP) to transform your existing AppSheet apps into powerful agent tools, fully equipped with your business context and logic.

Why this matters for you

By enabling your AppSheet apps as tools, you empower AI Agents to:

  • Take Real Action: Agents can securely read data, update records, and trigger automations—all within the guardrails of your existing app.

  • Act with Confidence: Because the agent operates through your AppSheet app, it is bound by the same logic, security, and governance rules you’ve already built into your enterprise systems. No hallucinations on business rules—just deterministic workflows for consistent, reliable execution.

  • Hit the Ground Running: There’s no need to build new tools from scratch. Your existing apps are the tools.

Whether it’s an agent helping a frontline worker optimize a facility inspection route or a virtual assistant submitting a travel approval request, your apps provide the context and structure the AI needs to succeed.

How the magic works

The AppSheet MCP Server acts as a secure intermediary. When an AI agent connects:

  • Discovery: The server automatically converts your app’s structure (tables, data actions) into a machine-readable specification, allowing the agent to “learn” exactly what it can and cannot do.

  • Execution: When a user asks the agent to perform a task (e.g., “Approve the case study for Acme Corp”), the agent translates this into a structured call to the specific data action. The AppSheet MCP Server handles the secure execution against your app’s backend data.

Basic set up

  1. AppSheet Creator (In AppSheet): An AppSheet developer builds a great app (like a “Case Management” system) and enables the AppSheet app as an API, officially making it available to use as a powerful agent Tool.

  2. The Agent Builder (In Google ADK, Copilot, etc.): The person building the AI agent configures an MCP connection to your AppSheet app using its application API access key. This is like giving the AI agent a key to your app.

  3. The End User (In agent chat): Simply ask the agent to do something in natural language, such as: “What are the approved case studies for the finance industry?” or “I approve the case study for Cymbal Telecom.” The agent understands a business action is needed, knows what to use the app to perform, and tells the app to execute the task.

Who can join the Private Preview?

This Private Preview is currently available exclusively to AppSheet Enterprise Plus customers.

If you are an AppSheet Admin for an Enterprise Plus organization and are ready to equip your AI agents with the action-taking power of AppSheet, we invite you to request access!

Ready to add AppSheet to your AI utility belt? How to Get started

  1. Confirm Eligibility: This feature requires an AppSheet Enterprise Plus account. If you need to upgrade, please reach out to AppSheet Sales.

  2. Review Requirements: The agent platform you use (such as Google ADK or Microsoft Copilot) must support the Model Context Protocol (MCP). Ensure that your organization and team policies allow for API access, or create a custom policy for the necessary account IDs and apps.

  3. Request Access: Access requests must be submitted by an organizational or team admin. If you are a creator, please discuss this with your admin and ask them to request access on your behalf.

  4. Fill Out the Form: Request access using our preview request app (select the AppSheet MCP Server program). You will need your Workspace ID and Account ID.

Once your request is accepted, we’ll send you more detailed information and documentation on setting up your apps as agent tools!

We can’t wait to see how you combine the reasoning power of AI with the action-taking, governance-backed power of AppSheet.

What are your initial thoughts on the possibilities this opens up for your business? Drop your ideas and questions below!

-The Google AppSheet Team

9 Likes

This sounds all great and I would have loved to get excited but I almost don’t know how to anymore…..well done team I suppose and I hope it helps some random company out there.

What if the App itself doesn’t send emails well, is blocked or has unattended bugs, basic interface shortfalls, etc. When will these be attended to?

Can we expect an AI agent to respond here and perhaps fix backend bugs in the near future or will we have to wait patiently for responses from management or dev teams.

I do apologise if this sounds despondent, but with no movement on client facing features that make the app more appealing to build with, these AI things just feel like the reason other areas have suffered and lacked development.

6 Likes

I’m excited to see MCP Server support coming to AppSheet - this opens up great possibilities for AI agent integration.

That said, I also agree with @Denzil_Snyman ’s point. There are fundamental issues that need attention first. Hopefully both can move forward together.

5 Likes

Yes that’s true. This is something that AppSheet should improve.

4 Likes

You’re absolutely right.

3 Likes

Thank you, Google AppSheet Team, this is fantastic news that you are hard at work to advance our beloved platform into the future and to take full advantage of AI agents.

Dear esteemed Community of AppSheet supporters (who has helped me and my company many times before), I can understand the frustration about Google not addressing some old complaints about the platform or not moving its new features quickly enough. But we shouldn’t miss that some nay-sayers have predicted that no-code platforms would be replaced entirely by vibe-coding ones. So it is very re-assuring to see that Google seems to think that AI and AI agents are here to support the AppSheet platform rather than replace it. If Google didn’t work on that now, chances are AppSheet would soon become obsolete!

3 Likes

@Gonzague_Issen1

Like you, I’m genuinely excited about this update!
I believe vibe-coding cannot handle the kind of complex data structures and routine business operations that AppSheet excels at.

This MCP Server integration will strengthen AppSheet’s value proposition, which is why I have high expectations for it.

1 Like

@goannsplain

I personally agree with others who posted here, i.e. the AppSheet should address the ongoing & pending issues (fix bugs) first of all, while we also welcome the new features to be topped up to this platform.

Before Google time, the team (AppSheet) always hosted the quick webiner to introduce the new features and address Q&A from the attendees basis real-time. Why your team abandoned the effort to host such a useful webiner? If I m correct, the meaningful AppSheet Event never hosted for a long time.

When your team is to introduce such a brand new features, the best way to approach to the mass audience is to quickly host the online webiner (Office Hours in the old fashioned manner it is called.)

Is this because Google Meets is not providing a capability to host such a webiner against the large (unlimited numbers) of the attendees/audience? Or your team is just shy to show up in such a place?

I really hope the AppSheet Office Hours (event) will be back again.

6 Likes

Stay tuned! We are in the process of relaunching Office Hours very soon! As before, we will be providing feature updates along with demos while providing a way to ask questions during the session. We’ll post more info on this soon!

4 Likes

@cschalk_ws

That’s great news! I’m looking forward to seeing a demo of the MCP Server in action during the Office Hours. It would be really helpful to understand what’s possible with this integration.

3 Likes

I m not ready to post ”Like” to your post, as the past office hours (after google acquisition) is not really addressing to the point what we want, but just focusing on What Google want to say. Thats why the mates in the community place lost the interest to see and join the webiners. What I want to address and stress the point is “AppSheet is No - Code tool”, by nature.

As far as we see the latest development of the AppSheet, Google is seemingly guide the platform to LOW CODE or CODING platform. Is that the official Google Strategy to guide the AppSheet (which is No-Code Platform for citizen developpers)?

For us, it is obvious that the Google started to depart from the original target to develop AppSheet as no-code platform to be friendly to the citizen developper, but you guys are guiding the platform to more friendly to the developers in the larger enterprise entities…

If this is not a story, I hope to see you guys explain why this is not true story through the upcoming office hours. You guys already lost the trust from the community, so the task is how to regain the trust from the community member. The office hours session should be the only the place to get the trust back from the community member. (None of the bugs are fixed, the intended new feature never delivered. etc etc. It is good opportunity for you to explain to the users and community members to explain why the Google operated AppSheet is not meeting with the users requirement and basic demands)

3 Likes

We simply watch you guys.

1 Like