
Convexity Mcp
io.github.bayesian-energyPublished by GitHub account bayesian-energyv0.6.0Updated Oct 25, 2026
Build, edit, solve and analyse Convexity energy-system models from any MCP client; drives the app.
Overview
A local MCP server that lets an assistant build, edit, solve and analyse Convexity energy-system models by driving the Convexity desktop app.
- What you can do
- Build and edit Convexity energy-system models from an MCP client, with the server driving the app on the user's machine. Solve models, including cloud solves when an API key is supplied. Read and analyse existing models without needing a key.
- When to use it
- Useful when you work with Convexity energy-system models and want an assistant to help construct, modify, solve or analyse them instead of doing it by hand in the app.
- Requirements
- Runs as a local stdio process on the user's machine, installed from the npm package convexity-mcp, so Node.js is needed. It drives the Convexity desktop app, which must be present. An optional CONVEXITY_API_KEY (a cxk_ key from a Convexity account) keeps editing enabled past the 14-day trial and enables cloud solves; reading never needs it.
Installation
In SourceWeft
- Open Convexity Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.6.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.