-
Notifications
You must be signed in to change notification settings - Fork 47
Support Model Context Protocol (MCP) Plugins #127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Closed
History could perhaps be updated like this:
And the show history could look like this (with the new MCP persona):
|
Added Apify support here: ea8a9b3 |
Released 1.8.3 with support for Apify: https://github.com/kardolus/chatgpt-cli/releases/tag/v1.8.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
As a CLI user, I want to use MCP (Model Context Protocol) plugins like apify or smithery to pull external data and inject it into my conversation context — either as pre-query context or as part of a query — so that I can seamlessly enrich GPT responses with live, structured data.
Examples of Supported Usage
With multiple --param flags
With a single --param
With raw JSON via --params
Default version behavior (@latest is assumed if omitted)
This is equivalent to:
Handling MCP Replies
By default, responses from MCP plugins are injected into the current thread as user context.
Example
This performs the following:
1. Calls apify/weather@latest with the provided parameters
2. Receives a response such as:
"Current weather in Brooklyn is 65°F and cloudy."
3. Adds the following to thread history:
Dual Behavior
Context added from apify/weather@latest with parameters: location=Brooklyn
Configuration
Create a
SMITHERY_API_KEY
andAPIFY_API_KEY
configuration item.Feedback
Open to feedback on syntax, behavior, or other integrations you’d like to see.
The text was updated successfully, but these errors were encountered: