How to integrate Centralstationcrm MCP with Claude Agent SDK

Framework Integration Gradient
Centralstationcrm Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Centralstationcrm to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Centralstationcrm agent that can add new company to crm contacts, log a sales opportunity for a client, count total people in my crm, record a birthday for an existing contact through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Centralstationcrm account through Composio's Centralstationcrm MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Centralstationcrm
  • Configure an AI agent that can use Centralstationcrm as a tool
  • Run a live chat session where you can ask the agent to perform Centralstationcrm operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Centralstationcrm MCP server, and what's possible with it?

The Centralstationcrm MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Centralstationcrm account. It provides structured and secure access to your customer relationship data, so your agent can perform actions like managing contacts, creating deals, updating company records, and tracking key interactions on your behalf.

  • Automated contact management: Quickly add new people to your CRM, update their details, and ensure your contact database stays current without manual entry.
  • Company and organization creation: Effortlessly create new company records so you can keep your account-based selling and organization tracking up-to-date.
  • Deal tracking and creation: Instantly log new sales opportunities by creating deals linked to your contacts or companies, helping your team stay on top of the pipeline.
  • Detailed relationship enrichment: Add addresses, assistants, avatars, and contact details to people in your CRM, making every customer profile richer and more actionable.
  • Milestone and history recording: Record important life events or milestones (like birthdays or anniversaries) for each person to boost relationship management and personalized outreach.

Supported Tools & Triggers

Tools
Check ConnectionTool to verify the connection status of the centralstationcrm api key.
Count PeopleTool to retrieve the total number of people in the account.
Create CompanyTool to create a new company record.
Create DealTool to create a new deal record.
Create PersonTool to create a new person record.
Create Person AddressTool to create a new address for a specific person.
Create Person AssistantTool to create a new assistant (assi) entry for a specific person.
Create Person AvatarTool to create a new avatar for a specific person.
Create Person Contact DetailTool to create a new contact detail for a specific person.
Create Person Historic EventTool to create a new historic event for a specific person.
Delete CompanyTool to delete a company record by id.
Delete personTool to delete a person record by id.
Delete Person AddressTool to delete a person's address by its id.
Delete Person AssiTool to delete an assi entry of a person.
Delete Person AvatarTool to delete a person's avatar by its id.
Delete Person Contact DetailTool to delete a contact detail of a person.
Delete Person Historic EventTool to delete a historic event of a person by its id.
Get API User MaildropTool to retrieve the current api user's maildrop for people and companies.
Get CompanyTool to retrieve details of a specific company by id.
Get DealTool to retrieve details of a specific deal by its id.
Get DealsTool to retrieve a paginated list of all deals.
Get PersonTool to retrieve details of a specific person by id.
Get Person AddressTool to retrieve a specific address of a person by address id.
Get Person AddressesTool to retrieve all addresses for a specific person.
Get Person AssiTool to retrieve a specific assi entry of a person by id.
Get Person AssisTool to retrieve all assistant entries for a specific person.
Get Person AvatarTool to retrieve a specific avatar of a person by avatar id.
Get Person AvatarsTool to retrieve all avatars for a specific person.
Get Person Contact DetailTool to retrieve a specific contact detail by id for a person.
Get Person Custom FieldsTool to retrieve all custom fields for a specific person.
Get Person Historic EventTool to retrieve a specific historic event of a person by id.
Get Person Historic EventsTool to retrieve all historic events for a specific person.
Get PersonsTool to retrieve a paginated list of all people.
Merge PersonTool to merge another person into an existing person by id.
Search RecordsSearch records
Search PeopleTool to retrieve people matching search criteria.
Stats PeopleTool to retrieve key statistics about people.
Update CompanyTool to update an existing company by id.
Update PersonTool to update an existing person by id.
Update Person AddressTool to update a specific address of a person.
Update Person AssiTool to update an assi entry of a person.
Update Person Contact DetailTool to update a specific contact detail of a person by id.
Update Person Historic EventTool to update a historic event of a person by id.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Centralstationcrm account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Centralstationcrm functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Centralstationcrm
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["centralstationcrm"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Centralstationcrm
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Centralstationcrm tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Centralstationcrm
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Centralstationcrm and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Centralstationcrm
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["centralstationcrm"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Centralstationcrm tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Centralstationcrm through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Centralstationcrm MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Centralstationcrm MCP?

With a standalone Centralstationcrm MCP server, the agents and LLMs can only access a fixed set of Centralstationcrm tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Centralstationcrm and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Centralstationcrm tools.

Can I manage the permissions and scopes for Centralstationcrm while using Tool Router?

Yes, absolutely. You can configure which Centralstationcrm scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Centralstationcrm data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.