micm.mx

mx.micmPublished by micm.mxOfficial publisherv0.1.0Updated Oct 25, 2026

Redacta, programa y mide posts de micm.mx. Draft, schedule and track micm.mx social posts.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server for micm.mx that lets an assistant draft, schedule and track social posts.

What you can do
Draft social posts for micm.mx from an assistant conversation. Schedule posts for later publishing. Track the performance of published posts. The manifest lists no individual tools, so the exact operations are not documented.
When to use it
Useful if you manage micm.mx social content and want an assistant to help write, queue and monitor posts without switching tools.
Requirements
A remote endpoint at mcp.micm.mx over streamable HTTP. OAuth authentication is required, so a micm.mx account with access is needed. No environment variables or headers are declared.
Before you install
The server can publish and schedule posts on your behalf, which changes public content; review drafts before scheduling. It requires OAuth sign-in to your micm.mx account, so grant access only to a trusted client. Post content and tracking data pass to micm.mx.

Installation

In SourceWeft

  1. Open micm.mx 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/mx.micm%2Fmcp/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": {
    "micm-mx": {
      "type": "http",
      "url": "https://mcp.micm.mx/mcp"
    }
  }
}

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. v0.1.0LatestOct 25, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.