How to Use the Google Pub/Sub Topic MCP in CrewAI

Enable specialized agent teams to perform complex, monitored actions using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Google Pub/Sub Topic MCP to CrewAI

Create your Vinkius account to connect Google Pub/Sub Topic 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 Google Pub/Sub Topic with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Agent Teams Publishing to the Google Pub/Sub Topic

You can assign an agent within your crew to handle external communications. By giving it access to this MCP Server, a specialized agent can execute `pubsub_publish_message` to send data to the Google Pub/Sub Topic. The resulting message acts as a trigger for other services, allowing your entire autonomous operation to react instantly to an event generated by one of your agents.

Monitoring Publishing Actions with CrewAI

Because you are using a multi-agent setup, visibility is key. When the publishing action occurs via `pubsub_publish_message`, the monitor agent sees the tool call and its successful result. This shared memory allows all agents to confirm that the necessary external event was successfully fired before moving to the next step in the process.

Autonomous Operations with MCP Server Integration

The `pubsub_publish_message` tool gives your crew a way to 'act' on the outside world. An agent can complete its research, and another agent immediately uses that result to publish an event. This creates true autonomous cycles: Agent A finishes -> publishes message -> Agent B picks up the event and analyzes it.

Setup guide

Set up Google Pub/Sub Topic 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 Google Pub/Sub Topic tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Google Pub/Sub Topic 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="Google Pub/Sub Topic Analyst",
        goal="Access and analyze Google Pub/Sub Topic data via MCP.",
        backstory="Expert analyst with direct Google Pub/Sub Topic access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Google Pub/Sub Topic 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 Google Pub/Sub Topic. 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 Google Pub/Sub Topic 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 Google Pub/Sub Topic MCP in CrewAI

You define an agent role responsible for external communication. That agent uses `pubsub_publish_message` to send the final output or status update to the topic, kicking off downstream processes.

Yes. A dedicated monitor agent can be tasked with periodically checking if an event related to a specific topic arrived. The publishing action guarantees the message hits the stream when needed.

The optimal setup involves having one agent perform the final data synthesis, and then passing that structured result to a second agent whose sole job is publishing via this MCP Server.

Yes. The tool output streams results back through the crew's shared memory, meaning all participating agents see the successful publication status in real-time as it happens.

It manages simple string payloads for the message body and requires a specific string identifying the target Google Pub/Sub Topic. The data is plain text only.

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