tinder

This Tinder MCP server provides a standardized MCP interface to interact with the Tinder API. It handles authentication flows (SMS and Facebook), request transformation, rate limiting, caching, and consistent error handling, enabling clients to integrate with Tinder through familiar MCP endpoints. You can authenticate users, fetch profiles and recommendations, like or pass on users, send messages, and manage your cache and rate limits via the built-in MCP tools. The server exposes authentication endpoints, user endpoints, interaction endpoints, and a suite of MCP tools for operational tasks such as cache management and rate limit inspection. To get started, deploy the server, configure your environment variables, and then use the MCP tools and resources endpoints to perform common actions like authenticating a user or retrieving a user profile. The tools include actions like authenticate_sms, authenticate_facebook, get_user_profile, get_recommendations, like_user, and clear_cache, among others, all accessible through the /mcp/tools and /mcp/resources endpoints.

Prerequisites:

• Node.js (v14+ or as required by the project)
• npm or yarn
• A supported database/cache (e.g., Redis) if you plan to use caching

1. Clone the repository

git clone https://github.com/yourusername/tinder-api-mcp-server.git
cd tinder-api-mcp-server

2. Install dependencies

npm install

3. Create and configure environment variables

cp .env.example .env

Edit .env to set your credentials, API base URL, and secrets. Example variables include:

• PORT
• ENV
• TINDER_API_BASE_URL
• TINDER_CLIENT_ID
• TINDER_CLIENT_SECRET
• JWT_SECRET
• REDIS_URL
• CACHE_TTL_SECONDS
• SMS_AUTH_ENABLED
• FB_AUTH_ENABLED

4) Build and run

npm run build npm start

5) Optional: Run in development mode

npm run dev

Tips:

• Do not commit secrets; use environment variables or a secrets manager.
• Ensure HTTPS in production and secure storage for tokens.
• If you change authentication methods, update the env flags accordingly (SMS vs Facebook).
• For scaling, configure Redis as the cache backend and tune CACHE_TTL_SECONDS according to your traffic.
• Use the MCP tools (POST /mcp/tools) to run maintenance tasks like clear_cache or get_rate_limits for monitoring.
• Check /mcp/info for server health and basic metadata. Common issues:
• Missing environment variables leading to startup errors: verify .env is loaded and matches the required keys.
• Network/firewall blocks to Tinder API endpoints: ensure outbound access is allowed.
• Invalid or expired JWTs: rotate JWT_SECRET and ensure tokens are refreshed via the authentication endpoints.