coinvest-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@coinvest-mcpshow my current portfolio"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
coinvest-mcp
A local MCP server that exposes Liquid Co-Invest's trading-data and order tools to a local LLM. It is a thin, generic proxy: it holds no hardcoded tools — on startup it fetches the tool catalog from your Liquid backend and forwards each call there. All reasoning happens in your local agent; Liquid executes the individual tool calls.
Backend dependency. This client talks to the Liquid Co-Invest backend
mcp_apiendpoints (GET /api/mcp/tools,POST /api/mcp/dispatch,GET /api/mcp/guide), which must be deployed and enabled for your user.
What it exposes
Whatever the backend registry advertises — market data, balances, portfolio analytics, order status, and trading (spot, perps, prediction markets, and batch orders, plus cancel / close / set leverage). Because the catalog is fetched live, adding or changing a tool on the backend needs no new release here.
It also exposes the authoritative operating guide as the
coinvest_operating_guide prompt, fetched live from the backend — load it
before driving the tools.
Related MCP server: QuantXData MCP Server
Install
First install uv — this is the only prerequisite.
The uvx command used below ships with uv (it's shorthand for uv tool run),
so there is nothing else to install:
# macOS / Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# or, with Homebrew
brew install uvThen install and run straight from the repo — no clone required. uvx fetches
the package from GitHub, builds it in an isolated environment (provisioning a
compatible Python automatically), and runs the coinvest-mcp entry point:
uvx --from git+https://github.com/liquid-public/coinvest-mcp.git coinvest-mcpThe server speaks MCP over stdio, so it's normally launched by your MCP client (see Connect your MCP client) rather than run interactively. The command above is the same one you put in the client config.
Pin to a branch or tag by appending @<ref>:
uvx --from git+https://github.com/liquid-public/coinvest-mcp.git@main coinvest-mcpTo install it once as a persistent tool on your PATH (so the command is just
coinvest-mcp), use uv tool instead:
uv tool install git+https://github.com/liquid-public/coinvest-mcp.git
uv tool upgrade coinvest-mcp # pull a newer version lateruvx caches the build. After the backend ships changes that only affect this
client, force a rebuild with
uvx --refresh --from git+https://github.com/liquid-public/coinvest-mcp.git coinvest-mcp.
Configuration
Var | Required | Description |
| yes | Base URL of the Co-Invest server, e.g. |
| yes | Your MCP token (generate/regenerate it in the Liquid web app) |
| no |
|
| no | HTTP timeout in seconds (default 30) |
The token can be generated from the Liquid web app (app.liquid.trade).
The token authenticates as you; every call is scoped to your account
server-side. One running server == one Liquid user. The token expires after a
period (default 30 days) of inactivity (it is refreshed on each use); once
expired, requests return 401 and you regenerate it from the Liquid web app.
Connect your MCP client
Point your MCP client at the same uvx command. The client launches the server
on demand and passes configuration through env.
Claude Code (CLI)
claude mcp add coinvest \
--env COINVEST_URL=https://coinvest.liquid.trade \
--env COINVEST_MCP_TOKEN=your-token-here \
-- uvx --from git+https://github.com/liquid-public/coinvest-mcp.git coinvest-mcpAdd --env COINVEST_READONLY=1 for a read-only setup.
Claude Desktop / generic MCP client (JSON)
{
"mcpServers": {
"coinvest": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/liquid-public/coinvest-mcp.git",
"coinvest-mcp"
],
"env": {
"COINVEST_URL": "https://coinvest.liquid.trade",
"COINVEST_MCP_TOKEN": "your-token-here"
}
}
}
}For a read-only setup, add "COINVEST_READONLY": "1" to env.
The client must be able to finduvx on its PATH. If it can't (common on
macOS GUI apps), use the absolute path from which uvx as command, e.g.
/opt/homebrew/bin/uvx.
Develop
Clone the repo for local development, then sync and test:
git clone https://github.com/liquid-public/coinvest-mcp.git
cd coinvest-mcp
uv sync
uv run pytestRun your local checkout directly (point the client at this command to test changes before pushing):
uv run --directory /path/to/coinvest-mcp coinvest-mcpSafety
The local agent owns risk. Liquid runs no server-side agent for these calls —
there is no automated margin management, invariant enforcement, or liveness
rescue behind them. See the coinvest_operating_guide prompt for the operating
contract.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceFastMCP server exposing brokerage and market tools (Angel One, Coinbase, News) via the Model Context Protocol, enabling portfolio queries and trade execution through natural language.Last updated1MIT
- Alicense-qualityDmaintenanceMCP server that exposes QuantXData's institutional crypto market data APIs to AI assistants, enabling natural language queries for trades, order books, OHLCV, options, and more across 120+ exchanges.Last updatedMIT
- Flicense-qualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.Last updated
- Alicense-qualityDmaintenanceMCP server for integrating FinanceMarker.ru with LLM agents, IDEs, n8n, and other MCP-compatible clients. It proxies the FinanceMarker REST API and exposes it as a set of MCP tools.Last updated4MIT
Related MCP Connectors
MCP server exposing the Backtest360 engine API as tools for AI agents.
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/liquid-public/coinvest-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server