home / mcp / people info mcp server
Orchestrates AI-assisted routing to developer and designer data servers via MCP, with natural-language response enhancement.
Configuration
View docs{
"mcpServers": {
"banique15-mcp-server": {
"command": "node",
"args": [
"/Users/banik/Desktop/Projects2025/MCP-Server/people-info-server/index.js"
],
"env": {
"ANTHROPIC_API_KEY": "your_anthropic_api_key_here"
}
}
}
}You run an intelligent MCP orchestrator that analyzes natural language queries, decides which specialized MCP servers to call, and then enhances raw responses into fluent, natural-language answers. This setup enables dynamic, on-demand data retrieval from dedicated developer and designer sources, while keeping orchestration logic separate from data storage and presentation.
You interact with the system by asking plain-language questions. The orchestrator analyzes your query, decides whether it concerns developers, designers, or another topic, and then starts the appropriate data server on demand. The specialized server provides the requested information via an MCP tool, and the orchestrator enhances the result into a natural, conversational answer.
Prerequisites: ensure Node.js is installed on your machine. You will also need an Anthropic API key for the AI-powered analysis and enhancement.
Step 1: Install the developer and designer data servers and the orchestrator locally.
cd people-info-server
npm install
cp .env.template .env
# Ensure the environment has your Anthropic API key
# ANTHROPIC_API_KEY=your_anthropic_api_key_here
# Start the orchestrator (and the specialized servers on demand as needed)
npm startStep 2: Configure the MCP client (your MCP desktop or client) to connect to the orchestrator. Use the following command configuration to point to the orchestrator entry point for the people-info server.
{
"mcpServers": {
"people-info": {
"command": "node",
"args": ["/Users/banik/Desktop/Projects2025/MCP-Server/people-info-server/index.js"],
"env": {
"ANTHROPIC_API_KEY": "your_anthropic_api_key_here"
}
}
}
}Configuration and on-demand orchestration details are focused on two specialized servers and a central orchestrator. The Public API surface is exposed through MCP tooling, which calls the appropriate server to fetch name information for developers or designers.
Keep your Anthropic API key secure. Do not commit keys to version control. When you stop using a specialized server, the orchestrator can shut it down to reclaim resources. Regularly update dependencies and verify that the orchestration logic correctly routes queries to the intended specialized server.
If queries return unexpected categories, verify that the orchestrator is running and that the developer-info and designer-info servers can be started on demand. Check that the MCP client can reach the orchestrator process and that the environment variables are correctly set in your MCP client configuration.
Tool used by the orchestrator to fetch the developer's name from the developer-info server.
Tool used by the orchestrator to fetch the designer's name from the designer-info server.