Nyne.ai MCP Server

Coverage

The hosted MCP exposes a curated subset of Nyne.ai workflows: people search, person enrichment, targeted lookup fields, person newsfeed, person Q&A, company search, and company enrichment. For the broader endpoint surface, point agents at the machine-readable docs first.

Available tools

Why use Nyne.ai MCP?

Integration guides

ChatGPT

1. Open ChatGPT and go to Settings → Connectors (custom connectors require Developer mode; Plus, Pro, Business, or Enterprise).
2. Click Add custom connector.
3. Enter the Nyne.ai MCP endpoint https://api.nyne.ai/mcp.
4. When prompted for authentication, choose OAuth (recommended). The flow uses:

   Authorization URL: https://api.nyne.ai/mcp/oauth/authorize
   Token URL: https://api.nyne.ai/mcp/oauth/token

5. ChatGPT handles Dynamic Client Registration and sends the public OAuth client_id during token and refresh requests.
6. OAuth returns short-lived access tokens plus rotating refresh tokens so ChatGPT can silently renew access without asking you to log in again.
7. Do not choose ChatGPT's Access token/API key Bearer option for Nyne API credentials. Nyne API credentials are a key/secret pair; ChatGPT's single Bearer field cannot send both values.
8. If OAuth is unavailable, select No authentication only for discovery. Tool execution requires OAuth or a client/proxy that can send X-API-Key and X-API-Secret headers.
9. Click Save. ChatGPT discovers Nyne.ai tools from the manifest.

Claude Desktop

1. Open or create the MCP configuration file at ~/.claude/mcp.json.
2. Add Nyne.ai to your configuration:

   {
     "mcpServers": {
       "nyne": {
         "url": "https://api.nyne.ai/mcp",
         "headers": {
           "X-API-Key": "your_nyne_api_key",
           "X-API-Secret": "your_nyne_api_secret"
         }
       }
     }
   }

3. Restart Claude Desktop. Nyne.ai tools are now available.

Other MCP clients

• Discovery endpoint: https://api.nyne.ai/.well-known/mcp
• MCP endpoint: https://api.nyne.ai/mcp
• OAuth authorization server metadata: https://api.nyne.ai/.well-known/oauth-authorization-server
• OAuth protected resource metadata: https://api.nyne.ai/.well-known/oauth-protected-resource
• Authentication: OAuth2 (recommended) via /mcp/oauth/authorize and /mcp/oauth/token; or the X-API-Key + X-API-Secret headers.

Pricing & usage

Nyne.ai MCP uses your existing subscription and credit balance. MCP tools use the same credit costs as the REST API.

Async processing & polling

MCP tools use the same async request pattern as the REST API. Your assistant handles the polling automatically - you just ask naturally.

# 1. Call an MCP tool with JSON-RPC
POST /mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "person_search",
    "arguments": { "query": "software engineers at Google", "limit": 1 }
  }
}

# Response content text contains JSON like:
{
  "request_id": "abc123...",
  "status": "pending",
  "endpoint": "person_search",
  "next_action": {
    "tool": "check_status",
    "args": { "request_id": "abc123...", "endpoint": "person_search" }
  }
}

# 2. Poll with check_status
POST /mcp
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "check_status",
    "arguments": { "request_id": "abc123...", "endpoint": "person_search" }
  }
}

# Response content while processing:
{ "status": "pending", "message": "Processing..." }

# Response content when complete:
{
  "status": "complete",
  "endpoint": "person_search",
  "request_id": "abc123...",
  "data": { "results": [] }
}

Status & result shapes

Use the MCP check_status tool for assistant workflows. Terminal success is complete in JSON-RPC MCP responses. The legacy GET /mcp/status route uses completed; both are terminal-success statuses.

Next steps