Turn any REST API into an MCP server in one command
About
Point mcpify at any OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf) can call — zero glue code, zero per-endpoint wrappers, always in sync with the spec. Supports GET/POST/PUT/PATCH/DELETE, auth headers, and both URL and local file specs.
Details
- Transport
- SSE
Explore
- Zero glue code or per‑endpoint wrappers
- Automatically stays in sync with the spec
- Supports all HTTP methods (GET, POST, PUT, PATCH, DELETE)
- Handles authentication headers
- Loads specs from URLs or local files
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Turn any REST API into an MCP server in one commandCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Point mcpify at any OpenAPI specification (via URL or local file) and run a single command. The generated MCP server exposes all endpoints as tools, supporting GET, POST, PUT, PATCH, DELETE, and authentication headers.
get_markets
Use this when the user asks which perpetual markets are tradable on MCPify (Hyperliquid), or for a market overview with prices, 24h change, volume, funding and max leverage.
get_price
Use this when the user asks the current price of a specific coin on Hyperliquid (mark price, 24h change, volume, funding).
get_orderbook
Use this when the user wants the live order book (bids/asks) for a Hyperliquid perp market.
get_candles
Use this when the user wants OHLCV candle history for a Hyperliquid perp market (for analysis or charting).
get_my_account
Use this when the user asks about THEIR MCPify account: balance, withdrawable, open positions with PnL and liquidation prices, and whether agent trading is armed.
get_my_open_orders
Use this when the user asks for their open/resting orders on Hyperliquid (including TP/SL trigger orders). Returns each order's oid for cancellation.
get_my_trade_history
Use this when the user asks for their recent fills/executions on Hyperliquid (live venue truth: price, size, fee, realized PnL).
get_my_order_records
Use this when the user asks what orders were placed through MCPify (our audit records, including which source placed them: web, mcp agent, admin) — successes and rejections alike.
preview_order
Use this BEFORE place_order whenever the user wants to open a position: it validates and sizes the order (fresh est. entry, size after rounding, est. liquidation, TP/SL sanity, MCP caps) WITHOUT placing anything, and shows a proposal card the user can confirm from. Read-only and always safe to call. If the user confirms, call place_order with the same arguments.
place_order
Use this when the user explicitly asks to open a perp position or place an order on Hyperliquid via MCPify. Real funds — ALWAYS call preview_order with the same arguments first, show the user the proposal, and get their explicit confirmation; place_order is refused unless a matching preview ran within the last 10 minutes. Requires Agent Trading enabled on the MCPify settings page.
close_position
Use this when the user asks to close (fully or partially) an open Hyperliquid position. Risk-reducing: works whenever agent trading is armed.
set_position_tp_sl
Use this when the user asks to set or update take-profit / stop-loss on an open Hyperliquid position. Replaces any existing TP/SL triggers for that coin.
cancel_order
Use this when the user asks to cancel a resting or trigger order by its oid (from get_my_open_orders).
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"turn any rest api into an mcp server in one command": {
"mcpify": {
"command": "mcpify",
"args": [
"https://your-api.com/openapi.json"
]
}
}
}
}McpServers
{
"mcpify": {
"command": "mcpify",
"args": [
"https://your-api.com/openapi.json"
]
}
}Point mcpify at any OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf) can call — zero glue code, zero per-endpoint wrappers, always in sync with the spec. Supports GET/POST/PUT/PATCH/DELETE, auth headers, and both URL and local file specs.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
