MCP Integrations

Claude Cowork

Connect SocialCRM to Claude with OAuth, then analyze data, add prompts, and build or run reusable agents.

Connect SocialCRM to Claude as a remote MCP custom connector. Once authorized, Claude can read SocialCRM analytics, add durable prompts to brand prompt sets, and configure or run reusable SocialCRM agents.

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

Prerequisites

  • A Claude plan that supports custom connectors
  • A SocialCRM account with access to a company workspace
  • admin access to create reusable agents, or admin/editor access to add prompts and run agents

Quick Start

1. Open Claude 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.

2. Enter the SocialCRM MCP endpoint

Fill in the connector form:

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

3. Sign in and approve access

Save the connector. Claude discovers SocialCRM's OAuth metadata and redirects you to SocialCRM. Sign in to your SocialCRM company workspace, review the requested read/write scopes, and approve access. Do not paste a SocialCRM API key into Claude.

The connector requests socialcrm.read for analytics and read-only discovery. Prompt creation, agent creation, and workflow or agent runs additionally require socialcrm.write.

In-chat prompt from Claude asking the user to approve use of the SocialCRM connector for this conversation.
Approve the connector when Claude first needs it. SocialCRM still enforces company scope and role checks on every call.

4. 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"
  • "List my prompt sets and show the prompts in my main brand"
  • "Create a reusable content strategist for my main brand"

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.

API-key configuration for developer clients

OAuth is the supported path for Claude's connector UI. Claude Code and other developer clients that accept explicit headers can alternatively use a SocialCRM API key:

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

Do not paste this API-key configuration into the Claude web connector when OAuth is available.

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 — Remove and reconnect SocialCRM to restart OAuth. Confirm that your SocialCRM user still belongs to the selected company and has the role required by the tool.

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.