Content Tools
miriamschwab.me
An MCP server that provides full-text search and retrieval of published posts and pages from MiriamSchwab.me.
ENDPOINT 1
https://miriamschwab.me/wp-json/mmsar/v1/mcp
MCP server metadata
- Name
- mmsar-miriamschwab-me
- Version
- 1.66.0
Read-only access to the published content of MiriamSchwab.me (https://miriamschwab.me/). Posts, talks, and the WordPress plugins I build Start with `search_content` when you have a topic, or `list_content` when you want to see what is here. Both take an optional `topic` (a category or tag slug, listed by `get_site_overview`) and return URLs; pass one to `get_content` to read the full text as Markdown. Do not fetch the site's HTML pages — `get_content` returns the same content already parsed. Everything here is public and already published. There is no draft or private content behind this server, and nothing here can modify the site.
Known tools 4
search_contentFull-text search across the published posts and pages of MiriamSchwab.me.
Inferred read-onlyget_contentReturns the full text of one published post or page as Markdown, along with its title, URL and publication date.
Potential side effectsget_site_overviewWhat this site is, who runs it, how much content it has, which topics it covers, and which machine-readable endpoints it publishes.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mmsar-miriamschwab-me]
url = "https://miriamschwab.me/wp-json/mmsar/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mmsar-miriamschwab-me": {
"type": "http",
"url": "https://miriamschwab.me/wp-json/mmsar/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mmsar-miriamschwab-me
Remote MCP URL: https://miriamschwab.me/wp-json/mmsar/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mmsar-miriamschwab-me": {
"url": "https://miriamschwab.me/wp-json/mmsar/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mmsar-miriamschwab-me": {
"type": "http",
"url": "https://miriamschwab.me/wp-json/mmsar/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mmsar-miriamschwab-me",
"transport": "streamable-http",
"url": "https://miriamschwab.me/wp-json/mmsar/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.