posterly
posterly is an MCP server published by awpthorp, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from awpthorp. Last verified 2026-08-20.
Does posterly support the current MCP specification (2026-07-28)?
Not yet confirmed. posterly is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is posterly a first-party (official) MCP server?
Yes. posterly is the first-party MCP server published by awpthorp (last verified 2026-08-20).
How do I connect to posterly?
posterly is available via a hosted remote endpoint at https://www.poster.ly/api/mcp, the package npm:posterly-mcp-server, the official MCP Registry under io.github.awpthorp/posterly, the source repository at https://github.com/awpthorp/posterly. Authentication: unknown. Transports: streamable-http.
Does posterly support MCP revision 2026-07-28?
No. posterly was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
Does posterly support MCP revision 2025-11-25?
Yes. posterly supports MCP revision 2025-11-25 (checked 2026-08-20).
When were posterly's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Validate, schedule, publish, and analyze social content across 18 platforms with posterly.
Which MCP spec revisions does posterly support?
posterly has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Not supported | Source | |
| MCP 2025-11-25 | Supported | Source |
How widely adopted is posterly?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for posterly
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
The repository this server declares no longer resolves. That is a measurement, not
a failed lookup: https://github.com/awpthorp/posterly returned 404 when checked.
Package (npm) as of
- Latest version
0.35.1- Last published
- First published
- Releases
- 56
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 1.0 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.awpthorp/posterly at version 0.27.1 - lists remote endpoint https://www.poster.ly/api/mcp and repository https://github.com/awpthorp/posterly - accessed
- poster.ly product site, retrieved 2026-08-20 - presents posterly as the "first scheduler with a public MCP server", names the npm package posterly-mcp-server and the endpoint https://www.poster.ly/api/mcp, and prices API and MCP access as a paid add-on, which establishes the server as the vendor's own - accessed
- npm registry metadata for posterly-mcp-server at published version 0.35.1, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed