Next.js MCP for SEO
Connect SEOmatic's MCP server and your AI agent finds what is holding your Next.js pages built from your database back in Google, stages the fix through the Postgres database your routes read, and waits for your approval. Then it checks whether the change worked.
- Your real Search Console data
- Fixes staged in Next.js
- Your approval first, by default

Last Checked
October 2026
Endpoint
https://app.seomatic.ai/api/mcp
Full Docs
Every tool, parameter and cost: SEOmatic MCP docs.
How SEOmatic's MCP Works on Next.js
The Short Answer
Vercel's next-devtools-mcp connects coding agents to a running Next.js 16 dev server for errors, routes and docs. It is a development tool, not a content tool. SEOmatic's MCP server (https://app.seomatic.ai/api/mcp) does a different job on Next.js: SEO. It reads your Google Search Console data, finds the Next.js pages built from your database that are losing clicks or not indexed, and stages the fix through the Postgres database your routes read. By default nothing goes live until you approve it, every change can be rolled back, and each one is measured afterwards and marked verified, ineffective or regressed. You can run both servers in the same agent.
Which Next.js MCP Do You Need?
| SEOmatic MCP | next-devtools-mcp (Vercel) | |
|---|---|---|
| What it is for | SEO: find what costs clicks, fix it, measure it | Debug a Next.js app in development |
| Your Search Console data | Yes, free with no limit | No |
| Picks what to change from search data | Yes | No |
| Rollback | Yes, with a check for edits made since | Not built in |
| Measures whether a change worked | Yes | No |
What SEOmatic Can Change on Next.js
Your app owns the rendering, so agents stay on their side of the line: they research, write and publish rows, and your code decides what happens to them.
- Writes The Pages: Full articles and programmatic pages from research to finished draft, published as rows your routes already render.
- Nothing Applies Without You: The agent arrives switched off and starts in approval mode. It acts on its own only where you allow it.
- Update, Never Duplicate: Agents remember the row they wrote and update it, so republishing does not leave you cleaning up copies.
- Column Field Mapping: Map your table's columns once to title, content, slug, excerpt, image and meta. Common names are matched for you.
- Publish Verification: After publishing, SEOmatic fetches the live URL and tells you if your route is still serving the old version.
- Draft And Published States: Rows carry their status, so your app can hold work back until you are ready for it to appear.
Every field, limit and safeguard is on the Next.js integration page.
Connect Next.js and Your Agent
1. Connect Next.js to SEOmatic. In SEOmatic, go to Connections and select Next.js. Paste your Postgres connection string. SEOmatic validates it and confirms the database name.
2. Connect SEOmatic to your agent. Add https://app.seomatic.ai/api/mcp as a remote MCP server (Streamable HTTP) in your agent, then sign in to SEOmatic in the browser. Sign-in is OAuth 2.1 with PKCE and dynamic client registration, so there is no key to paste. Scripts and headless agents can send a workspace API key as a Bearer token instead.
https://app.seomatic.ai/api/mcpWhat to Ask About Your Next.js Site
- "Which pages rendered from my database lose the most clicks?"
- "Audit my live Next.js site for noindex and canonical mistakes."
- "Stage refreshed content for database pages that rank 5 to 15."
- "Find pages Google has not indexed and tell me why."
- "Which titles get seen but skipped?"
Fix Next.js SEO From Your Agent
Setup guides for Next.js with each agent: Claude, Claude Code, Claude Cowork, ChatGPT, Codex, Cursor, Gemini, OpenClaw, Hermes Agent, Grok Bot, Perplexity Computer, Manus. Setup guides per agent: Claude, ChatGPT, Claude Code, Cursor, Codex, Gemini and 24 more.
From Answer to Fix
By default, nothing changes on your site until you approve it. A fix is staged as a proposal that says what will change and why. Approved fixes run within seconds, the page's previous state is stored, and any edit to an existing page can be rolled back. A rollback refuses to overwrite edits someone made since. Changes that could take a page out of Google, like a noindex, need an extra confirmation.
Every shipped change is measured against its own baseline and the site's trend: after 14 days for a title, 28 for a content refresh, 42 for striking-distance and cannibalization work, 90 for a new page. It is marked verified only when the gain over the site's own trend is statistically clear and worth at least 5 more clicks; otherwise it is ineffective, or regressed when it falls more than 15%. Low-risk changes that lose traffic roll back on their own.
What Is Free
Connecting is free with no card. Search Console reports, page checks and 30-page site audits are free, as often as you like. Live market data (keyword volumes, competitors, backlinks) uses free questions: 5 a month, plus a one-time 10 when you connect Search Console, and one question covers up to 5 lookups. Staging and publishing fixes is part of paid plans, which start with a 14-day trial.
More SEOmatic MCP Pages
Frequently Asked Questions
Is there an official Next.js MCP server?
Yes. Vercel's next-devtools-mcp connects coding agents to a running Next.js 16 dev server for errors, routes and docs. It is a development tool, not a content tool.
How is SEOmatic's MCP different on Next.js?
It is built for SEO: it reads your Search Console data, stages fixes to your Next.js pages built from your database for your approval, and measures whether each change worked. Next.js's own MCP options are used to debug a Next.js app in development.
What do I need to connect Next.js?
A Postgres database reachable from the public internet, with a table that has an id column, plus INSERT and UPDATE permissions. Works with Supabase, Neon, Railway, Render, RDS and Lightsail. SSL is used automatically.
Will SEOmatic publish to Next.js without asking?
No. By default every change waits for your approval, your agent is told never to approve on its own, and any applied change can be rolled back.


