# Tinder Bio [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/pipeworx-io/mcp-tinder-bio  
**GitHub Stars:** 0  
**npm Downloads (last month):** 596  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tinder-bio

## Description
tinder-bio MCP — wraps StupidAPIs (requires X-API-Key)

## Tools
Capabilities this server exposes over MCP:

- **tinder_bio_generate** — Generate a dating profile bio. Red flags embedded at no extra charge.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "tinder-bio": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-tinder-bio"]
  }
}
```

## Documentation

## What the Tinder Bio MCP server does

The Tinder Bio MCP server exposes one pack-specific MCP tool: `tinder_bio_generate`. It generates a dating profile bio and includes red flags in the generated result at no additional charge, according to the project documentation.

The tool is provided through Pipeworx and can be used by an MCP-compatible client or called directly over HTTP. The repository also provides a local npm package for clients that launch MCP servers over standard input and output.

## How it works

The hosted option uses a streamable MCP endpoint at `https://gateway.pipeworx.io/tinder-bio/mcp`. Add that URL to an MCP client to expose the Tinder Bio tool. The same gateway also offers a full endpoint at `https://gateway.pipeworx.io/mcp`; the pack endpoint lists Tinder Bio tools directly, while both endpoints can access Pipeworx routing through the shared `ask_pipeworx` capability.

For clients or scripts that do not use MCP, send a JSON POST request to `https://gateway.pipeworx.io/v1/tools/tinder_bio_generate`. The documented example passes age, profession, personality, situation, gender, relationship preference, and energy. Tool metadata can be inspected with a GET request to the corresponding `/v1/tools/` URL.

## Setup and configuration

For a hosted connection, configure the MCP client with the gateway URL. The documentation states that the initial calls do not require an account.

For local use, configure the client to run `npx -y @pipeworx/mcp-tinder-bio`. This starts the package as a stdio MCP server. It does not require a Pipeworx account or a gateway round trip, and it exposes only the pack’s own tools.

A direct HTTP call requires `Content-Type: application/json` and a request body containing the tool arguments. No API key or other environment variable is documented for the hosted or local setup.

## Tools and capabilities

- `tinder_bio_generate`: Creates a dating profile bio from supplied profile details and includes red flags in the output.
- Pipeworx gateway connections also expose shared gateway tools, including `ask_pipeworx`, `discover_tools`, `search_within`, `remember`, and `recall`.
- `ask_pipeworx` can route a natural-language request across the wider Pipeworx catalog when using a gateway connection.

The standalone package does not include those shared gateway meta-tools. Its MCP methods are limited to the Tinder Bio pack.

## Limitations and notes

The project documentation describes the gateway as covering more than 1,684 live data sources, but this server’s own pack-specific functionality is the single bio-generation tool. The number of tools reported by a hosted `tools/list` call can therefore be larger because of shared gateway tools; the connection’s `initialize` response is the authoritative scope for that connection.

It also does not list any required environment variables. Choose the local stdio mode when you want only this pack’s tool, and the hosted mode when gateway routing is useful.

_Full upstream README: https://allmcps.com/mcp/tinder-bio/readme_