How to Use the Flystack MCP in OpenAI Agents SDK

Q: How does the OpenAI Agents SDK handle Flystack API failures?

If checkapistatus returns an error or a timeout occurs, your agent catches the exception within its standard execution loop. You can write custom retry logic or halt the run before executing further diagnostic steps.

Audit your active clusters and track live performance metrics directly inside your OpenAI Agents SDK production loops.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Flystack MCP to OpenAI Agents SDK

Create your Vinkius account to connect Flystack to OpenAI Agents SDK and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Flystack with OpenAI Agents SDK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Real-time cluster telemetry

Stop guessing if your cluster is healthy; run `get_cluster_metrics` to grab memory usage and CPU load right when your agent detects an anomaly. It gives your Python code instant visibility without manual dashboard hopping. If the metrics point to a failing node, you can trigger downstream alerts. The agent checks `check_api_status` first to confirm the Flystack API itself isn't the bottleneck.

Deep deployment inspections in OpenAI Agents SDK

Run automated checks on your workloads using `list_flystack_deployments` to pull active environments. Once you spot a suspect service, use `get_deployment_details` to extract the exact configuration and replica count. This MCP Server feeds raw JSON payloads directly into your agent's context. Your code processes the infrastructure state, validates it against your safety guardrails, and flags mismatched configurations instantly.

Multi-agent infrastructure audits

Build specialized agents that pass tasks off to each other, using `list_flystack_clusters` to map your overall footprint. One agent can map the topology, while another inspects individual workloads. This setup keeps your system clean. By isolating the tools in a dedicated MCP connection, you ensure your production agents only access the specific read-only data they need to run diagnostics.

Setup guide

Set up Flystack MCP in OpenAI Agents SDK

Prerequisites

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

1

Install the SDK

Run pip install openai-agents to install the OpenAI Agents SDK. The MCP integration is built-in — no extra dependencies needed.
2

Connect via SSE transport

Use MCPServerSse with your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. The SDK auto-discovers all Flystack tools at runtime.
3

Create your Agent

Pass the MCP to Agent(mcp_servers=[server]). The agent receives Flystack tools as native definitions — JSON schemas resolve automatically.
4

Run the agent

Call Runner.run(agent, prompt) to execute. The agent invokes the appropriate Flystack tools and returns structured results. Copy the full example on the right to get started.

agent.py

import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerSse

async def main():
    async with MCPServerSse(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as server:
        agent = Agent(
            name="Flystack Agent",
            instructions="You have access to Flystack tools.",
            mcp_servers=[server],
        )
        result = await Runner.run(agent, "List recent transactions")
        print(result.final_output)

asyncio.run(main())

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 Flystack. 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 Flystack 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 Flystack MCP in OpenAI Agents SDK

Install the openai-agents package and initialize the MCPServerStreamableHttp client with your Vinkius endpoint. Pass the server instance inside the mcp_servers list when you instantiate your agent. The tools are discovered automatically.

Yes. You handle this on the Vinkius platform by configuring permissions for your endpoint token. Your agent will only see the tools you expose, like `list_flystack_deployments` or `check_api_status`.

If `check_api_status` returns an error or a timeout occurs, your agent catches the exception within its standard execution loop. You can write custom retry logic or halt the run before executing further diagnostic steps.

Yes. Set cacheToolsList to True in your SDK configuration. This prevents unnecessary round-trips to Vinkius to fetch the schema, saving latency on every agent run.

This integration only accesses read-only cluster metrics and deployment configurations. No database credentials, application secrets, or customer PII are ever touched. All data passes through ephemeral, zero-trust V8 sandboxes that wipe clean immediately.

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