Refresh List connects to Claude through a secure remote MCP connector. Discovery is public so Claude can find the service; account data and actions remain protected behind OAuth.
Step-by-step
1. Open Claude connectors
In Claude, open Settings → Connectors, or use the Add connectors option from a conversation. Search for Refresh List when it is available in the directory.
2. Choose Connect
Select Refresh List and begin the authorization flow. Sign in with the Refresh List account that owns the workspace you want Claude to use.
3. Review the permission boundary
Confirm the Refresh List workspace and the requested access. Claude can call the published MCP tools, while Refresh List continues to enforce workspace membership, role permissions, token expiry, and revocation.
4. Finish OAuth
Approve the connection and return to Claude. Tokens are issued for the connector session; never paste a Refresh List API key into Claude chat.
5. Test the connection
Ask Claude: “Check my Refresh List balance.” A successful connection returns your paid credits, trial allowance, pricing, and recent list status.
6. Start using the workflow
Try “Estimate verification cost for this list” or “Preflight this CSV.” For paid work, Claude will guide you to the quote and approval step before starting.
The official connection URL
The Refresh List remote MCP endpoint is https://refreshlist.net/api/mcp. It is safe to publish because the URL is only the service address; protected tool calls require a valid OAuth bearer token.
What data flows where
Claude sends only the content and arguments needed for a tool you ask it to run. Refresh List processes the request in the selected workspace. Account summaries and job status are bounded; raw stored result files remain available through authenticated Refresh List handoffs.
If the connection does not work
Disconnect and reconnect the connector, make sure the intended Refresh List workspace is selected, then ask Claude to check your balance again. If authorization has expired or been revoked, OAuth will request a fresh sign-in.
Security boundaries
The connector uses HTTPS, OAuth discovery, expiring access tokens, revocation, role checks, and server-side provider credentials. Do not publish access tokens, refresh tokens, API keys, or admin URLs.
Refresh List publishes its connector address for discovery, but every account action is authorized. Never share an access token, refresh token, API key, or payment credential.
Common questions
Is the MCP URL a secret?+
No. It is a public connector endpoint. The security boundary is OAuth token validation and workspace authorization, not URL obscurity.
Can I use Claude without a paid Refresh List balance?+
You can connect and use read-only account and estimate tools. A paid verification requires sufficient credits or an available trial allowance, plus approval.
Does connecting Claude expose my whole account?+
No. Access is tied to the selected workspace and the connector’s published tools. Refresh List still checks membership and permissions on every protected call.
Where can I read the technical API documentation?+
Read the public API documentation at /api-docs and the security boundary at /security.