MCP Claude Hacker News
imprvhubLABSCO SUMMARY
Confidential P2s are excluded by default, and that is the setting not to touch.
The interesting choice here is the confidentiality gate: only blogs explicitly marked with the sticker are readable by the assistant, and the override to disable that check is documented as not recommended. Beyond that, the moving part is the background auth service — if tools disappear or the client asks you to authenticate again, check that service is running before touching the config.
What it is
A WordPress.com Reader integration published by Automattic. A small background service holds the OAuth session so the MCP server does not have to re-authenticate every time the desktop client restarts, and the whole thing is driven in plain language rather than by naming tools.
What you get
- Your Reader feed: recent posts from the blogs you follow, filtered by count or by day
- Notifications: unread counts, comments-only views, and marking them read
- Tags: posts from a tag, subscribing and unsubscribing, and listing the tags you follow
- Blogs: the list you follow, following and unfollowing, and recommendations for new ones
- A8C posts for Automattic company updates
- A confidentiality check that only allows AI access to blogs carrying the
p2_confidentiality_disabledsticker
Requirements
A WordPress.com account and a developer application you create, with the website URL set to http://localhost:3000 and the redirect URI to http://localhost:3000/auth/callback. Its Client ID and Client Secret go into web-app/.env as WORDPRESS_CLIENT_ID and WORDPRESS_CLIENT_SECRET, alongside REDIRECT_URI, PORT, JWT_SECRET and MCP_SERVER_URL. Node.js is required; npm run setup installs, builds, configures Claude Desktop and starts the auth service, after which you authorise in the browser.
Setup effort
Build from source — git clone https://github.com/Automattic/wordpress-reader-mcp.git
USE CASES
01
Catching up without opening Reader
Ask for the latest posts from the blogs you follow and have them summarised in one pass.
02
Clearing a notification backlog
Check unread counts, look at just the comments, then mark them read.
03
Following a topic
Subscribe to a tag and pull its recent posts in the same conversation.
04
Fixing a session that stopped working
Check the background auth service status, restart it, and re-authorise in the browser.
BEFORE YOU INSTALL
What to know first
Requires
- A WordPress.com account and a WordPress.com developer application (Client ID and Client Secret)
- Node.js
- Claude Desktop
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
Create an application at https://developer.wordpress.com/apps/ with Website URL http://localhost:3000 and Redirect URI http://localhost:3000/auth/callback, then copy its Client ID and Client Secret
TERMINAL
git clone https://github.com/Automattic/wordpress-reader-mcp.git
cd wordpress-reader-mcp
npm run setupWhen prompted, enter your WordPress.com Client ID and Client Secret; the setup then opens your browser to authenticate with WordPress.com
Restart Claude Desktop
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"wordpress-reader": {
"command": "node",
"args": [
"<YOUR_PATH_TO_THIS_FOLDER>/mcp-server/dist/index.js"
]
}
}
}npm run setup tries to add this for you. If it could not, add it by hand; <YOUR_PATH_TO_THIS_FOLDER> is the full path of your clone.
WORDPRESS_CLIENT_ID and WORDPRESS_CLIENT_SECRET are not set in this block: npm run setup asks for them and keeps them in web-app/.env, where the background authentication service reads them.
