Use Gender-API directly inside AI tools

Our MCP Server lets MCP-compatible AI tools call Gender-API directly. That means your assistant can enrich first names, full names, email-derived names, and country-of-origin data through structured tool calls instead of prompt-only instructions.

The easiest setup is the hosted Streamable HTTP endpoint at https://mcp.gender-api.com.

Customers connect directly to the hosted MCP endpoint and authenticate with the same Gender-API bearer token they already use for the API.

What customers can do with it

Use live Gender-API data: Your AI tool can query live Gender-API results instead of inventing request formats or responses.
Reuse your existing token: The MCP server works with the same Gender-API bearer token you already use for the API.
Connect MCP-compatible clients: You can use it in Claude, Cursor, or your own MCP-compatible internal tools and agents that support hosted MCP URLs.
Keep billing simple: Normal Gender-API credit usage still applies, so there is no second billing system to learn.

Supported tools

Included MCP tools

query_first_name – Query likely gender by first name.
query_full_name – Query likely gender by full name.
query_email – Extract and enrich a name from an email address.
get_country_of_origin – Get likely countries of origin.
get_statistics – Check remaining credits and account statistics.

Hosted transport

Use the hosted Streamable HTTP endpoint at https://mcp.gender-api.com and authenticate with your existing Gender-API bearer token.

Real-world MCP use cases

Lead enrichment inside AI copilots

Let Claude, Cursor, or an internal sales agent look at a lead list, call Gender-API through MCP, and add likely first names, gender, and country-of-origin context before outreach.

CRM and support personalization

Your support assistant can inspect incoming email addresses, extract likely first names with `query_email`, and create more natural personalized draft replies for agents.

Spreadsheet cleanup and research agents

MCP-enabled data-cleaning agents can review CSV files or spreadsheets, standardize first-name columns, and enrich rows with Gender-API results without custom API code in every workflow.

Marketing automation and segmentation

Use MCP in campaign-building assistants to generate salutations, enrich contact data, and check remaining credits before launching a personalization workflow.

How customers can use it in their own tools

1. Use the hosted MCP endpoint

If your AI platform supports remote MCP, point it directly at the hosted endpoint below and authenticate with your normal Gender-API bearer token.

https://mcp.gender-api.com

2. Authenticate with your normal API token

Hosted MCP uses the same Gender-API token you already use for the API. Send it as a bearer token in the request headers.

Authorization: Bearer your-api-token

3. Call the included Gender-API tools

After the hosted MCP session is initialized, your client can call the built-in Gender-API tools for live enrichment and account checks.

query_first_name
query_full_name
query_email
get_country_of_origin
get_statistics

That keeps onboarding simple: one hosted endpoint, one bearer token, and one toolset for all supported MCP clients.

Example client configurations

Production SDK example

import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';

const transport = new StreamableHTTPClientTransport(new URL('https://mcp.gender-api.com'), {
  requestInit: {
    headers: {
      Authorization: 'Bearer your-api-token',
    },
  },
});

Production MCP client config pattern

{
  "mcpServers": {
    "gender-api": {
      "transport": "streamable-http",
      "url": "https://mcp.gender-api.com",
      "headers": {
        "Authorization": "Bearer your-api-token"
      }
    }
  }
}

Exact field names vary by client, but every hosted setup needs the same MCP URL and bearer token header.

Frequently Asked Questions

01

Does this use my normal Gender-API credits?

Yes. The MCP server is a thin integration layer over the existing Gender-API endpoints, so normal token permissions and credit usage still apply.

02

Can I use it in my own internal MCP tool?

Yes. If your tool supports hosted MCP, connect it to https://mcp.gender-api.com and send your Gender-API bearer token.

Hosted MCP Server