CrewAI agents can load tools from MCP servers, so a crew can use Reelspan's hosted MCP server to publish, schedule and read results. There is no separate Reelspan package to install.
Install
pip install crewai mcpAPI key
Create a key under Developers → API keys and export it, along with the key for the model your agents use. Start with a test key (rs_test_…): every check runs, but nothing is posted.
export REELSPAN_API_KEY=rs_test_...Example
This crew publishes a text post to the sandbox network, which needs no connected account, and then checks the result.
import os
from crewai import Agent, Crew, Task
from crewai.mcp import MCPServerHTTP
reelspan = MCPServerHTTP(
url="https://api.reelspan.com/mcp",
headers={"Authorization": f"Bearer {os.environ['REELSPAN_API_KEY']}"},
cache_tools_list=True,
)
publisher = Agent(
role="Social media publisher",
goal="Publish posts with Reelspan and confirm they went out",
backstory="You manage the brand's social accounts through Reelspan.",
mcps=[reelspan],
)
task = Task(
description="Publish 'Hello from my CrewAI agent' as a text post to the sandbox network for the profile my-brand, "
"then check its status.",
expected_output="The request_id and each network's result.",
agent=publisher,
)
print(Crew(agents=[publisher], tasks=[task]).kickoff())Replace my-brand with one of your profiles (the agent can find them with list_profiles).
Notes
- Posting runs in the background. The publish tools return a
request_id; the agent callsupload_statusto read each network's result. - Media goes in as URLs.
upload_videoandupload_photostake publichttpsURLs, not local files. - Scope the key. The agents can do whatever the key allows. A key with only Publish and Read can't create or delete profiles.
- Going live: swap the test key for a live one (
rs_live_…) and use real networks instead ofsandbox.
The full tool list is on the MCP server page. CrewAI's own guide: docs.crewai.com/en/mcp/overview.