Binelek MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Binelek MCP Serverquery the knowledge graph for products in electronics"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Binelek MCP Server
Model Context Protocol (MCP) server for the Binelek Platform. This server provides MCP tools for interacting with the Binelek knowledge graph, search, AI, and data pipeline services through the API Gateway.
Features
Knowledge Graph Tools: Query, create, update, and delete entities and relationships
Search Tools: Semantic, keyword, and hybrid search capabilities
AI Tools: Chat with AI, make predictions, analyze entities
Pipeline Tools: Trigger and monitor data pipelines
Admin Tools: Domain configuration, YAML validation, code generation
Related MCP server: Britive MCP Server
Installation
npm install
npm run buildConfiguration
Create a .env file (copy from .env.example):
BINELEK_GATEWAY_URL=http://localhost:8092
BINELEK_TENANT_ID=core
BINELEK_JWT_TOKEN=your-jwt-token-here
LOG_LEVEL=infoUsage
As a Standalone Server
npm startWith Claude Desktop
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"binelek": {
"command": "node",
"args": ["/path/to/binelek-mcp-server/build/index.js"],
"env": {
"BINELEK_GATEWAY_URL": "http://localhost:8092",
"BINELEK_TENANT_ID": "core",
"BINELEK_JWT_TOKEN": "your-jwt-token"
}
}
}
}With VS Code Extension
The binelek-vscode-extension uses this MCP server. See that project's README for setup instructions.
Available Tools
Ontology Tools
binelek_get_entity- Get entity by IDbinelek_query_entities- Execute Cypher queriesbinelek_create_entity- Create new entitiesbinelek_update_entity- Update existing entitiesbinelek_delete_entity- Delete entitiesbinelek_get_relationships- Get entity relationshipsbinelek_create_relationship- Create relationships
Search Tools
binelek_semantic_search- Semantic search using embeddingsbinelek_keyword_search- Keyword search with Elasticsearchbinelek_hybrid_search- Combined semantic + keyword search
AI Tools
binelek_ai_chat- Chat with Binelek AI assistantbinelek_ai_predict- Make predictions with ML modelsbinelek_ai_analyze_entity- AI-powered entity analysis
Pipeline Tools
binelek_list_pipelines- List all pipelinesbinelek_get_pipeline- Get pipeline detailsbinelek_trigger_pipeline- Trigger pipeline executionbinelek_get_pipeline_runs- Get pipeline run history
Admin Tools
binelek_list_domains- List available domainsbinelek_get_domain- Get domain configurationbinelek_get_ontology_schema- Get ontology YAML schemabinelek_validate_yaml- Validate ontology YAMLbinelek_generate_code- Generate code from YAML
Authentication
The MCP server uses JWT tokens to authenticate with the Binelek API Gateway. You can:
Set in environment:
BINELEK_JWT_TOKEN=your-tokenSet in .env file: See
.env.examplePass via MCP config: When configuring in Claude Desktop or VS Code
To obtain a JWT token, authenticate through the Binelek platform or use the auth API:
curl -X POST http://localhost:8092/api/auth/login \
-H "Content-Type: application/json" \
-d '{"email":"user@example.com","password":"your-password"}'Architecture
MCP Client (Claude/VS Code)
↓ stdio
MCP Server (this project)
↓ HTTP/REST
API Gateway (localhost:8092)
↓ routes to
Backend Services (Ontology, Search, AI, Pipeline, etc.)Important: The MCP server communicates ONLY with the API Gateway, never directly with backend services. This ensures proper authentication, tenant isolation, and rate limiting.
Development
# Install dependencies
npm install
# Build
npm run build
# Development mode (auto-reload)
npm run dev
# Type check
npm run type-checkError Handling
The server handles errors gracefully and returns them in MCP format:
{
"content": [{
"type": "text",
"text": "Error: Entity not found: prop_123"
}],
"isError": true
}License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
Connect AI clients to biomedical data and tools.
Unified gateway exposing 150+ tools across all NexGenData MCP servers via one endpoint.
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides LLM-agnostic access to API documentation through MCP and REST endpoints, enabling AI assistants to retrieve, search, and proxy requests to whitelisted APIs across multiple platforms.-

Britive MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.1-- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with OSDU platform services including search, data management, and schema operations.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables querying disease/target/drug knowledge graph from Open Targets, supporting searches, profiles, and associations via natural language through the Pipeworx gateway.6 npmMIT