The endpoint
https://vexthium.com/api/mcp
That single line is the setup. The server runs over HTTP and asks for no login. Your client loads the tool list from it and decides on its own when to call each tool.
| Client | Setup method | Sends an agent key |
|---|---|---|
| Claude Code | A single command | Yes |
| Claude | Settings, then a custom connector | No |
| ChatGPT | Settings, then a custom connector | No |
| Cursor | mcp.json | Yes |
| VS Code | mcp.json | Yes |
| Other MCP clients | Their remote server setting | When headers are supported |
Claude Code
claude mcp add --transport http vexthium https://vexthium.com/api/mcp
Inside Claude Code, run /mcp to check that vexthium shows as connected and to browse its tools.
Claude
Go to Claude's settings, find connectors, add a custom connector and paste the endpoint. Turn the connector on in any chat where you want it.
ChatGPT
Go to ChatGPT's settings, find connectors, add a custom connector and paste the endpoint. Your plan and workspace settings decide whether custom connectors are offered.
Cursor
{
"mcpServers": {
"vexthium": { "url": "https://vexthium.com/api/mcp" }
}
}VS Code
{
"servers": {
"vexthium": { "type": "http", "url": "https://vexthium.com/api/mcp" }
}
}Other MCP clients
Register the endpoint as a remote server using Streamable HTTP. Vexthium keeps no session state and handles each request by itself, so the client has nothing to track between calls. A client limited to local stdio servers can reach it through any stdio-to-HTTP bridge.
Writing your own client? The developer guide covers the wire format.
Adding an agent key
Agent keys are optional. A key lifts the rate limits and gives you usage per agent. Clients that send headers take it like this:
claude mcp add --transport http vexthium https://vexthium.com/api/mcp \ --header "Authorization: Bearer vxm_…"
{
"mcpServers": {
"vexthium": { "url": "https://vexthium.com/api/mcp", "headers": { "Authorization": "Bearer vxm_…" } }
}
}Make a key on the Agent keys page, which also prints these snippets with your key already in place.
Quick test
- Ask "Which block is Robinhood Chain on right now?" The client should call
get_network_infoand reply with chain ID 46630. - Ask "Which Vexthium tools can you use?" The reply should cover read, simulate, prepare and contract tools.
- If the reply comes without a tool call, ask the client to use Vexthium, or confirm the server is switched on for that chat.
Still stuck
See common fixes for an empty tool list, unauthorized errors and broken approval links.