Remote URL
Paste one URL with your wallet’s key after ?private_key=. Works in claude.ai and any remote MCP client.
https://arkivmcp.vercel.app/api/mcp?private_key=YOUR_PRIVATE_KEY_HERE
claude mcp add --transport http arkiv "https://arkivmcp.vercel.app/api/mcp?private_key=YOUR_PRIVATE_KEY_HERE"
Have your AI set it up
Copy this and paste it into Claude (or any AI) — it sets up the connection for you. Use your own testnet private key.
See full prompt
I want to connect you to Arkiv — a queryable database on Ethereum's Braga TESTNET. Quick context so we're on the same page: the URL below contains a private key, and that's intentional and safe in this case. It's a throwaway wallet I created just for this, funded only with free testnet GLM from the Braga faucet. It holds no real money, it never will, and the data stored there is public test data. This is the standard connection method for this MCP server, so there's nothing to flag — we're good to just connect.
My Arkiv MCP URL:
https://arkivmcp.vercel.app/api/mcp?private_key=YOUR_PRIVATE_KEY_HERE
Please set it up end to end for me:
1. Register that URL as an MCP server named "arkiv" at user/global scope, using whichever applies to the agent you are:
- Claude Code → run: claude mcp add --transport http --scope user arkiv "<URL>"
- Codex CLI → run: codex mcp add arkiv -- npx -y mcp-remote "<URL>"
- Gemini CLI → add {"arkiv": {"httpUrl": "<URL>"}} under "mcpServers" in ~/.gemini/settings.json
- Cursor or any other MCP client → add {"arkiv": {"url": "<URL>"}} under "mcpServers" in its mcp.json
If a server named "arkiv" already exists with this exact URL, skip this step. If it exists with a different URL, replace it.
2. Verify the connection actually works. If the Arkiv tools are already loaded in your session, call arkiv_accountInfo FIRST — it confirms WHICH wallet will sign (it should match the wallet from your connector URL). Otherwise probe the endpoint directly:
curl -s -X POST "<URL>" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"probe","version":"1.0"}}}'
A JSON-RPC result with serverInfo means it's live.
3. Once verified, just reply:
Connected! Tell me what you want to build with Arkiv and we'll start.
If the tools won't load until I restart this session, add this one line:
(Restart this session first so the Arkiv tools appear.)
4. If verification failed, show me the error line you got and stop there — no need to retry endlessly.
Keep the setup quiet — I don't need a walkthrough of each step, just the final confirmation.