MCP Integrations

Claude Cowork

Add SocialCRM as a connector in the Claude desktop app, and build live artifacts that call SocialCRM tools.

Connect SocialCRM to Claude Cowork — the Claude desktop app's workspace mode — as an MCP connector. Once connected, Claude can pull brand data, AI visibility metrics, and workflow results into any conversation, and you can build live artifacts that stay in sync with your SocialCRM account.

Looking for the Claude CLI? This guide is for the Claude desktop app. For terminal-based setup, see Claude Code.

Prerequisites

  • Claude desktop app installed and signed in (macOS or Windows)
  • Cowork mode enabled on your Claude plan
  • SocialCRM account with an API key (get one from Settings > API Keys)

Quick Start

1. Create or copy a SocialCRM API key

In SocialCRM, open Settings > API Keys and create a key that starts with sk_live_. Keep it handy — you'll paste it into Cowork in the next step.

2. Open Cowork Connectors

In the Claude desktop app, open Settings, then choose Connectors. Click Add custom connector (or Add MCP server, depending on your build).

Claude desktop app Settings with Connectors selected in the sidebar and the Add custom connector button visible.
Open Settings → Connectors in the Claude desktop app, then start a new custom connector.

3. Enter the SocialCRM MCP endpoint

Fill in the connector form:

  • Name: SocialCRM
  • Transport: Streamable HTTP
  • URL: https://socialcrm.com/mcp

4. Add the Authorization header

In the Headers section, add:

  • Key: Authorization
  • Value: Bearer sk_live_YOUR_KEY_HERE

Replace sk_live_YOUR_KEY_HERE with the real key from SocialCRM.

Cowork Add custom connector form with Name set to SocialCRM, Transport set to Streamable HTTP, URL set to https://socialcrm.com/mcp, and an Authorization header with a Bearer token value.
Enter the production SocialCRM endpoint and add your API key as a standard HTTP Authorization header, then save.

5. Save and approve access

Click Save. When Claude offers to use the new connector in a conversation, approve it. The 21 SocialCRM tools become available to Claude automatically — no restart required.

In-chat prompt from Claude asking the user to approve use of the SocialCRM connector for this conversation.
When Claude first needs the connector, approve it to make all 21 SocialCRM tools available for the session.

6. Verify the connection

In a Cowork session, try any of:

  • "List my brand profiles"
  • "Get platform metrics for my main brand"
  • "Show recent mentions for Stevens Creek Toyota"
  • "List available workflows and check my credit balance"

Claude should discover and call the SocialCRM MCP tools without further setup.

What You Can Ask

Because Cowork sits on the desktop alongside Claude's file, shell, and artifact tools, SocialCRM works well in cross-tool workflows:

  • "Pull my brand mentions this month and save them to ~/Desktop/mentions.csv."
  • "Build me a one-page summary of our AI visibility scores across ChatGPT, Claude, and Gemini."
  • "Draft a customer email using the latest AI Shop Checkup findings for Ace Auto Repair."
  • "Compare competitor rankings across the last three runs and summarize what changed."

Build a Live Artifact Powered by SocialCRM

Cowork can persist interactive HTML pages as live artifacts that call your connectors on every open — so a morning "brand dashboard" is always fresh without re-running the conversation.

Inside an artifact, call any SocialCRM tool via window.cowork.callMcpTool. The method returns the same MCP-shaped result Claude sees.





  
  My SocialCRM Brands
  


  
My SocialCRM Brands

  
Loading…

A few practical notes:

  • The server field must match the Name you gave the connector in Cowork. If you renamed it from SocialCRM, update the artifact to match.
  • MCP tool output is wrapped in { content: [{ type: 'text', text: '...' }] }. SocialCRM puts JSON in the text field, so parse it before rendering.
  • Do not call localStorage or sessionStorage — Cowork artifacts run in a sandbox that blocks browser storage. Keep state in memory or re-fetch on open.
  • Any tool in the Tool Reference is callable the same way: swap the name (e.g. get_platform_metrics, get_brand_mentions, run_workflow) and pass its arguments.

Ask Claude in a Cowork session to "turn this into a live artifact I can re-open each morning" once you've seen data you'd like to keep returning to — that's usually the right trigger.

Manual Configuration (config file)

If your build of the Claude desktop app supports editing the MCP config directly, the Cowork connector maps to:

{
  "mcpServers": {
    "SocialCRM": {
      "type": "http",
      "url": "https://socialcrm.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_YOUR_KEY_HERE"
      }
    }
  }
}

Use this as a reference — the Connectors UI is the supported path.

Troubleshooting

Connector saves but no tools appear — Start a new Cowork conversation, or explicitly approve the connector when Claude asks. Some builds require re-approval per session on first use.

Authentication failed / 401 / 403 — The header value must begin with Bearer followed by your full SocialCRM API key. Regenerate a fresh key in Settings > API Keys if needed.

Live artifact can't reach the tool — Confirm the connector name matches the artifact's server field. Open Cowork's Connectors panel and check the connector status is green.

Tools work in chat but not in artifacts — Cowork requires the user to have the connector enabled for the current session. Approve it when prompted, or re-enable it from Connectors.