MCP pour OpenAI et Claude

Created By
Spysailora year ago
Implementation of OpenAI MCP Server
Overview

What is MCP for OpenAI and Claude?

MCP for OpenAI and Claude is a simple server that acts as a Master Control Program (MCP) to interact with AI models from OpenAI and Anthropic (Claude).

How to use MCP?

To use MCP, clone the repository, install the dependencies, configure your API keys in the .env file, and start the server. Access it via http://localhost:3000.

Key features of MCP?

  • Unified API endpoint that automatically detects the provider based on the requested model.
  • Supports multiple AI models from OpenAI and Claude.
  • Simple web interface for testing the MCP.

Use cases of MCP?

  1. Interacting with OpenAI's GPT models for various applications.
  2. Utilizing Claude's models for AI-driven tasks.
  3. Testing and developing AI applications with a unified interface.

FAQ from MCP?

  • What models are supported?

MCP supports various models from OpenAI (like gpt-4, gpt-3.5-turbo) and Claude (like claude-3-opus).

  • How do I configure my API keys?

Edit the .env file to add your OpenAI and Claude API keys.

  • Is there a web interface for testing?

Yes! A simple web interface is included for testing the MCP.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Spysailor
Star
0
Language
HTML
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago