MCP Chat Adapter

Created By
aiamblichusa year ago
MCP server for using OpenAI compatible chat endpoints
Overview

What is MCP Chat Adapter?

MCP Chat Adapter is a server that implements the Model Context Protocol (MCP) to provide a clean interface for language models to utilize chat completion capabilities through OpenAI-compatible APIs. It serves as a bridge between LLM clients and chat models, enabling seamless conversations while managing API interactions and conversation states.

How to use MCP Chat Adapter?

To use the MCP Chat Adapter, set up the required environment variables in your mcp.json file, including your OpenAI API key and the conversation directory. You can then create, manage, and interact with chat conversations using the provided tools.

Key features of MCP Chat Adapter?

  • Built with FastMCP for robust implementation
  • Tools for conversation management and chat completion
  • Error handling and timeouts
  • Conversation persistence with local storage
  • Minimal configuration for easy setup
  • Configurable model parameters
  • Compatibility with OpenAI and compatible APIs

Use cases of MCP Chat Adapter?

  1. Managing multiple chat conversations with language models.
  2. Integrating chat capabilities into applications using OpenAI APIs.
  3. Facilitating seamless user interactions with AI chatbots.

FAQ from MCP Chat Adapter?

  • What is the purpose of the MCP Chat Adapter?

It acts as a bridge for LLMs to interact with OpenAI's chat completion API, simplifying conversation management.

  • Is it necessary to set environment variables?

Yes, required environment variables must be set for the server to function properly.

  • Can I edit conversations manually?

Yes, conversations can be edited in the CONVERSATION_DIR, but the server needs to be restarted to see changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aiamblichus
Star
0
Language
TypeScript
License
MIT 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
Crevio

2 days ago