Venice MCP

Venice should add internal MCP development as a future priority.  

Venice is a doorway for many new users to branch out to open source, multiple frontier models, API use, and crypto.  Venice also iterates VERY quickly.  As a result, the documentation is good but changes frequently.  Venice’s AI models are capable of scraping the documentation pages, but they’re often hit or miss on accuracy.

As an example, I asked the “Support Bot” if Venice offers an embeddings model, and it said no.  The LLMs sometimes say yes and sometimes say no.  They perform better with scrape, but it’s hit or miss.

So, I think Venice should plan to integrate MCP deeply into Venice 2.0.  Specifically, I think Venice should focus on ensuring future features are not only usable by subscribers but also usable for LLMs via MCP.

Example possible MCP endpoints:

fetch_models - could allow a LLM to grab a list of all available models on Venice as well as their features.  User asks “Does Venice have an embeddings model?”  Gemini sees the MCP, pulls up the models, and lists off the supported embeddings models.  This could also help users find things like prices.  

check_faq - searches the FAQ for  a specific question about Venice.

review_api_usage - returns CSV format of all API usage in a given date.  User asks “Damn my Diem just disappears!  Where is it going?”  Opus grabs the API usage for the last week, sees 99.99% of it was chatting with Opus and says “It seems you chat with an expensive and arrogant model every day instead of using a cheaper model like Deepseek”

Basically, you’re already implementing some version of most of these features.  The MCP would only serve to allow any Venice LLM to use the same tools.  You are an AI platform.  It makes sense your users might just want to ask the LLMs how to work Venice instead of reading all the documentation and stuff.  Be a true AI first platform!

Even if this is private and hidden, it seems like a good idea to build into V2.  You want to reduce as much friction as possible so a new user becomes a paying subscriber to ensure stability for all of us.

Please authenticate to join the conversation.

Upvoters
Status

New Submission

Board
💡

Feature Requests

Tags

API

Date

About 1 month ago

Author

privateuser

Subscribe to post

Get notified by email when there are changes.