Data · Remote MCP server
posteverywhere.ai
Schedule and publish social posts to 11 platforms with media, campaigns, analytics and AI captions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.posteverywhere/mcp- Version
- 1.9.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- ai.posteverywhere
- Namespace
- Namespace verified by the MCP Registry via the domain posteverywhere.ai · how
- Repository
- github.com/posteverywhere/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.posteverywhere.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @posteverywhere/mcp | 1.9.0 | stdio |
How to connect posteverywhere.ai
posteverywhere.ai is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.posteverywhere.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @posteverywhere/mcp version 1.9.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @posteverywhere/mcp@1.9.0. It reads the environment variable POSTEVERYWHERE_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@posteverywhere/mcp@1.9.0"
],
"env": {
"POSTEVERYWHERE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Posokanei MCPUnofficial read-only MCP server for Greek supermarket price data from PosoKanei. | Local · stdio |
| Postal CodesPostal code lookup with place names and coordinates for 60+ countries. Via Zippopotam.us. | Remote · HTTPLive check: ✓ handshake |
| Postal Lookup MCPFree, keyless postal/ZIP code lookup: place name(s), state/region, and coordinates. | Remote · HTTPLive check: ✓ handshake |
| Postcodes MCPUK postcode lookup from postcodes.io. No key required. | Local · stdio |
| PosthogCapture analytics events, evaluate feature flags, and manage projects. | Local · stdio |
| Posthog MCP ServerMCP server for PostHog - product analytics for AI assistants. Query events, persons, insights, da... | Local · stdio |
| PostHog MCP ServerOfficial PostHog MCP Server for product analytics, feature flags, experiments, and more. | Remote · HTTP, SSELive check: sign-in required |
| Pota MCPParks on the Air MCP server. Park lookup, activator and hunter stats, live spots. | Local · stdio |