How to Use the Postscript MCP in CrewAI

Q: How do I configure CrewAI to use Postscript?

Pass the endpoint URL directly into your agent's mcps array. For granular control, use MCPServerHTTP to restrict which agent gets which tools.

Q: Can I restrict a CrewAI agent from creating Postscript campaigns via MCP?

Yes. Use a tool filter to only expose read-only tools like listcampaigns to your analysis agents. Keep write access strictly isolated.

Q: Do the agents share memory when querying SMS automations?

Yes. An agent calls listautomations and stores the active abandoned cart triggers in shared memory. The rest of the crew uses that context for subsequent tasks.

Deploy multi-agent CrewAI teams to monitor Postscript campaigns and manage SMS subscribers autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Postscript MCP to CrewAI

Create your Vinkius account to connect Postscript to CrewAI — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Postscript with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Monitor campaigns autonomously

The `list_campaigns` tool allows an analytical CrewAI agent to scan your recent SMS broadcasts via the MCP Server. The agent grabs the IDs and hands them off to a specialized reporting agent. That second agent uses the `get_campaign` tool to extract click-through rates and spend. This setup completely automates your morning marketing reports without a human pulling CSVs.

Enforce subscriber compliance

A compliance-focused agent runs the `get_subscriber` tool through this MCP integration to verify opt-in statuses across your database. It checks if users who texted STOP actually got removed. If it finds a discrepancy, the agent executes an `update_subscriber` call to fix the record immediately. An acquisition agent uses `create_subscriber` for new leads, knowing the moderator agent watches the logs.

Manage webhooks and infrastructure

The `list_webhooks` tool gives your technical agent visibility into active Postscript endpoints via MCP. It identifies duplicate listeners that cause double-sends. When the agent finds a broken connection, it triggers `delete_webhook` to clean it up. It then checks `get_account_info` to ensure the API limits are healthy before handing control back to the manager agent.

Setup guide

Set up Postscript MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Postscript tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Postscript Analyst",
    goal="Access and analyze Postscript data via MCP.",
    backstory="Expert analyst with direct Postscript access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Postscript transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Postscript Analyst",
        goal="Access and analyze Postscript data via MCP.",
        backstory="Expert analyst with direct Postscript access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Postscript transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Postscript. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Postscript now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Postscript MCP in CrewAI

Pass the endpoint URL directly into your agent's `mcps` array. For granular control, use `MCPServerHTTP` to restrict which agent gets which tools.

Yes. Use a tool filter to only expose read-only tools like `list_campaigns` to your analysis agents. Keep write access strictly isolated.

One agent identifies the necessary changes and passes the context to an execution agent. That agent calls `update_subscriber` to apply the new profile data.

Yes. An agent calls `list_automations` and stores the active abandoned cart triggers in shared memory. The rest of the crew uses that context for subsequent tasks.

The crew accesses full phone numbers, campaign engagement logs, and subscriber tags. Vinkius routes every request through a zero-trust architecture, ensuring this MCP Server never persists your marketing data across sessions.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript