Social Media
parasiteseoposter.com
An MCP server for generating and managing social media draft posts from web pages, including page atomization, image search, and attaching images.
ENDPOINT 1
https://www.parasiteseoposter.com/api/v1/mcp
MCP server metadata
- Name
- parasiteseoposter
- Version
- 1.0.0
Tools call the parasiteseoposter.com /api/v1 endpoints as your workspace. Reads are free; generate_posts, atomize_page and publish_post draw on the workspace's prepaid API credit balance.
Known tools 6
generate_postsGenerate draft posts for an atomized page — one per connected channel of the page's domain.
Inferred read-onlysearch_imagesSearch Pexels and Unsplash for a photo (the same library the dashboard's picker uses).
Inferred read-onlypublish_postPublish a generated post now, or schedule it with scheduled_at (ISO-8601, future).
Potential side effectsCONNECT 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.parasiteseoposter]
url = "https://www.parasiteseoposter.com/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"parasiteseoposter": {
"type": "http",
"url": "https://www.parasiteseoposter.com/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: parasiteseoposter
Remote MCP URL: https://www.parasiteseoposter.com/api/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": {
"parasiteseoposter": {
"url": "https://www.parasiteseoposter.com/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"parasiteseoposter": {
"type": "http",
"url": "https://www.parasiteseoposter.com/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "parasiteseoposter",
"transport": "streamable-http",
"url": "https://www.parasiteseoposter.com/api/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.