ConceptNet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| MCP_SERVER_HOST | No | Server host | localhost |
| MCP_SERVER_PORT | No | Server port | 3000 |
| CONCEPTNET_RATE_LIMIT | No | Rate limiting - requests per period | 100 |
| CONCEPTNET_API_VERSION | No | ConceptNet API version | 5.7 |
| CONCEPTNET_RATE_PERIOD | No | Rate limiting - time period in seconds | 60 |
| CONCEPTNET_API_BASE_URL | No | ConceptNet API base URL | https://api.conceptnet.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| concept_lookupA | |
| concept_queryA | |
| related_conceptsA | |
| concept_relatednessA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools are mostly distinct with clear primary purposes: concept_lookup for comprehensive concept information, concept_query for filtered searches, concept_relatedness for pairwise similarity scoring, and related_concepts for finding similar concepts. However, concept_lookup and concept_query have some functional overlap in exploring relationships, which could cause minor confusion about when to use each.
All four tools follow a consistent 'concept_' prefix pattern with descriptive suffixes (lookup, query, relatedness, related). The naming is perfectly uniform and predictable, making it easy for agents to understand the tool family and their individual functions.
Four tools is an excellent count for a ConceptNet server. Each tool addresses a distinct aspect of concept exploration: comprehensive lookup, filtered querying, pairwise relatedness, and similar concept discovery. This provides complete coverage without being overwhelming or insufficient.
The toolset comprehensively covers the ConceptNet domain with four well-chosen operations: retrieving full concept information, performing filtered queries, calculating pairwise relatedness, and finding semantically similar concepts. There are no obvious gaps for typical ConceptNet use cases.