OpenAI Integration with MCP Server

@Robinson777-prog

リポジトリ

基本情報

カテゴリ

AI とエージェント

トランスポート

stdio

作者

Robinson777-prog

OpenAI Integration with MCP Server について

4-openai-integration

OpenAI Integration with MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

OpenAI Integration with MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is OpenAI Integration with MCP?

This example demonstrates how to integrate the Model Context Protocol (MCP) with OpenAI’s API, allowing OpenAI to dynamically use tools exposed by an MCP server. It is intended for developers building AI‑powered applications that need to access backend knowledge bases or other tool‑based systems.

How to use OpenAI Integration with MCP?

Install the required dependencies, set your OpenAI API key in a .env file, and run the client with python client.py. The MCP server is automatically launched as a subprocess via stdio transport, so no separate server startup is needed. For a split client‑server architecture, switch to SSE transport as described in the documentation.

Key features of OpenAI Integration with MCP

Exposes a get_knowledge_base tool that retrieves Q&A pairs
Converts MCP tools to OpenAI’s function‑calling format
Handles tool selection, execution, and result integration automatically
Uses stdio transport for single‑process communication
Provides a standardized, secure bridge between AI and backend systems
Includes an example knowledge base of company policy Q&A

Use cases of OpenAI Integration with MCP

Empower OpenAI to answer employee questions by querying an internal knowledge base
Automate customer support by giving OpenAI access to a help‑desk tool database
Build AI assistants that retrieve dynamic data from any MCP‑compatible backend
Prototype and test MCP integrations with OpenAI before deploying to production

よくある質問

What transport does this example use?

It uses **stdio transport**, meaning the client and server run in the same process and the client launches the server as a subprocess. If you need separate applications (e.g., running the server on a different machine), use the **SSE (Server‑Sent Events) transport** instead.

How does OpenAI execute the tools?

OpenAI’s function‑calling mechanism works through four steps: the MCP client registers tools as OpenAI functions, OpenAI chooses which tool to use based on the query, the client executes the tool via MCP, and OpenAI incorporates the result into its final response.

What role does MCP play in this integration?

MCP acts as a standardized, secure bridge between AI models and your backend systems. It abstracts away backend complexity, provides a consistent interface for tool interactions, and lets you control exactly which tools and data are exposed.

What data does the example knowledge base contain?

It contains Q&A pairs about company policies stored in a JSON file (`data/kb.json`). The MCP server retrieves these pairs through the `get_knowledge_base` tool.

Do I need to run the MCP server separately?

No. With the stdio transport used here, the client automatically starts the server as a subprocess. For an SSE‑based setup, you would run the server independently.

「AI とエージェント」の他のコンテンツ

Simplepages

Build and edit landing pages and websites from your AI assistant, and pull how they are performing.

q-ring

I4cTime

Quantum-inspired keyring for AI coding agents. Secure secrets with superposition, entanglement, tunneling, and teleportation — CLI + 44 MCP tools.

Kourier

Kourier AI Inc.

Discover flat-rate DeepSeek plans, model limits, API-key instructions, and coding-client setup

OpenZiti / LLM-Gateway

openziti

NetFoundry LLM Gateway is an OpenAI-compatible API proxy that routes requests across multiple LLM providers using zero-trust networking. Zero trust LLM gateway. OpenAI-compatible proxy with semantic routing and load bala

strac-mcp-dlp

strac-io

Detect and redact PII, PHI, PCI and secrets — SSNs, credit cards, passports, API keys and cloud credentials — in text and in local files, using the Strac DLP API. Five tools: redact_text, detect_sensitive_data, detect_fi