How to integrate Stormboard MCP with Claude Agent SDK

Framework Integration Gradient
Stormboard Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Stormboard to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Stormboard agent that can summarize all sticky notes on a board, add action items to a stormboard project, list team members assigned to a board through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Stormboard account through Composio's Stormboard 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 Stormboard
  • Configure an AI agent that can use Stormboard as a tool
  • Run a live chat session where you can ask the agent to perform Stormboard 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 Stormboard MCP server, and what's possible with it?

The Stormboard MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Stormboard account. It provides structured and secure access so your agent can perform Stormboard operations on your behalf.

Supported Tools & Triggers

Tools
Accept a Storm InviteTool to accept a Storm invitation and join the Storm.
Add a Favorite StarTool to add a favorite star to a Storm on the Dashboard.
Check AuthenticationTool to verify API key authentication validity.
Close a StormTool to close an open Storm, making it read-only.
Create a Line ConnectorTool to create a line connector between two ideas.
Create a new chat messageTool to create a new chat message in a Stormboard storm.
Create a New StormTool to create a new Storm in Stormboard for interactive planning and collaboration.
Create a New TagTool to create a new tag in a Storm without any data related to Ideas.
Create a New UserTool to create a new user account in Stormboard.
Create an idea in StormboardTool to create a new idea in an existing Stormboard storm.
Create Tag Data for an IdeaTool to update tag data for an idea.
Decline a Storm InviteTool to decline a Storm invitation and remove it from your list.
Delete a Connector Between IdeasTool to delete a line connector between two ideas.
Delete a Specific ConnectorTool to delete a line connector using the connector ID.
Get Storm DetailsTool to retrieve detailed information about a specific Storm.
Duplicate a StormTool to duplicate an existing Storm.
Get a list of connectors in a StormTool to retrieve a list of connectors within a specific Storm.
Get a List of IdeasTool to retrieve all ideas from a Storm.
Get A List Of ParticipantsTool to retrieve a list of all participants in a Storm.
Get A List Of Storms InvitesTool to retrieve a list of storms that you have been invited to.
Get List of Tags in StormTool to retrieve the list of tags that have been created in a Storm.
Get A List Of Your StormsTool to retrieve a list of storms from Stormboard.
Get Authentication InfoTool to retrieve authentication information and API token for the authenticated user.
Get Chat MessagesTool to retrieve a list of chat messages from a Stormboard storm.
Get Idea DataTool to retrieve detailed data and metadata for a specific idea.
Get Info About Your UserTool to retrieve authenticated user profile information.
Get My Storm AccessTool to check if the authenticated user has access to a Storm and retrieve their permission level.
Get Storm TemplateTool to retrieve template data for a Storm including all sections and subsections.
Get Tag Data For An IdeaTool to retrieve tag data for a specific idea in Stormboard.
Get Unread Chat MessagesTool to retrieve unread chat messages from a specific Storm.
Invite Participants to StormTool to invite people to join a Storm by email.
Join a StormTool to join a Storm using its ID and access key.
Mark Chat Messages as ReadTool to mark all chat messages as read in a Storm.
Remove a Favorite StarTool to remove a favorite star from a Storm on the Dashboard.
Reopen a StormTool to reopen a closed Storm.
Update a Line ConnectorTool to update a specific line connector between two ideas.
Update NotificationsTool to update user notification preferences.
Update Section in StormTool to update a section's title, description, and/or character in a Storm.
Update Storm LegendTool to update the color labels of the legend for a storm.
Update Your ProfileTool to update your user profile information.
Verify Your AccountTool to verify a Stormboard account using a verification code.

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 Stormboard 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 Stormboard 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 Stormboard
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["stormboard"]
    )

    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 Stormboard
  • 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 Stormboard 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 Stormboard
  • 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 Stormboard 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 Stormboard
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["stormboard"]
    )

    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 Stormboard 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 Stormboard 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 Stormboard MCP Agent with another framework

FAQ

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

With a standalone Stormboard MCP server, the agents and LLMs can only access a fixed set of Stormboard tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Stormboard 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 Stormboard tools.

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

Yes, absolutely. You can configure which Stormboard 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 Stormboard 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.