A brief becomes a real page.Visibility MCP integration
Give Visibility a conversational editing surface.
Read and update Visibility post SEO metadata with EMCP’s free integration. Work on titles, descriptions, canonical URLs, the robots directives Visibility manages, sitemap exclusion, social previews and the per-post Schema.org type.
Free integrationVisibility (native-aeo-pack) active
Set a post’s metadata and schema type in one pass.
| Workflow detail | What to check |
|---|---|
| Stored title and description | Empty means no explicit value |
| Robots flags | noindex, nofollow, noimageindex, nosnippet |
| Schema type | One of Visibility’s allowed values |
| Readback | Verify the saved fields |
A practical place to start
Set a post’s metadata and schema type in one pass.
- 01
Read what Visibility stores
Read the post’s stored title, description, canonical, robots flags and schema type. Visibility keeps each field as its own post meta key, so an unset field simply comes back empty rather than generated.
- 02
Draft the fields that need changing
Propose only the values the post needs: a clearer title, a description grounded in the page, an explicit noindex or sitemap exclusion for a page that should stay out of search, or a Schema.org type that matches the content. Leave canonical and the remaining flags intact unless the brief says otherwise.
- 03
Save and read back
Save the approved fields and read them back. A schema type outside Visibility’s allowed list is refused with the list, so a typo never reaches the database; an empty schema type restores the site default.
Built for Visibility
Set the exact fields Visibility reads
Visibility stores each SEO field as its own post meta key, so there is no serialized block to decode and no generated value hiding behind an empty override. Read the current values, propose only the fields that need changing, and read the approved values back after saving. For a post that should stay out of search, the robots flags and the sitemap exclusion are separate fields, so set both deliberately.
Treat the schema type as a reviewed choice
The per-post Schema.org type override is validated against the list Visibility itself allows. That keeps a typo or an invented type out of the database, and it means the AI can only pick from the types you have configured. An empty value restores the site default, which is the right answer for most posts; reserve overrides for content whose type genuinely differs from the site’s default.
Check the page that visitors and crawlers receive
Stored values are part of the result, not the whole result. Site-level defaults and page context influence the rendered tags. Pair a metadata update with an inspection of the public page so the editor can see whether the requested title, robots and schema settings took effect. Metadata maintenance does not guarantee a ranking improvement.
Read the SEO tool documentation for the supported operations and parameters.
Get connected
Put Visibility in your AI’s toolkit.
- 1
Prepare the integration
Activate Visibility (native-aeo-pack) and free EMCP. Pick a published post whose metadata or schema type needs attention and keep its URL and post ID together.
- 2
Check the available tools
Connect your MCP client to this WordPress site and check visibility-read / visibility-write in EMCP’s tool settings; the write tool ships disabled by default. Inspect the live operation catalog before starting; installed plugins and saved tool choices determine what is available.
- 3
Establish a first test
Compare one post’s stored values with its public title, description and robots meta. Decide which fields deserve an explicit value before writing anything.
Then connect Claude Code, Claude Desktop, or Cursor to use the Visibility tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Visibility, supported operations, and the workflow on your site.
Do I need EMCP Pro for Visibility?
No. Visibility is one of EMCP’s free plugin integrations, contributed by the community in EMCP 3.17.1.
What happens if the AI sends a schema type Visibility does not know?
The write is refused with the list of allowed values and nothing is stored, the same rule Visibility applies to its own REST writes. An empty string clears the override so the post uses the site default.
Can I update category metadata?
Not in this release. The adapter is post-level only; term metadata is a planned follow-up.
Does this change how Visibility renders my pages?
No. EMCP writes the same post meta keys Visibility already stores, so its front-end output, sitemap and settings behave exactly as before.
Your tools. Your WordPress site.