Connect Anysite MCP Server to Claude Desktop using OAuth
The Anysite MCP Tool for Claude Desktop provides seamless integration between Claude Desktop and the Anysite API through the Model Context Protocol (MCP). This allows Claude to extract LinkedIn, Instagram, Reddit, and other social media data directly within your conversations using OAuth authentication.
Secure OAuth 2.0 authentication - no API keys stored locally
Built-in connector support with easy setup through Claude Desktop settings
Granular control over which tools Claude can access and when
Automatic tool updates without manual configuration changes
First, obtain your OAuth URL from the Anysite dashboard:
https://mcp.anysite.io/mcp (recommended for Claude Desktop)
https://mcp.anysite.io/mcpFor Claude Desktop, always use the OAuth URL (not Direct URL) for better security and automatic credential management.
Now configure the connector in Claude Desktop:
Fill in the connector details:
https://mcp.anysite.io/mcpExpand Advanced settings if needed (usually defaults are fine)
You'll see a warning: "⚠ Confirm that you trust this connector"
Click Add button to save the connector
Only add connectors from trusted sources. The Anysite MCP connector is safe and only accesses data through the Anysite API with your explicit permission.
After adding the connector, you need to establish the connection:
Complete the OAuth authorization process:
You'll see the "AUTHORIZE APPLICATION" screen
Review the information:
Note: "You can revoke access at any time from your account settings"
Click ALLOW ACCESS button to grant permission
Or click DENY if you changed your mind
After authorization, you'll be redirected back to Claude Desktop, and the connector will show as "Connected".
Required setting — without this, Claude may fail to find the right Anysite tools for your requests.
The Anysite MCP Server uses a meta-tool architecture with 5 universal tools (discover, execute, get_page, query_cache, export_data). The default "Load tools when needed" mode searches by tool name only and often fails to match generic names like discover to queries like "Find Dario Amodei on LinkedIn".
With "Tools already loaded", all 5 meta-tools and server instructions are always in Claude's context. Since there are only 5 tools (not 70+), the context overhead is minimal.
Configure which tools Claude can use and how:
Available Tools:
Permission Levels:
Start with "Always ask permission" for all tools until you're comfortable with how they work. Then switch frequently-used tools to "Allow unsupervised" for smoother workflows.
Test your MCP integration:
If everything is working correctly, Claude will either:
To disconnect the Anysite MCP connector:
To fully revoke access from Anysite side:
If you need to reconnect:
**Solutions:**
- Ensure your Anysite account is active with valid subscription
- Check your internet connection
- Try disconnecting and reconnecting the connector
- Clear Claude Desktop cache and restart the application
- Verify the OAuth URL is exactly: `https://mcp.anysite.io/mcp`
**Solutions:**
- Ensure you're logged in to your Anysite account in the browser
- Check if popup blockers are preventing the OAuth window
- Try using a different browser as default
- Clear browser cookies for anysite.io and retry
- Check if your firewall is blocking api.anysite.io
**Solutions:**
- Restart Claude Desktop completely
- Disconnect and reconnect the connector
- Check if your Anysite subscription includes the tools you need
- Verify tool toggles are enabled (switched on)
- Try asking Claude explicitly: "Show me all available MCP tools"
**Solutions:**
- Check API rate limits in your Anysite dashboard
- Verify your subscription is active and not expired
- Ensure you're providing valid input (e.g., correct LinkedIn URLs)
- Check if specific tools have permission set to "Disabled"
- Review error messages for specific guidance
**Solutions:**
- Change permission level from "Always ask permission" to "Allow unsupervised" for trusted tools
- Note: "Allow unsupervised" means Claude can use tools without asking each time
- You can always change permissions back if needed
**Solutions:**
- This is expected behavior - Anysite MCP is a custom connector
- "CUSTOM" label means it's not built-in to Claude Desktop
- This is completely normal and doesn't affect functionality
- Only add custom connectors from sources you trust
OAuth 2.0 ensures your API keys never touch your local machine. Authentication tokens are managed securely.
You can revoke Claude Desktop's access to Anysite at any time from your account settings.
All API requests are logged in your Anysite dashboard for transparency and monitoring.
Granular control over which tools Claude can use and whether approval is needed.
Start Restrictive: Begin with "Always ask permission" for all tools until you understand their behavior
Regular Reviews: Periodically review which tools are enabled and their permission levels
Monitor Usage: Check your Anysite dashboard regularly for API usage and quota
Secure Account: Use strong passwords and enable 2FA on your Anysite account
Test First: Try tools with sample data before using them on sensitive or production data
Update Regularly: Keep Claude Desktop updated to get the latest connector features
Document Workflows: Note which tools work best for your specific use cases
| Feature | Claude Desktop (OAuth) | Local Server |
|---|---|---|
| Setup Complexity | Easy (GUI-based) | Moderate (command line) |
| Authentication | OAuth 2.0 (secure) | Environment variables |
| Credentials | Managed automatically | Manual configuration |
| Tool Updates | Automatic | Requires git pull |
| Best For | General users, production | Developers, testing |
| Security | OAuth tokens | API keys in config |
| Revocation | One-click disconnect | Manual removal |
Contact our support team for assistance with Claude Desktop MCP integration