Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @quidli/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add quidli-connect-mcp -- npx -y @quidli/connect-mcp@0.6.24Execute em um terminal.
{ "mcpServers": { "quidli-connect-mcp": { "command": "npx", "args": [ "-y", "@quidli/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirOpen payments for multiplayer agents, powered by onchain reputation. Resolve a social handle to a wallet, check its onchain reputation, and send tokens — from Cursor, Claude Desktop, Claude Code, or any MCP-compatible client.
Multiplayer means parties who don't already know each other — an agent paying a person, or another agent, with no prior relationship and no account to fall back on. Connect is how it verifies who it's dealing with before sending anything.
Public repository: github.com/Quidli/connect-mcp
No API key required.
Claude Code:
claude mcp add --transport http quidli https://mcp.connect.quid.li/
Cursor: Add to Cursor (or paste that link into Settings → MCP → Add new MCP server)
Claude Desktop: Settings → Connectors → Add custom connector, URL https://mcp.connect.quid.li
Local (any client) — runs on your machine instead of the hosted endpoint:
npx -y @quidli/connect-mcp
See Choose how to connect below for API keys, x402 wallet pay-per-call, and full config snippets.
Then ask your agent:
Resolve the GitHub handle
justinquidlito a wallet.
{
"status": "completed",
"results": [
{
"type": "github",
"value": "justinquidli",
"ethWalletAddress": "0x6a48ADE3bE3F9f0b8B4c9af61Bb654A219311699",
"solWalletAddress": "8vo1awED98mwqDa4qR9JyMsk7qJYiwnTSG4EnXGyWXRh"
}
]
}
Resolves across GitHub, X, Telegram, Discord, LinkedIn, Farcaster, email and phone — and generates a wallet for people who have never used Quidli.
Then score what you find: connect_scores_batch returns onchain reputation for a batch of identities.
Lookup, scores, and price run without a key under a shared anonymous quota. Add a Connect API key for higher limits, your own profile (connect_me), and Smart Send.
Get a Connect API key at connect.quid.li → Enable API access for higher limits, connect_me, and Smart Send.
Zero local setup. Lookup, scores, agent, and price work without an API key (shared anonymous quota). Add a key for higher limits, your profile (connect_me), and Smart Send.
If you already have other MCP servers: skip the deeplink and add manually — the one-click install can overwrite your entire mcp.json in some Cursor versions.
Add to Cursor
Or paste into Cursor Settings → MCP → Add new MCP server:
cursor://anysphere.cursor-deeplink/mcp/install?name=quidli-connect&config=eyJ1cmwiOiJodHRwczovL21jcC5jb25uZWN0LnF1aWQubGkifQ==
Merge this into ~/.cursor/mcp.json (global) or .cursor/mcp.json (project) under mcpServers — do not replace your existing entries:
"quidli-connect": {
"url": "https://mcp.connect.quid.li"
}
Optional — higher limits and Smart Send:
"quidli-connect": {
"url": "https://mcp.connect.quid.li",
"headers": {
"x-api-key": "<your-connect-api-key>"
}
}
https://mcp.connect.quid.li. Optionally set header x-api-key: <your-connect-api-key>.Or merge this into your config file and restart Claude:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"quidli-connect": {
"url": "https://mcp.connect.quid.li"
}
}
}
If your Claude version does not support remote url connectors, use the local bridge instead (still hosted API, runs a small local helper):
{
"mcpServers": {
"quidli-connect": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"--http",
"https://mcp.connect.quid.li"
]
}
}
}
Requires Node.js 20+ for the bridge. Restart Claude Desktop after saving. You should see a hammer icon in the chat input when tools are available.
Without a key, initialize / tools/list always succeed. Anonymous tools/call share a global quota (HTTP 429 when exceeded — get a key for higher limits). Placeholder keys still return 401.
https://mcp.connect.quid.liThis gives Grok access to the anonymous-tier tools -- lookup, scores, agent, and price -- under the shared quota.
Current limitation: Grok's custom connector UI does not currently support attaching an API key or custom header. That means connect_me, connect_drop, and connect_drop_balance (all API key only) are not usable through Grok yet -- calls to them will return an unauthorized error. This isn't a connect-mcp limitation; it's Grok's custom-connector setup not exposing an auth field at this time.
If you already use Smithery, it will handle auth and sessions for you. Requires a Smithery account.
npx smithery login
npx smithery mcp add quidli/connect
Best if you want pay-per-call with a wallet, or prefer credentials in a local env file.
Requires Node.js 20+.
Add one of the following to .cursor/mcp.json (project) or your global MCP settings.
Same billing model as hosted; credentials stay on your machine.
{
"mcpServers": {
"quidli-connect": {
"command": "npx",
"args": ["-y", "@quidli/connect-mcp"],
"env": {
"CONNECT_API_KEY": "<your-connect-api-key>",
"CONNECT_API_BASE_URL": "https://api.connect.quid.li"
}
}
}
}
No API key. Authenticated calls pay automatically when the API returns HTTP 402. Your wallet private key is only read by the local process.
{
"mcpServers": {
"quidli-connect": {
"command": "npx",
"args": ["-y", "@quidli/connect-mcp"],
"env": {
"EVM_PRIVATE_KEY": "0x<wallet-with-usdc-on-base>",
"CONNECT_API_BASE_URL": "https://api.connect.quid.li",
"CONNECT_X402_EVM_NETWORK": "8453"
}
}
}
}
Use 84532 for Base Sepolia when pointing at a staging API.
The MCP process starts without CONNECT_API_KEY or EVM_PRIVATE_KEY. connect_lookup, connect_scores_*, connect_get_price, and connect_get_chains call the API without auth. That succeeds when x402 is disabled (price 0, typical for local). On production with x402 enabled, those tools return HTTP 402 until you set a key or wallet.
connect_me, connect_drop, and connect_drop_balance still require CONNECT_API_KEY.
{
"mcpServers": {
"quidli-connect": {
"command": "npx",
"args": ["-y", "@quidli/connect-mcp"],
"env": {
"CONNECT_API_BASE_URL": "http://127.0.0.1:3011"
}
}
}
}
mcpServers in:~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"quidli-connect": {
"command": "npx",
"args": ["-y", "@quidli/connect-mcp"],
"env": {
"CONNECT_API_KEY": "<your-connect-api-key>",
"CONNECT_API_BASE_URL": "https://api.connect.quid.li"
}
}
}
}
{
"mcpServers": {
"quidli-connect": {
"command": "npx",
"args": ["-y", "@quidli/connect-mcp"],
"env": {
"EVM_PRIVATE_KEY": "0x<wallet-with-usdc-on-base>",
"CONNECT_API_BASE_URL": "https://api.connect.quid.li",
"CONNECT_X402_EVM_NETWORK": "8453"
}
}
}
}
If both CONNECT_API_KEY and EVM_PRIVATE_KEY are set, the API key is used.
Credentials are optional in local mode. Without either variable, lookup/scores still work when the API does not charge x402. connect_me and Smart Send tools require CONNECT_API_KEY.
npx hangs with no output when run from a background serviceIf you're launching @quidli/connect-mcp via npx from inside a background
process manager -- a macOS launchd agent, a systemd unit, a supervisor, or
any client config running without a normal interactive shell -- it can hang
indefinitely with zero output and no error. This isn't a crash; npx is
stuck resolving PATH in an environment that doesn't provide the same shell
initialization an interactive terminal gets.
Workaround: if you have Bun installed, use bunx
instead of npx. It performs the same job -- running the package without a
local install -- but doesn't hit this hang in restricted-PATH environments.
{
"mcpServers": {
"quidli-connect": {
"command": "bunx",
"args": ["-y", "@quidli/connect-mcp"],
"env": {
"CONNECT_API_KEY": "your-api-key"
}
}
}
}
If you're spawning the process yourself (rather than through a client's MCP
config) and want to be resilient to bunx not being on PATH either,
resolve it by absolute path first:
import { spawn } from "node:child_process";
import { existsSync } from "node:fs";
import { homedir } from "node:os";
import { join } from "node:path";
const BUNX_PATH = (() => {
const candidate = join(homedir(), ".bun", "bin", "bunx");
return existsSync(candidate) ? candidate : "bunx";
})();
const proc = spawn(BUNX_PATH, ["-y", "@quidli/connect-mcp"], {
stdio: ["pipe", "pipe", "pipe"],
});
This isn't a general claim that Bun is better than npm -- it's a targeted fix
for one specific, reproducible failure mode when npx is spawned outside an
interactive shell.
Double-check you're setting CONNECT_API_KEY, not API_KEY -- the server
only reads CONNECT_API_KEY, and a mismatch here fails silently: your calls
will run in anonymous/unauthenticated mode instead of erroring, which can
look like a working-but-oddly-limited connection rather than a config
mistake.
connect_get_chains (REST: GET /chains) is the source of truth and needs no key. As of 2026-10-14 it lists these mainnets, each with lookup and drop enabled:
World Chain Sepolia (4801) is also listed, as a testnet.
ethWalletAddress, Solana pays their solWalletAddress.connect_drop sends native tokens when tokenContract is omitted. For an ERC-20 or SPL token you pass its contract address or mint.connect_drop_balance returns the native balance everywhere. ERC-20 balances come from a per-chain provider: Moralis on Monad and Base, Blockscout on Robinhood Chain, and other chains may return only native plus featured tokens. Zero balances are omitted, spam tokens can appear, and a token the provider doesn't index can be missing. If you know its contract address you can still send it by passing tokenContract.Ask your client to use these tools when you need Connect data or actions.
This repository is a read-only mirror, regenerated on every release — changes committed here are overwritten. Please open an issue rather than a pull request. See CONTRIBUTING.md.
Wallet lookup and onchain reputation for multiplayer agents. Resolve a social handle - X, Telegram, Discord - to an EVM or Solana wallet, send agent payments in any ERC-20, SPL, NFT or native token, a
{ "mcpServers": { "quidli-connect-mcp": { "command": "npx", "args": [ "-y", "@quidli/[email protected]" ] } }}Visão geral
Wallet lookup and onchain reputation for multiplayer agents. Resolve a social handle - X, Telegram, Discord - to an EVM or Solana wallet, send agent payments in any ERC-20, SPL, NFT or native token, and build trust graphs from EAS attestations.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@quidli/connect roda localmente via stdio.
Última verificação: 2026-11-16. Wallet lookup and onchain reputation for multiplayer agents. Resolve a social handle - X, Telegram, Discord - to an EVM or Solana wallet, send agent payments in any ERC-20, SPL, NFT or native token, and build trust graphs from EAS attestations.