# Pinlyx MCP [Verified] [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/CRM-Solid/crmsolid-mcp  
**GitHub Stars:** 6  
**npm Downloads (last month):** 194  
**Views:** 11  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/crm-solid-mcp

## Description
Read and reply to social DMs, schedule posts, and manage CRM contacts and deals across Telegram, X, WhatsApp, Instagram and email from your AI assistant.

## Tools
Capabilities this server exposes over MCP:

- **crm_list_social_accounts** — Lists connected accounts per platform
- **crm_list_social_conversations** — Filters by `platform`, `status`, `contactId`, `unreadOnly
- **crm_get_social_conversation** — One conversation plus its last 10 messages
- **crm_list_social_messages** — Message history, paged with `beforeMessageId
- **crm_send_social_message** — Sends a DM and pauses the AI agent for that contact
- **crm_mark_social_conversation_read** — Clears unread state, safe to repeat
- **crm_social_inbox_summary** — Totals per platform, plus the 10 oldest waiting replies
- **crm_list_social_posts** — Filters by `status`, `platform`, `fromDate`, `toDate
- **crm_get_social_post** — One post with its media, target account and outcome
- **crm_schedule_social_post** — Queues a post per target account, **never publishes by accident
- **crm_update_social_post** — Edits content, time or media while the post is still pending
- **crm_cancel_social_post** — Cancels a post that has not gone out
- **crm_social_post_stats** — Publishing outcomes per platform over `days

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "pinlyx-mcp": {
    "command": "npx",
    "args": ["-y","@crmsolid/mcp-server"],
    "env": {
      "CRMSOLID_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `CRMSOLID_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What CRM Solid MCP MCP server does

CRM Solid MCP MCP server gives MCP clients access to CRM Solid's connected social accounts, unified DM inbox, and social posting calendar. It supports Instagram, Facebook, X (Twitter), LinkedIn, TikTok, YouTube, Threads, Pinterest, Reddit, Bluesky, Telegram, and WhatsApp.

The server can list accounts and conversations, retrieve recent or paged message history, send direct messages, and mark conversations as read. Inbox summaries include totals by platform and the ten oldest conversations waiting for replies. Sending a message also pauses the AI agent for that contact.

For publishing workflows, CRM Solid MCP MCP server lists and retrieves posts, queues content for selected accounts, updates pending posts, cancels posts that have not been sent, and reports publishing outcomes by platform over a selected number of days. The same server also includes CRM tools for areas such as contacts, deals, tasks, email, finance, analytics, sequences, pipelines, jobs, webhooks, and agents.

## How it works

The package communicates with an MCP client over stdio and reads and writes the shared CRM Solid inbox and posting calendar. Changes made through the client are reflected in the CRM Solid interface rather than a separate local data store.

Post scheduling includes explicit safeguards. A scheduled time is required unless `publishNow: true` is supplied, so an incomplete request is rejected instead of publishing unexpectedly. Daily limits for each target account are checked before a post is written, and posts that have already been published cannot be cancelled or deleted through the API.

The server also provides MCP resources for connected accounts, inbox state, scheduled posts, and published posts. Included prompts cover inbox triage, weekly content planning, and drafting a DM reply. The reply-drafting prompt produces drafts only; it does not send them.

## Setup and configuration

CRM Solid MCP MCP server requires Node 20 or newer. Install nothing globally: configure the MCP client to run `npx -y @crmsolid/mcp-server`, then provide a CRM Solid bearer key in `CRMSOLID_API_KEY`. Keys are created in CRM Solid's developer settings.

The default API endpoint is `https://api.crmsolid.com`. `CRMSOLID_BASE_URL` can point to another host, such as a staging environment. `CRMSOLID_TOOLS` accepts a comma-separated tool filter, with examples including `social,posts`. Set `CRMSOLID_READ_ONLY` to remove write tools. Command-line flags override their matching environment variables.

After restarting the client, asking it to list connected social accounts provides a basic connection check.

## Tools and capabilities

- List connected social accounts by platform.
- Filter conversations by platform, status, contact, or unread state.
- Retrieve recent conversation messages or page through message history.
- Send DMs and clear unread status.
- Summarize waiting replies across platforms.
- Schedule, edit, cancel, and inspect social posts.
- Compare publishing outcomes by platform.

CRM Solid MCP MCP server is suitable for read-only deployments through `--read-only`, or for limiting a deployment to selected tool groups with `--tools`. Its social write operations should be used with awareness of platform messaging windows and policies.

_Full upstream README: https://allmcps.com/mcp/crm-solid-mcp/readme_