Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://api.pinlyx.com/mcpปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.azorkai-crmsolid-mcp https://api.pinlyx.com/mcpRun in a terminal.
{ "mcpServers": { "io.github.azorkai-crmsolid-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.pinlyx.com/mcp" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิด@crmsolid/mcp-server is an MCP server for social media. It gives Claude Desktop, Claude
Code, Cursor, ChatGPT and any other Model Context Protocol client typed access to your
social DM inbox and your posting calendar across 12 platforms, so you can triage messages,
draft replies, schedule posts and pull stats without opening a single dashboard.
Add this to your MCP client config, restart the client, and ask it to list your social
accounts. Nothing to install: npx fetches the package on first run.
{
"mcpServers": {
"crmsolid": {
"command": "npx",
"args": ["-y", "@crmsolid/mcp-server"],
"env": { "CRMSOLID_API_KEY": "csk_live_..." }
}
}
}
Create the key at app.pinlyx.com/settings/developers. Config file locations per client:
Then say, in the client: List my connected social accounts. If you get a table back, you
are done. If you do not, jump to Troubleshooting.
These are ordinary sentences, not commands. The client picks the tools.
Summarise my social inbox and show the conversations waiting longest for a reply.
Draft a friendly reply to the Instagram DM from Dilara about the 12 month plan.
Anything mentioning a refund today? Open a task for each one and assign the contact.
Plan five posts for next week from what we shipped, and show me the table before you schedule any of them.
Move Thursday's LinkedIn post to Friday 09:00 Europe/Istanbul.
How did last month's posts do compared with the month before?
The server is not a separate copy of your data. It reads and writes the same social inbox and the same posting calendar you see in Pinlyx, so a conversation you triage from Claude is already triaged when you open the panel, and a post your assistant queues shows up in the calendar with everything else.
Both screens come from the live demo at demo.crmsolid.com, which is read only and needs no account.
Instagram, Facebook, X (Twitter), LinkedIn, TikTok, YouTube, Threads, Pinterest, Reddit, Bluesky, Telegram and WhatsApp. One inbox, one calendar, one tool surface. A recipe written against Instagram works against LinkedIn without changes, though per platform messaging windows and policies still apply.
Thirteen social tools ship in this release: seven for the DM inbox, six for posts. They sit
alongside 129 CRM tools (contacts, deals, tasks, email threads and mailboxes, finance,
analytics, sequences, pipelines, jobs, webhooks, agents, Google Ads) on the same server,
142 tools in all, which is the point: a DM that never becomes a contact record is a DM you
will lose. The email family can also connect a mailbox: crm_add_email_account takes an
address and an app password, fills in the IMAP/SMTP hosts for the common providers, and
saves nothing unless both connections authenticate. It never returns the password.
Full arguments, example calls and example responses for every tool: docs/tools-reference.md.
The publishing rule. crm_schedule_social_post requires scheduledAt unless you pass
publishNow: true explicitly. Leave both out and the call is rejected with
scheduledAt is required unless publishNow is true. An assistant that misunderstands you
gets an error, never a surprise post. Two more guards sit behind it: each target account's
daily post limit is checked before anything is written, and a post that already went out on
the platform cannot be cancelled or deleted through the API.
Attach these when you want the model to read state without spending a tool call.
A flag beats the matching environment variable. Two useful profiles:
// Content scheduling only, on a machine that must never touch the inbox.
{
"mcpServers": {
"crmsolid": {
"command": "npx",
"args": ["-y", "@crmsolid/mcp-server", "--tools", "posts"],
"env": { "CRMSOLID_API_KEY": "csk_live_..." }
}
}
}
// Read only, for a shared laptop or a demo.
{
"mcpServers": {
"crmsolid": {
"command": "npx",
"args": ["-y", "@crmsolid/mcp-server", "--read-only"],
"env": { "CRMSOLID_API_KEY": "csk_live_..." }
}
}
}
Requires Node 20 or newer. The package is ESM, ships a crmsolid-mcp binary, and speaks
MCP over stdio.
MCP client (Claude Desktop, Claude Code, Cursor, ChatGPT, ...)
| stdio, JSON-RPC
crmsolid-mcp (this package: filters, then forwards)
| HTTPS, Authorization: Bearer csk_live_...
POST https://api.crmsolid.com/mcp
|
your connected Instagram / LinkedIn / X / WhatsApp / ... accounts
The package is a thin stdio proxy. It mirrors tools/list, tools/call, resources/* and
prompts/* from the hosted endpoint, and applies your --tools and --read-only filters to
the tool list before the client ever sees it. A filtered tool is not listed and not callable:
the proxy refuses the call rather than forwarding it. Resources and prompts pass through
unfiltered, because a resource is inert data and a prompt is a template, and the scopes on
your key still gate what either one can read. The proxy holds no platform credentials of its
own: the Instagram token, the LinkedIn token and the rest live server side, so nothing a
model reads or writes can leak them onto the local machine.
Remote clients that want a URL instead of a subprocess can call
https://api.crmsolid.com/mcp directly with a bearer header. See
docs/chatgpt-and-other-clients.md.
Four new scopes ship with this release, granted per key:
Four properties worth knowing before you hand a key to a model:
--read-only and --tools are local filters. They protect you from a confused
model. They are not a substitute for scoping the key, because a stolen key is used
without your proxy. Scope the key first, filter second.Rotate a key from the same screen you created it on. Revoking takes effect immediately.
Full symptom to fix walkthrough, including proxies, stale npx caches and how to read your
client's MCP log: docs/troubleshooting.md.
Quick self test, no client involved:
npx -y @crmsolid/mcp-server --version
curl -s https://api.crmsolid.com/mcp \
-H "Authorization: Bearer $CRMSOLID_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Hosted documentation: docs.pinlyx.com/integrations/mcp/. Vendor neutral tutorials, including ones that do not involve Pinlyx at all: Pinlyx/mcp-social-media-guide.
@crmsolid/node: the REST client, for code
that is not an AI assistant.n8n-nodes-crmsolid: the n8n
community node, for the workflows an assistant is not in. Same API, same keys, so a
contact your assistant files is the one an n8n branch picks up.Issues and pull requests: Pinlyx/pinlyx-mcp.
When you report a connection problem, include your client and version, the output of
npx -y @crmsolid/mcp-server --version, your config with the key redacted, and the relevant
lines from the client's MCP log.
Licensed MIT. The Model Context Protocol specification lives at modelcontextprotocol.io.
Pinlyx CRM for AI assistants: contacts, deals, social inbox and posts, email and Google Ads.
{ "mcpServers": { "io.github.azorkai-crmsolid-mcp": { "url": "https://api.pinlyx.com/mcp", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: CRMSOLID_API_KEY, CRMSOLID_BASE_URL, CRMSOLID_READ_ONLY, CRMSOLID_TOOLS
Pinlyx เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Pinlyx CRM for AI assistants: contacts, deals, social inbox and posts, email and Google Ads.