About gpt2099.nu
gpt2099 is a scriptable MCP client for Nushell that stores editable context threads in cross.stream. It is aimed at Nushell users who want to call LLMs from the terminal through one interface covering several providers.
Key features
- 01Single interface for multiple model providers
- 02Persistent, editable conversation threads
- 03Tool extension through connected MCP servers
- 04Document upload with content-type detection
- 05Event-driven processing built on cross.stream
Use cases
- 01Calling LLMs from a Nushell workflow
- 02Reviewing and editing the context window of a conversation
- 03Letting models work on local files through MCP servers
MCP support
gpt2099 acts as an MCP client that connects to MCP servers and uses the tools they provide within conversations.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEgpt2099 
A Nushell scriptable MCP client with editable context threads stored in cross.stream
Features
- Consistent API Across Models: Connect to Anthropic, Cerebras, Cohere, Gemini, and OpenAI through a single, simple interface. (Add providers easily.)
- Persistent, Editable Conversations: Conversation threads are saved across sessions. Review, edit, and control your own context window — no black-box history.
- Flexible Tool Integration: Connect to MCP servers to extend functionality.
gpt2099already rivals Claude Code for local file editing, but with full provider independence and deeper flexibility. - Document Support: Upload and reference documents (PDFs, images, text files) directly in conversations with automatic content-type detection and optional caching.
Built on cross.stream for event-driven processing, gpt2099
brings modern AI directly into your Nushell workflow — fully scriptable, fully inspectable, all in
the terminal.
https://github.com/user-attachments/assets/1254aaa1-2ca2-46b5-96e8-b5e466c735bd
"lady on the track" provided by mobygratis
Getting started
Step 1.
First, install and configure cross.stream. Once set up, you'll
have the full cross.stream ecosystem of tools for editing and
working with your context windows.
After this step you should be able to run:
"as easy as" | .append abc123
.last abc123 | .cas
Step 2.
It really is easy from here.
overlay use -pr ./gpt
Step 3.
Initialize the cross.stream command that performs the actual LLM call. This appends the command to
your event stream so later gpt invocations can use it:
gpt init
Step 4.
Enable your preferred provider. This stores the API key for later use:
gpt provider enable
Step 5.
Set up a milli alias for a lightweight model (try OpenAI's gpt-4.1-mini or Anthropic's
claude-3-5-haiku-20241022):
gpt provider ptr milli --set
Step 6.
Give it a spin:
"hola" | gpt -p milli
Documentation
- Commands Reference - Complete command syntax and options
- How-To Guides - Task-oriented workflows:
- Configure Providers - Set up AI providers and model aliases
- Work with Documents - Register and use documents in conversations
- Manage Conversations - Threading, bookmarking, and continuation
- Use MCP Servers - Extend functionality with external tools
- Generate Code Context - Create structured context from Git repositories
Reference Documentation
- Provider API - Technical specification for implementing providers
- Schemas - Complete data structure reference for all gpt2099 schemas
FAQ
- Why does the name include 2099? What else would you call the future?
Original intro
This is how the project looked, 4 hours into its inception:
https://github.com/user-attachments/assets/768cc655-a892-47cc-bf64-8b5f61c41f35
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.