
What This Article Is About I’d like to tell you about a few of the MCP servers and agent...
I’d like to tell you about a few of the MCP servers and agent skills that I use most often. I’ll tell you what they do, how I use them, and how to install them.
These make up much of my agentic environment — or agent harness — that ensures that my agentic tools do what I need them to do, in a reliable and repeatable way. Since I mostly work within the Google ecosystem, it will be no surprise to the majority of my readers that most of these (but not all) are Google-centric.
This first part will cover the MCP servers, and I’ll share my favourite agent skills in the second part.
Check out this video, where I explain MCP and skills, how they work, and how they differ.
{% youtube tFUjc1Jx5_0 %}
I talk about the use cases where skills are better than MCP servers and vice versa, and I talk about the scenarios where you might want to use them together. (This is the talk I did for the Google Build with AI roadshow.)
MCP servers and skills are crucial for grounding our agents and ensuring they do what we want them to do, in a repeatable way. They make up two core components of the agent harness. If you’re new to this term, then here’s the thing to know: “If you’re not the model, you’re the harness.”
When you’re using an agent to achieve a goal, that agent calls at least one model. But every agent also needs at least some of the following: prompts, context management, state management, tools, data for grounding, orchestration and an execution environment. These are the things that make up the harness.
So, where exactly do MCP and skills fit into this scaffolding?
Assembling a tailored set of skills and MCP servers dials your agentic development environment straight up to 11. Suddenly, your agentic editor isn’t just suggesting code; it’s actively provisioning cloud services, auditing your SEO, checking your security protocols, and maintaining your documentation.
These days I’m doing all my development work in either Google Antigravity CLI or Antigravity IDE. (By the way, Google Antigravity is also known as Agy. So I’ll be using this nickname frequently in this article.) If you want a general overview of how to set up skills and MCP servers in Agy, check out my article:
Configuring MCP Servers and Skills for Antigravity CLI and IDE
Okay, that’s it for the preamble. Let’s get into the list!
This MCP server acts as the bridge between your agent and your GitHub repositories. It exposes a full set of tools for managing pull requests, creating issues, committing changes, and pushing them.
It’s also particularly useful if you manage to get yourself in a git pickle! I have a bit of imposter syndrome when it comes to remembering certain git commands. Is it just me?
For example, you might say to Antigravity: “Commit all the changes in my workspace in a new branch, and push.”
In response, Agy is going to pick an appropriate name for your branch, create it, stage and commit your changes with an appropriate commit message, and push to your remote repo.
Here’s a really simple demo, where I’ve asked Agy:
“Look up all my public github repos. Return them to me directly in this chat as a markdown table, including one line description, primary technologies used, and number of stars. List them in descending stars order.”
{% youtube yIrgfGh-hTo %}
To install it, just add this block to your MCP configuration. (In Antigravity, it will be ~/.gemini/config/mcp_config.json.) The MCP server is remote, so you don’t need to install anything locally. You will need a GitHub access token, to allow your agent to authenticate to GitHub.
"mcpServers": {
// other MCP servers
"remote-github": {
"serverUrl": "https://api.githubcopilot.com/mcp/",
"headers": {
"Authorization": "Bearer YOUR_GITHUB_PERSONAL_ACCESS_TOKEN",
"Content-Type": "application/json"
}
}
}
This is a remote server that gives your agent the power to perform semantic search of the official Google developer documentation corpus. It covers everything from Android, Go, Flutter, Firebase, ADK, and Gemini APIs, to Google Cloud and TensorFlow.
With this MCP server, your agent knows:
In short… If you do any work with Google services, you want this MCP to be running!
Without this MCP, you’ll often get outdated information about Google services and APIs, or code generated with hallucinations that don’t actually work.
Let’s give it a try…
“Using Google Developer Knowledge MCP, tell me about GKE in-place pod resize”
Our agent quickly comes back with an accurate and up-to-date response:

Note: it’s not really necessary to tell Agy which MCP server to use to do a task. But sometimes, if you have many servers with complementary capabilities, it can save your agent a bit of confusion if you tell it how you want it to fetch your information.
To configure this, you’ll need to authenticate (which can be with ADC or an API key), and then add an entry like this to your MCP config:
"mcpServers": {
// other MCP servers
"google-developer-knowledge": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://developerknowledge.googleapis.com/mcp",
"--header",
"X-Goog-Api-Key: YOUR_API_KEY"
]
}
}
I love this one! It’s basically a wrapper around the free command line tool, ffmpeg. With it you can manipulate video, images and audio with natural language commands. With prompts like…
Let’s do a quick demo… I’ve put an episode of an old 1980s Dungeons and Dragons cartoon into the workspace directory. My goal is to extract just the first 10 seconds of the episode and save it as a separate video file. The original video has quite a long title, but I don’t have to be specific with Agy:
“Take the first 10 seconds of the dungeons and dragons video, and save it as a new video.”
{% youtube mh_XKxrJleg %}
The clip generation was super fast. Agy, via the MCP server, ran this command, but we don’t need to know or care!
ffmpeg -y -i "dungeons & dragons -01- the night of no tomorrow (mummra1983).avi" \
-ss 00:00:00 -t 10 -c:v libx264 \
-c:a aac media-output/dungeons_and_dragons_10s.mp4
Insanely cool, right?
Unlike the previous MCP servers I’ve described, this one requires that we set up some prerequisites...
ffmpeg installed locally.Finally, add your MCP configuration as usual:
"mcpServers": {
// other MCP servers
"avtool": {
"command": "mcp-avtool-go",
"env": {
"MCP_SERVER_REQUEST_TIMEOUT": "55000",
"PROJECT_ID": "your-google-project",
"GENMEDIA_BUCKET": "your-gcs-bucket",
"LOCATION": "europe-west1"
}
}
}
Everyone knows I love NotebookLM! A quick recap, if you don’t know what it is…
NotebookLM is a personalised AI research assistant built on top of Google’s multimodal Gemini models. It’s designed to help you understand, synthesise, and present complex information that’s scattered across all sorts of different formats. Some key tenets:
I’ve written a dedicated blog about using MCP to integrate with NotebookLM previously:
Integrate NotebookLM with Gemini CLI, Google Antigravity or Other Agents with MCP
That blog has a number of use cases demonstrated, so I won’t repeat them here.
This is another MCP server that runs locally, so there’s a few things you need to setup:
uv installed. (Like many locally running MCP servers require.)notebooklm-mcp-cli: uv tool install notebook-mcp-cliNow you can go ahead and add your MCP server entry:
"mcpServers": {
// other MCP servers
"notebooklm-mcp": {
"command": "uvx",
"args": [
"--from",
"notebooklm-mcp-cli",
"--with",
"fakeredis<2.20.0",
"notebooklm-mcp"
]
}
}
This is very useful when developing using Google Agent Development Kit (ADK). This particular MCP Server provides your agent with specific grounding documentation about ADK itself. These days, this one might be a little redundant, given that the Google Developer Knowledge MCP includes ADK documentation in its corpus. But I still find that having this MCP installed provides very targeted information when I’m building agents with ADK.
It works by running a local mcpdoc MCP server on your machine and pointing that server to the official ADK documentation. If you want to know a bit more about how this works, you might find this interesting:
Give Your AI Agents Deep Understanding With LLMS.txt
You do need to have uv pre-installed, but otherwise, the only configuration you need is this:
"mcpServers": {
// other MCP servers
"adk-docs-mcp": {
"command": "uvx",
"args": [
"--from",
"mcpdoc",
"mcpdoc",
"--urls",
"AgentDevelopmentKit:https://adk.dev/llms.txt",
"--transport",
"stdio"
]
}
}
Google Stitch is very cool! It’s all about designing the UI.
This is its tagline:

You describe an idea in natural language, and Stitch creates the wireframe and the interactive mockups of what your application will look like. You might give Stitch a prompt like:
“A landing page for a movie club application. Minimalist dark-mode aesthetic with neon purple and green accents. Top bar navigation, with main window widgets for calendar and movie management.”
Let’s give that prompt a go!
Initially, as Stitch is building the design, we see this:

And a minute later, we have this:

How cool is that?
From here, you can annotate, modify and iterate.
As you go, Stitch maintains your UI design in a standardised DESIGN.md document that is both human and agent-readable. And you can export everything created by Stitch — the DESIGN.md, the HTML, and the images — in various formats, including Figma, as a zip file, or directly into AI Studio.
If I download the zip, it looks like this:

Now I can add these files to my development project. If I’m vibing the frontend, I could drop in these files and then ask Agy to (say) create a React web application that matches these files.
But with the Stitch MCP server, it’s even easier! It essentially opens a two-way conversation about your agentic development environment (like the Agy IDE) and Stitch. So now you could say, from Agy:
“Using Stitch MCP, create a landing page for a movie club application. Minimalist dark-mode aesthetic with neon purple and green accents. Top bar navigation, with main window widgets for calendar and movie management. Let me give it the once over before we build the actual web UI application.”
This is what we then see in Agy:

Then, as with any MCP server, Agy asks if it has permission to execute the required tool:

Once Agy is finished, we see this:

Of course, we can always go into the Stitch UI and take a look at what was created.
To conclude, with the Stitch MCP server we can:
And all without ever leaving our IDE’s chat interface. Also, we never have to export any files from Stitch and dump them into our workspace. We have true two-way conversation between our Agy agent and Stitch.
Stitch uses a remote MCP server, so we just need to download an API key from Stitch, and then add this to our MCP config:
"mcpServers": {
// other MCP servers
"StitchMCP": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://stitch.googleapis.com/mcp",
"--header",
"X-Goog-Api-Key: YOUR_API_KEY"
]
}
}
These have been around for a little while now, but Google made them generally available (GA) in April 2026.
Basically, they are a set of remote MCP servers, hosted and fully-managed by Google. They align to many of Google’s services and products, like BigQuery, Firestore, Cloud SQL, Cloud Storage, Cloud Run, GKE, Maps, Cloud Monitoring, Cloud Logging, and so on. They allow us to have natural language conversations with these Google services.
And because they are fully-managed, we don’t have to install anything and we never have to maintain them.
Typically, I don’t have these enabled all the time. But if I’m working with a particular Google Cloud service for a given project, I’ll typically configure the required MCP server for as long as I need it.
We do need to do a couple of things in Google Cloud first. This includes:
bigquery.googleapis.comroles/mcp.toolUser roleThen we can add our MCP configuration:
"mcpServers": {
// other MCP servers
"FirestoreMCP": {
"serverUrl": "https://firestore.googleapis.com/mcp",
"authProviderType": "google_credentials",
"oauth": {
"scopes": [
"https://www.googleapis.com/auth/cloud-platform"
]
},
"headers": {
"X-Goog-User-Project": "YOUR_PROJECT_ID"
}
}
}
If you want to know more about these Google MCP servers, check out Romin Irani’s Google MCP Server Tutorial Series. He goes into a lot of depth, and provides a bunch of use cases.
This empowers our agent to know how to use the Google gcloud CLI. So we can issue natural language prompts like:
This saves a lot of time in trying to determine the exact gcloud syntax to do a specific thing.
This is a remote MCP server, and setting it up is as simple as adding this config:
"mcpServers": {
// other MCP servers
"gcloud": {
"command": "npx",
"args": [
"-y",
"@google-cloud/gcloud-mcp"
]
},
}
It operates with the authority of your ADC credentials.
Having a robust agent harness transforms the effectiveness of your agent. Having a good set of MCP servers is part of this harness. Give these a try in your own development environment, whether it’s Antigravity or other. And let me know: which are your favourites? What other MCP servers would you recommend?
Stay tuned. The Agent Skills rundown will arrive soon.
Skills and MCP Servers Explained (Build with AI, Prishtina)
{% youtube tFUjc1Jx5_0 %}
Configuring MCP Servers and Skills for Antigravity CLI and IDE
Integrate NotebookLM with Gemini CLI, Google Antigravity or Other Agents with MCP
aiMost of us have seen a coding agent fail to complete a task we know it can do. We just don't...
googlecloudWhen building Generative AI applications, developers often encounter a massive bottleneck: sequential...
discussI’ve been thinking about sharing some electronic circuit posts on Dev.to — small circuits, DIY...
agentsWhat nobody tells you about exporting your multi-agent prototype to a local workspace. Every...
agenticarchitectAutonomous agents are genuinely good at answering messy business questions. Give one an LLM and a set...
aiPR volume went up, ticket quality didn't, and the gap got filled with LLMs on both sides of the review: bots reviewing, bots replying, bots occasionally arguing with bots about priorities that only existed in a teammate's head. Our CEO named the actual problem, and it's bigger than code review.
Workflows from the Neura Market marketplace related to this Stable Diffusion resource