wp_get_site_info: inspect public site information
Returns basic facts about the site. The cheapest orientation call available.
Arguments
None.
Permissions
mcp:read and wp:content:read. No WordPress capability required — the only tool in the WordPress groups with no capability check at all.
That reflects what it returns: information a visitor could largely determine from the site itself.
What it returns
| Field | Meaning |
|---|---|
name |
The site title |
description |
The tagline |
url |
The home URL |
locale |
The site language |
timezone |
The site timezone |
wp_version |
The WordPress version |
blog_id |
Which site of a multisite network this is |
blog_id is the field to check first
On multisite, this is the fastest confirmation that you are connected to the site you think you are.
Every MCP server is site-scoped, and configuring one subsite while intending another is a real and confusing mistake — the tools all work, they just work on the wrong content.
Get the site info and tell me the name and blog ID.
Make that the first call of any session on a network you did not set up yourself.
locale and timezone matter for content work
Both affect how an assistant should behave:
localeis the language POM AI's own generation tools work in, and the language content should be written in. An assistant drafting copy for a site with anes_ESlocale should write European Spanish.timezonedetermines how dates in tool responses relate to the site's own sense of "today". Scheduling or date-sensitive work needs it.
Neither is guessable from the domain.
wp_version is public anyway
WordPress exposes its version in various ways by default, so returning it here is not a disclosure. It is useful for the assistant to know which core features exist.
What it does not return
- No option values. Use
wp_get_option. - No theme or plugin inventory. Not exposed at all.
- No user information.
- No admin email. That is an option, and readable separately with the appropriate care.
- No network information beyond this site's own ID.
Using it well
At the start of any session:
Get the site info, count the posts and pages, and list the post types. Then stop.
Four read calls and you know what site you are on, how big it is, and what kind of content it holds — before agreeing to change anything.
Common problems
| Symptom | Cause |
|---|---|
| The wrong site name | You are connected to a different subsite |
An unexpected blog_id |
Same — check the MCP URL |
| A locale that surprises you | The site language differs from the content language |
That last row is worth a second look on multilingual sites: the locale is the site language, and a Polylang site serves several. See Provide context and terminology.
Related
wp_get_option- The status endpoint, which reports similar facts without authentication