3,400+ MCP servers ready to use
Vinkius

OmniEngage MCP Server for OpenAI Agents SDKGive OpenAI Agents SDK instant access to 12 tools to Check Api Status, Create Prospect, Delete Prospect, and more

Built by Vinkius GDPR 12 Tools SDK

The OpenAI Agents SDK enables production-grade agent workflows in Python. Connect OmniEngage through Vinkius and your agents gain typed, auto-discovered tools with built-in guardrails. no manual schema definitions required.

Ask AI about this App Connector for OpenAI Agents SDK

The OmniEngage app connector for OpenAI Agents SDK is a standout in the Industry Titans category — giving your AI agent 12 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python
import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MCPServerStreamableHttp(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as mcp_server:

        agent = Agent(
            name="OmniEngage Assistant",
            instructions=(
                "You help users interact with OmniEngage. "
                "You have access to 12 tools."
            ),
            mcp_servers=[mcp_server],
        )

        result = await Runner.run(
            agent, "List all available tools from OmniEngage"
        )
        print(result.final_output)

asyncio.run(main())
OmniEngage
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About OmniEngage MCP Server

Connect your OmniEngage (Cynthia AI) account to any AI agent and take full control of your sales orchestration and prospect engagement through natural conversation. OmniEngage provides a powerful platform for automated LinkedIn and email outreach, and this integration allows you to retrieve prospect metadata, launch new research sequences, and monitor campaign performance directly from your chat interface.

The OpenAI Agents SDK auto-discovers all 12 tools from OmniEngage through native MCP integration. Build agents with built-in guardrails, tracing, and handoff patterns. chain multiple agents where one queries OmniEngage, another analyzes results, and a third generates reports, all orchestrated through Vinkius.

What you can do

  • Prospect & Lead Orchestration — List all managed prospects and retrieve detailed profile metadata programmatically to ensure your sales pipeline is always synchronized.
  • Campaign & Sequence Control — Launch new outreach campaigns and trigger research sequences for prospects directly from the AI interface to drive better lead qualification.
  • Engagement Intelligence — Access and monitor campaign results and retrieve detailed engagement metadata via natural language to maintain a high-fidelity interaction history.
  • Webhook & Automation Control — List and oversee your configured webhooks to ensure your sales workflows are always optimized using simple AI commands.
  • Operational Monitoring — Track system responses and manage prospect statuses to ensure your outreach strategy is always high-performing.

The OmniEngage MCP Server exposes 12 tools through the Vinkius. Connect it to OpenAI Agents SDK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 OmniEngage tools available for OpenAI Agents SDK

When OpenAI Agents SDK connects to OmniEngage through Vinkius, your AI agent gets direct access to every tool listed below — spanning prospecting, outreach-automation, lead-generation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

check_api_status

Verify API connectivity and account status

create_prospect

Pass data as a JSON string. Add a new prospect

delete_prospect

Remove a prospect from the system

get_campaign_details

Get details for a specific campaign

get_prospect_details

Get specific prospect details

launch_campaign

Pass data as a JSON string. Launch a new outreach campaign

list_outreach_campaigns

List all outreach campaigns

list_prospects

List all outreach prospects

list_sequences

List all outreach sequences

list_tags

List all prospect tags

list_webhooks

List configured synchronization webhooks

update_prospect

Update an existing prospect

Connect OmniEngage to OpenAI Agents SDK via MCP

Follow these steps to wire OmniEngage into OpenAI Agents SDK. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Install the SDK

Run pip install openai-agents in your Python environment
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Run the script

Save the code above and run it: python agent.py
04

Explore tools

The agent will automatically discover 12 tools from OmniEngage

Why Use OpenAI Agents SDK with the OmniEngage MCP Server

OpenAI Agents SDK provides unique advantages when paired with OmniEngage through the Model Context Protocol.

01

Native MCP integration via `MCPServerSse`, pass the URL and the SDK auto-discovers all tools with full type safety

02

Built-in guardrails, tracing, and handoff patterns let you build production-grade agents without reinventing safety infrastructure

03

Lightweight and composable: chain multiple agents and MCP servers in a single pipeline with minimal boilerplate

04

First-party OpenAI support ensures optimal compatibility with GPT models for tool calling and structured output

OmniEngage + OpenAI Agents SDK Use Cases

Practical scenarios where OpenAI Agents SDK combined with the OmniEngage MCP Server delivers measurable value.

01

Automated workflows: build agents that query OmniEngage, process the data, and trigger follow-up actions autonomously

02

Multi-agent orchestration: create specialist agents. one queries OmniEngage, another analyzes results, a third generates reports

03

Data enrichment pipelines: stream data through OmniEngage tools and transform it with OpenAI models in a single async loop

04

Customer support bots: agents query OmniEngage to resolve tickets, look up records, and update statuses without human intervention

Example Prompts for OmniEngage in OpenAI Agents SDK

Ready-to-use prompts you can give your OpenAI Agents SDK agent to start working with OmniEngage immediately.

01

"List all active prospects in OmniEngage."

02

"Show me details for campaign ID camp_291 including its performance stats."

03

"List all outreach sequences available in my account."

Troubleshooting OmniEngage MCP Server with OpenAI Agents SDK

Common issues when connecting OmniEngage to OpenAI Agents SDK through the Vinkius, and how to resolve them.

01

MCPServerStreamableHttp not found

Ensure you have the latest version: pip install --upgrade openai-agents
02

Agent not calling tools

Make sure your prompt explicitly references the task the tools can help with.

OmniEngage + OpenAI Agents SDK FAQ

Common questions about integrating OmniEngage MCP Server with OpenAI Agents SDK.

01

How does the OpenAI Agents SDK connect to MCP?

Use MCPServerSse(url=...) to create a server connection. The SDK auto-discovers all tools and makes them available to your agent with full type information.
02

Can I use multiple MCP servers in one agent?

Yes. Pass a list of MCPServerSse instances to the agent constructor. The agent can use tools from all connected servers within a single run.
03

Does the SDK support streaming responses?

Yes. The SDK supports SSE and Streamable HTTP transports, both of which work natively with Vinkius.