PostNimbo

com.postnimboPublished by postnimbo.comOfficial publisherv1.0.0Updated Nov 5, 2026

Schedule social posts to 30+ networks, answer the inbox and run chat automations.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

PostNimbo is a remote MCP server that lets an assistant schedule social posts to 30+ networks, reply to the inbox and run chat automations.

What you can do
  • Schedule and publish social media posts across 30+ networks
  • Answer and manage messages in the social inbox
  • Run chat automations
  • No tool list is published, so the exact actions available are not documented in the supplied material
When to use it
Useful when you want an assistant to plan and schedule social media content, keep up with incoming messages, or handle chat automation from one connected account instead of switching between network dashboards.
Requirements
A remote MCP endpoint at postnimbo.com reached over streamable HTTP. OAuth authentication is required, so a PostNimbo account and an authorization grant are needed. No environment variables or headers are declared.
Before you install
The server can publish posts and respond to messages on connected social accounts, so assistant actions are visible to the public and to customers. OAuth grants access to the PostNimbo account; review the scopes requested and revoke access if no longer needed. No tool list is published, so confirm what it can change before enabling it.

Installation

In SourceWeft

  1. Open PostNimbo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.postnimbo%2Fpostnimbo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "postnimbo": {
      "type": "http",
      "url": "https://postnimbo.com/api/mcp-oauth-dynamic"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.