SendIt

What SendIt does

SendIt MCP server gives compatible agents access to SendIt's social publishing workflows. The documented capabilities cover creating and scheduling social posts, uploading media, and reviewing analytics. The integration is intended for workflows where an agent needs to prepare, publish, or inspect social content through SendIt rather than through separate platform-specific connections.

The public service exposes a live MCP endpoint at https://sendit.infiniteappsai.com/api/mcp. A read-only discovery check reported 148 available tools for the release described in the repository. The listing does not provide a complete tool-by-tool inventory, so the exact operation names and platform coverage should be checked in the current package documentation.

How it works

SendIt supports two authentication approaches: OAuth and API keys. Interactive connectors should use the host's OAuth credential store when available. Terminal and developer bot integrations can provide an API key through their secret storage.

Agents can connect to the hosted endpoint through supported connector configurations, or use the SendIt CLI and stdio bridge for terminal-based workflows. The repository documents integrations for Hermes, OpenClaw, Grok, Meta Muse, and Muse Code. It also provides a package for general terminal agents. Grok connections use its custom MCP connector or remote MCP contract; Meta Muse access depends on its connector submission and approval process.

As a 🌐 Social Media tool, the SendIt MCP server is most relevant when an agent must combine content operations with scheduling or analytics review. It is less suitable if the required workflow depends on an undocumented tool or a client not covered by the repository's installation paths.

Setup and configuration

For terminal use, the documented command is:

npx --yes --package=@senditapp/mcp@0.2.1 sendit --help

The CLI guide covers persistent installation, stdio configuration, and a downloadable GitHub archive fallback. Terminal integrations may use the SENDIT_API_KEY secret. OAuth-based hosts should instead follow their native credential setup.

OpenClaw can install the pinned npm plugin with openclaw plugins install @senditapp/openclaw@0.2.0. Its ClawHub installation path is also documented. Muse Code uses its native MCP settings path and the command muse mcp login sendit. Hermes has a workflow skill and native OAuth MCP configuration. Grok requires adding the public endpoint at grok.com/connectors for its custom connector flow.

Meta Muse setup is subject to its hosted connector submission process and directory approval. The repository notes that Muse's native Code plugin format is a developer preview, while the tested stable 1.4.1 build has plugins disabled; its native skill and MCP settings path works in that build.

Tools and capabilities

The SendIt MCP server is documented for:

• Publishing social posts.
• Scheduling social posts.
• Uploading media for social content.
• Reviewing analytics.
• Exposing SendIt functionality through a hosted MCP endpoint.
• Providing a CLI and stdio bridge for terminal agents.

The release notes report 148 tools from read-only discovery, but the provided material does not enumerate every tool or describe the individual input and output schemas.

Limitations and notes

The repository is an integration and installation source; the private application repository is not required for users. Validation status differs by host. In particular, the Cursor-format Grok plugin bundle is described as a review candidate, and its import into Grok Bot is not verified. Meta Muse directory availability requires approval. The repository also directs users to its release-status documentation for publication and validation boundaries.

The exact client support list in this entry is limited to the hosts named in the repository. OAuth availability, API-key handling, and installation details can vary by host, so credentials should be configured using the host-specific instructions rather than assuming one setup applies everywhere.