Developer documentation

Human Kind MCP Server

Human Kind's content is queryable via the Model Context Protocol. Connect any MCP-compatible AI agent to this endpoint and query our articles, services, case studies, and company information directly.

Endpoint

POST https://thehumankind.co/api/mcp

The endpoint accepts MCP JSON-RPC 2.0 requests over HTTP. It is stateless; each request is handled independently. No authentication is required. CORS is open for cross-origin requests.

There is no rate limiting in place. This is a public, read-only endpoint serving pre-indexed content.

Quickstart: Claude Desktop

Add the following to your Claude Desktop configuration file. On macOS this is at ~/Library/Application\ Support/Claude/claude_desktop_config.json.

{
  "mcpServers": {
    "humankind": {
      "url": "https://thehumankind.co/api/mcp"
    }
  }
}

Restart Claude Desktop after saving. You will see Human Kind listed in the MCP servers panel. You can then ask Claude questions like:

Use the humankind server to tell me about their sustainability services
Search humankind for articles about Digital Product Passports
What case studies does Human Kind have?

Available tools

search_humankind

Search Human Kind's published content. Returns the most relevant results for a given query, ranked by relevance across title, description, and body text.

{
  "query": string,      // required: search term or question
  "type": string        // optional: filter by content type
                        // "post" | "service" | "case-study" | "page"
}

get_content

Retrieve a specific piece of content in full by its ID. Use search_humankind or list_content to discover IDs.

{
  "id": string          // required: content ID
                        // e.g. "post:mcp-framework"
                        //      "service:digital-product-ai"
                        //      "case-study:workhouse-ai-pilots"
}

list_content

List all available content, optionally filtered by type. Useful for discovery before searching or retrieving specific items.

{
  "type": string,       // optional: filter by content type
                        // "post" | "service" | "case-study" | "page"
  "limit": number       // optional: maximum items to return
}

Content schema

All content items share a common schema. The type field determines what additional fields are present.

{
  "id":          string,   // e.g. "post:mcp-framework"
  "type":        string,   // "post" | "service" | "case-study" | "page"
  "title":       string,
  "description": string,
  "url":         string,   // path, e.g. "/latest-thinking/mcp-framework/"
  "body":        string,   // full text content

  // Optional: populated on posts, may appear on other types:
  "category":    string,   // "AI for Humans" | "Insight" | "Opinion" | "Sustainability Decoded"
  "date":        string,   // ISO date string
  "tags":        string[]
}

Example requests

Initialize session

curl -X POST https://thehumankind.co/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "clientInfo": { "name": "my-agent", "version": "1.0.0" }
    }
  }'

Search content

curl -X POST https://thehumankind.co/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "search_humankind",
      "arguments": {
        "query": "Digital Product Passports automotive"
      }
    }
  }'

List all services

curl -X POST https://thehumankind.co/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "list_content",
      "arguments": { "type": "service" }
    }
  }'

Protocol reference

This server implements the Model Context Protocol specification version 2024-11-05. It uses a stateless HTTP transport; no session management is required between requests. Each tool call is independent.

Questions or integration issues? Get in touch or try the on-site demo to see it working.