Skip to main content
Glama
dvvolkovv

Human Design MCP Server

by dvvolkovv
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Human Design MCP Server

MCP Server для расчета карты Human Design по дате, времени и месту рождения. Совместим с n8n и другими системами, поддерживающими Model Context Protocol.

Описание

Этот сервер предоставляет инструменты для расчета Human Design карты, включая:

  • Определение типа (Manifestor, Generator, Manifesting Generator, Projector, Reflector)

  • Вычисление стратегии и авторитета

  • Расчет профиля

  • Определение активных ворот (gates) и их линий

  • Определение определенных центров

  • Расчет Incarnation Cross

Related MCP server: Swiss Ephemeris MCP Server

Установка

Требования

  • Node.js >= 18.0.0

  • npm или yarn

Установка зависимостей

cd human_design
npm install

Сборка

npm run build

Использование

Запуск сервера

HTTP Server (для Railway/n8n):

npm start

MCP Server (через stdio):

npm run start:mcp

📚 Сервер использует Swiss Ephemeris для точных расчетов

HTTP сервер работает на порту 3000 (или PORT из env) и готов принимать запросы.

Инструменты сервера

1. calculate_human_design

Рассчитывает полную карту Human Design.

Параметры:

  • birthDate (string, обязательный): Дата рождения в формате YYYY-MM-DD

  • birthTime (string, обязательный): Время рождения в формате HH:MM

  • birthLocation (string, обязательный): Место рождения (город, страна)

  • latitude (number, опциональный): Широта места рождения

  • longitude (number, опциональный): Долгота места рождения

Пример запроса:

{
  "name": "calculate_human_design",
  "arguments": {
    "birthDate": "1990-05-15",
    "birthTime": "14:30",
    "birthLocation": "Москва, Россия",
    "latitude": 55.7558,
    "longitude": 37.6173
  }
}

Пример ответа:

{
  "birthDate": "1990-05-15",
  "birthTime": "14:30",
  "birthLocation": "Москва, Россия",
  "type": {
    "name": "Generator",
    "description": "Генератор"
  },
  "strategy": "Отвечать",
  "authority": {
    "name": "Sacral",
    "description": "Сакральная авторитет"
  },
  "profile": {
    "number": "3/5",
    "description": "Профиль 3/5"
  },
  "gates": [
    {
      "number": 19,
      "name": "Approach",
      "line": 2,
      "planet": "Sun"
    },
    {
      "number": 49,
      "name": "Revolution",
      "line": 4,
      "planet": "Earth"
    }
  ],
  "definedCenters": [
    {
      "number": 2,
      "name": "Sacral Center"
    }
  ],
  "incarnationCross": {
    "sunGate": 19,
    "earthGate": 19,
    "cross": "Cross of 19 / 19"
  }
}

2. get_human_design_definition

Получить определения и значения компонентов Human Design.

Параметры:

  • component (string, обязательный): Компонент для определения

    • type - Типы Human Design

    • authority - Авторитеты

    • profile - Профили

    • gates - Ворота

    • channels - Каналы

    • centers - Центры

Пример запроса:

{
  "name": "get_human_design_definition",
  "arguments": {
    "component": "type"
  }
}

Интеграция с n8n

Метод 1: Использование HTTP Request Node

Создайте веб-обертку для MCP сервера:

// wrapper-server.js
import express from 'express';
import { spawn } from 'child_process';
import readline from 'readline';

const app = express();
app.use(express.json());

app.post('/calculate', async (req, res) => {
  const mcpServer = spawn('node', ['index.js']);
  
  const rl = readline.createInterface({
    input: mcpServer.stdout,
    output: mcpServer.stdin,
  });
  
  // Отправка MCP запроса
  const request = {
    jsonrpc: '2.0',
    id: 1,
    method: 'tools/call',
    params: {
      name: 'calculate_human_design',
      arguments: req.body,
    },
  };
  
  mcpServer.stdin.write(JSON.stringify(request) + '\n');
  
  // Чтение ответа
  rl.once('line', (response) => {
    const result = JSON.parse(response);
    res.json(result.result);
  });
});

app.listen(3000, () => {
  console.log('MCP wrapper server running on port 3000');
});

Затем используйте в n8n HTTP Request Node:

  • Method: POST

  • URL: http://localhost:3000/calculate

  • Body: {"birthDate": "...", "birthTime": "...", "birthLocation": "..."}

Метод 2: Использование Function Node в n8n

В n8n используйте Function Node с прямым вызовом модуля:

const { calculateHumanDesign } = require('/path/to/human_design/src/calculations.js');

// Получить данные из предыдущего узла
const birthDate = $input.item.json.birthDate;
const birthTime = $input.item.json.birthTime;
const birthLocation = $input.item.json.birthLocation;

// Рассчитать Human Design
const result = await calculateHumanDesign({
  birthDate,
  birthTime,
  birthLocation,
});

return {
  json: {
    ...result,
    timestamp: new Date().toISOString(),
  }
};

Метод 3: Использование Sub-workflow

Создайте отдельный workflow в n8n:

  1. Webhook Trigger для входящих запросов

  2. Function Node с расчетом Human Design

  3. HTTP Response Node для отправки результата

workflow-json:

{
  "name": "Human Design Calculator",
  "nodes": [
    {
      "parameters": {},
      "name": "Webhook",
      "type": "n8n-nodes-base.webhook",
      "position": [250, 300]
    },
    {
      "parameters": {
        "jsCode": "const { calculateHumanDesign } = require('/path/to/human_design/src/calculations.js');\n\nconst result = await calculateHumanDesign({\n  birthDate: $input.item.json.birthDate,\n  birthTime: $input.item.json.birthTime,\n  birthLocation: $input.item.json.birthLocation,\n});\n\nreturn { json: result };"
      },
      "name": "Calculate HD",
      "type": "n8n-nodes-base.function",
      "position": [450, 300]
    },
    {
      "parameters": {},
      "name": "Respond to Webhook",
      "type": "n8n-nodes-base.respondToWebhook",
      "position": [650, 300]
    }
  ],
  "connections": {
    "Webhook": { "main": [[{ "node": "Calculate HD", "type": "main", "index": 0 }]] },
    "Calculate HD": { "main": [[{ "node": "Respond to Webhook", "type": "main", "index": 0 }]] }
  }
}

Интеграция с другими системами

Claude Desktop

Добавьте сервер в конфигурацию Claude Desktop:

{
  "mcpServers": {
    "human-design": {
      "command": "node",
      "args": ["/absolute/path/to/human_design/index.js"]
    }
  }
}

Custom MCP Client

Пример использования в Node.js:

import { spawn } from 'child_process';
import readline from 'readline';

const mcpServer = spawn('node', ['index.js']);

const rl = readline.createInterface({
  input: mcpServer.stdout,
  output: mcpServer.stdin,
});

async function calculateHumanDesign(birthDate, birthTime, birthLocation) {
  const request = {
    jsonrpc: '2.0',
    id: 1,
    method: 'tools/call',
    params: {
      name: 'calculate_human_design',
      arguments: {
        birthDate,
        birthTime,
        birthLocation,
      },
    },
  };
  
  mcpServer.stdin.write(JSON.stringify(request) + '\n');
  
  return new Promise((resolve, reject) => {
    rl.once('line', (response) => {
      const result = JSON.parse(response);
      if (result.error) {
        reject(new Error(result.error.message));
      } else {
        resolve(result.result);
      }
    });
  });
}

// Использование
const result = await calculateHumanDesign('1990-05-15', '14:30', 'Москва, Россия');
console.log(result);

Структура проекта

human_design/
├── http-server.js              # HTTP Server для Railway/n8n
├── index-with-swiss.js         # MCP Server через stdio
├── package.json                # Зависимости проекта
├── README.md                   # Документация
├── QUICKSTART.md              # Быстрый старт
├── RAILWAY_DEPLOY.md          # Инструкция по деплою на Railway
├── N8N_SETUP.md              # Интеграция с n8n
└── src/
    └── calculations-cjs.cjs   # Расчеты Human Design (Swiss Ephemeris)

Разработка

Запуск в режиме разработки

npm run dev

Сервер будет перезагружаться автоматически при изменении файлов.

Тестирование

Для тестирования отправьте MCP запрос:

echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}' | node index.js

Лицензия

MIT

Поддержка

Для вопросов и предложений создайте issue в репозитории проекта.

Примечания

  • Human Design использует тропический зодиак (не сидерический, как в ведической астрологии)

  • Расчеты основаны на Swiss Ephemeris для точности позиций планет

  • Проект использует только Swiss Ephemeris версию с точными расчетами

  • Требуется компиляция нативных модулей при установке

Требования для установки Swiss Ephemeris

Для компиляции Swiss Ephemeris требуются build tools:

macOS:

xcode-select --install

Ubuntu/Debian:

sudo apt-get update
sudo apt-get install build-essential python3

Windows: Установите Visual Studio Build Tools

См. SWISS_EPHEMERIS.md для детальной информации о установке.

Available Tools

2 tools
calculate_human_designC

Рассчитывает карту Human Design по дате, времени и месту рождения

ParametersJSON Schema
NameRequiredDescriptionDefault
birthDateYesДата рождения в формате YYYY-MM-DD
birthTimeYesВремя рождения в формате HH:MM
birthLocationYesМесто рождения (город, страна)
latitudeNoШирота места рождения
longitudeNoДолгота места рождения

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool calculates a Human Design chart but doesn't describe what the output includes (e.g., chart components, format), error handling, performance characteristics, or any side effects. For a calculation tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Russian that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and parameters, making it easy to understand quickly. Every part of the sentence contributes essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of calculating a Human Design chart, the description is incomplete. There is no output schema, so the description should ideally explain what the calculation returns (e.g., chart data, interpretations). Without annotations or output details, users lack critical context about the tool's results and limitations, making it inadequate for informed use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions the parameters 'дате, времени и месту рождения' (date, time, and place of birth), which aligns with the required parameters in the schema. However, with 100% schema description coverage, the schema already fully documents all 5 parameters, including optional latitude and longitude. The description adds minimal value beyond what the schema provides, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Рассчитывает карту Human Design по дате, времени и месту рождения' (Calculates a Human Design chart based on date, time, and place of birth). It specifies the verb 'рассчитывает' (calculates) and the resource 'карту Human Design' (Human Design chart), making the action clear. However, it doesn't explicitly differentiate from its sibling tool 'get_human_design_definition', which likely provides definitions rather than calculations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions the required inputs but doesn't specify scenarios, prerequisites, or comparisons to the sibling tool 'get_human_design_definition'. Without such context, users must infer usage based on the tool name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_human_design_definitionC

Получить определения и значения в Human Design

ParametersJSON Schema
NameRequiredDescriptionDefault
componentYesКомпонент Human Design для определения

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states it 'gets definitions and meanings' without specifying whether this is a read-only operation, what format the output takes, whether there are rate limits, authentication requirements, or other behavioral traits. This leaves significant gaps for an agent to understand how to use it effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence in Russian that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool with one parameter and no complex behavior to explain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., format, structure of definitions), how errors are handled, or how it differs from the sibling tool. For a tool with no structured output documentation, the description should provide more context about expected results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage with a clear enum for the 'component' parameter, so the schema does the heavy lifting. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain what each component type means or provide examples). This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'Получить определения и значения в Human Design' (Get definitions and meanings in Human Design), which is clear but vague. It specifies the domain (Human Design) and general action (get definitions/meanings), but doesn't distinguish it from the sibling tool 'calculate_human_design' or provide specific details about what kind of definitions are retrieved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling tool 'calculate_human_design'. There's no mention of prerequisites, alternatives, or specific contexts where this tool is appropriate versus others. The user must infer usage from the name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedcalculate_human_design
    • First observedget_human_design_definition
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one calculates a Human Design chart from birth data, while the other retrieves definitions and meanings. There is no overlap or ambiguity between these functions.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (calculate_human_design and get_human_design_definition), using snake_case and clear action verbs that align with their functions.

Tool Count2/5

With only two tools, the server feels thin for the Human Design domain, which typically involves multiple components like centers, gates, profiles, and types. A more comprehensive set would include tools for interpreting or analyzing specific aspects beyond just calculation and definitions.

Completeness2/5

The tool surface is significantly incomplete for Human Design. It lacks tools for key operations such as interpreting chart components (e.g., centers, channels), generating reports, or comparing charts, which are essential for practical use in this domain.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • BaZi (Eight Characters)

    minionszyw
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Calculates Chinese BaZi (Four Pillars of Destiny) charts based on birth date, time, and location, including solar term information, decade luck cycles, and true solar time corrections.
    2
    -

  • mcp-astrology

    molpass
    A
    license
    A
    quality
    C
    maintenance
    Receives birth information and returns Western astrology natal charts including planetary positions, houses, ASC/MC text, and a chart PNG image.
    1
    MIT

  • Astrology MCP Server

    memyselfandm
    A
    license
    Not graded
    quality
    D
    maintenance
    Calculates astrological birth charts including planetary positions, house placements, and aspects based on birth date, time, and location.
    714
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dvvolkovv/MCP_Human_design'

If you have feedback or need assistance with the MCP directory API, please join our Discord server