Quidli Connect MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONNECT_API_KEY | No | Connect API key for higher limits, connect_me, and Smart Send tools. | |
| EVM_PRIVATE_KEY | No | Wallet private key for x402 pay-per-call authentication. Must have USDC on Base. | |
| CONNECT_API_BASE_URL | No | Base URL of the Connect API. | https://api.connect.quid.li |
| CONNECT_X402_EVM_NETWORK | No | EVM network ID for x402 (8453 for Base mainnet, 84532 for Base Sepolia). | 8453 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_get_priceA | Get public x402 list prices for lookup, scores, and agent (reference only; live paywall amounts are in 402 responses). |
| connect_lookupB | Resolve social identities to EVM and Solana wallet addresses. If status is processing, retry the same payload. |
| connect_lookup_exposedA | List platforms a recipient has exposed on Connect, with enriched profile, scores, and wallet addresses. May require x402 payment when the profile owner charges for lookups. |
| connect_scores_batchC | Batch scores for linked accounts or Connect usernames. Optional filter excludes users below minScore. |
| connect_scores_by_accountC | Scores for a linked social account or wallet. |
| connect_scores_by_usernameC | Scores by Connect public username. |
| connect_meA | Get the Connect profile, scores, and all linked accounts for the API key owner. Use to identify which user the key belongs to. |
| connect_dropA | Execute a Smart Send (batch token transfer). Returns 201 when submitted or 202 when recipients still processing — retry with same idempotencyKey. |
| connect_drop_balanceA | Get native and ERC-20 balances for the API key owner Smart Send embedded wallet on a chain. Use before connect_drop to verify gas and token funds. |
| connect_agent_promptA | Natural-language agent turn for Farcaster/Lens cohort discovery. Blocking up to 60s. Omit sessionId to start; include to continue. Do not send requester. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Tools are largely distinct, but the three score-related tools (connect_scores_batch, connect_scores_by_account, connect_scores_by_username) overlap in purpose, differing mainly by input type. This could cause misselection if an agent doesn't carefully read descriptions. Other tools have clearly separate functions.
Tool names consistently use the 'connect_' prefix and mostly follow a verb_noun pattern (e.g., get_price, lookup, scores_batch, drop_balance). However, 'connect_me' is a plain noun and 'connect_agent_prompt' is noun_noun, deviating slightly from the pattern without causing confusion.
With 10 tools, the server strikes a good balance—enough to cover identity resolution, scoring, token transfers, and agent interactions without overwhelming users. Each tool serves a clear purpose within the server's scope.
The tool set covers core workflows: resolving identities, retrieving scores via multiple input methods, checking balances, executing drops, and agent-driven discovery. No obvious gaps exist for the stated purpose; retries and idempotency are handled via documentation in descriptions.