Connect ViewPrinter and your agent gets 18 tools, among them accounts_connect, accounts_list, accounts_performance. It answers at https://viewprinter.tech/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Schedule social posts to TikTok, Instagram, Facebook, YouTube and X; manage accounts and media
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
accounts_connect | Connect a social account. Opens the platform in the person's browser so they can sign in and approve access — that part cannot happen here, because it needs their session and their consent. Call it again after they finish and it reports the Inputs: platform |
accounts_list | List every social account you can post to, across all your workspaces. Each account includes the workspace it belongs to and any groups it is in. Use the returned ids to name post destinations explicitly, or a group name to name several at |
accounts_performance | How each connected account is performing: followers, posts, total likes and following, each with how far it has moved over the period. Ordered by followers, largest first. Numbers are as of the last sweep rather than live — every account ca Inputs: period |
groups_create | Name a set of accounts. Afterwards posts_schedule can take the name instead of every id. The name is how it is addressed, so it has to be unique in the workspace and is matched without regard to case. All the accounts must be in one workspa Inputs: name, description, account_ids |
groups_delete | Remove a group. The accounts in it are not touched and stay connected — only the name and its membership go. Posts already scheduled through it are unaffected, because a post records the accounts rather than the group. Inputs: name |
groups_list | Your named sets of accounts. Each group lists its members with the state of each, and how many of them need reconnecting — a post naming a group is refused outright if any member cannot publish, so check here before composing one. Use a gro |
groups_update | Rename a group, re-describe it, or change who is in it. account_ids is the full membership afterwards, not a list to add: whatever is sent replaces what was there. Omit it to leave the members alone. Inputs: name, new_name, description, account_ids |
media_confirm | Record a file that finished uploading. Its size and type are read back from storage rather than taken on trust. Safe to call again if the first response was lost. Inputs: id, kind, description |
media_delete | Remove a file and its stored bytes. This cannot be undone, and any post still using it will lose it. Inputs: id |
media_list | Every file uploaded in your workspaces, newest first. Use these ids when attaching media to a post. |
media_update | Say what a file shows, in your own words. On a base image this is who is on camera — "a woman in her early twenties, blonde hair in a loose bun" — and a campaign reads it so the same person appears in every render instead of changing betwee Inputs: id, description |
media_upload | Reserve an id and get a short-lived URL to PUT the file to. The bytes go straight to storage, not through this API. Call media_confirm with the same id once the PUT succeeds — nothing is recorded until then. Inputs: kind, mime_type |
platforms_list | What each platform accepts. Called with nothing, it lists every platform with the media kinds and counts it takes and its caption limit — enough to decide where a post can go. Name platforms to add their recommended sizes and durations, the Inputs: platforms |
posts_cancel | Stop a post before it goes out. Destinations that have not started are cancelled; any already being published cannot be recalled and are returned in still_going. Safe to call again. Inputs: post_id |
posts_list | Posts in your workspaces, newest first, each with the state of every destination it was sent to. Call it to check whether something published, and before changing or cancelling anything — posts_update and posts_cancel both take a post_id fr |
posts_performance | How published posts are performing, one row per destination: views, likes, comments, shares and saves, each with how far it has moved over the period. Best first, so the default answers "what did well" in one call rather than by listing eve Inputs: period, sort_by, by, limit |
posts_schedule | Create a post and queue it for every account named. Pass draft true to hold it here instead, sending nothing until posts_update promotes it. Name accounts with ids from accounts_list, or name a group from groups_list and get all of its memb Inputs: content, account_ids, groups, media_ids, scheduled_at, platform_options |
posts_update | Change a post that has not gone out yet: its caption, its time, its destinations, or whether it is a draft. Editing is always allowed; sending a draft needs publishing enabled on the account, and where it is not the draft is left exactly as Inputs: post_id, content, scheduled_at, account_ids, groups, draft |
Every block below points at https://viewprinter.tech/api/mcp. Pick your client and copy.
claude mcp add --transport http viewprinter https://viewprinter.tech/api/mcp
{
"mcpServers": {
"viewprinter": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://viewprinter.tech/api/mcp"]
}
}
}{
"mcpServers": {
"viewprinter": {
"url": "https://viewprinter.tech/api/mcp"
}
}
}{
"servers": {
"viewprinter": {
"type": "http",
"url": "https://viewprinter.tech/api/mcp"
}
}
}{
"context_servers": {
"viewprinter": {
"url": "https://viewprinter.tech/api/mcp"
}
}
}{
"mcpServers": {
"viewprinter": {
"serverUrl": "https://viewprinter.tech/api/mcp"
}
}
}{
"mcpServers": {
"viewprinter": {
"url": "https://viewprinter.tech/api/mcp"
}
}
}name: ViewPrinter
version: 0.0.1
schema: v1
mcpServers:
- name: ViewPrinter
type: streamable-http
url: https://viewprinter.tech/api/mcp{
"mcpServers": {
"viewprinter": {
"httpUrl": "https://viewprinter.tech/api/mcp"
}
}
}{
"mcpServers": {
"viewprinter": {
"type": "http",
"url": "https://viewprinter.tech/api/mcp"
}
}
}{
"mcpServers": {
"viewprinter": {
"url": "https://viewprinter.tech/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fviewprinter.tech%2Fapi%2Fmcp&type=streamable_http&id=viewprinter&name=ViewPrinter
It answered our last check on 24 October 2026 in 368 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by viewprinter.tech and served from viewprinter.tech, the vendor's own domain: https://viewprinter.tech/api/mcp.
18, as returned by the server's own tools/list on 23 September 2026: accounts_connect, accounts_list, accounts_performance, groups_create, groups_delete, groups_list, groups_update, media_confirm, and 10 more.
It answered our last check on 24 October 2026 in 368 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://viewprinter.tech/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: tech.viewprinter. Endpoint host: viewprinter.tech. ARD identifier: urn:air:tech.viewprinter:mcp:viewprinter.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.