INDIVIDUAL MCP TOOL
get_content
Returns the full text of one published post or page as Markdown, along with its title, URL and publication date.
LIVE ENDPOINT
https://miriamschwab.me/wp-json/mmsar/v1/mcp
Connect to this endpoint to inspect the live schema for get_content and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description contains a write-action term.
- A tool name or description suggests retrieving external content.
Parent server
CONNECT 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.
Related tools
search_content— Full-text search across the published posts and pages of MiriamSchwab.me.list_content— Lists published content newest first, without searching.get_site_overview— What this site is, who runs it, how much content it has, which topics it covers, and which machine-readable endpoints it publishes.