Alpha implementation exposes four MCP tools plus health endpoints.
(Health endpoints /api/health, /api/ready are standard HTTP, not MCP tools.)
{
"workspaceName": "demo",
"name": "Alice",
"entityType": "Person",
"observations": ["Software engineer"],
"metadata": "{\"dept\":\"Engineering\"}",
"id": "<guid>"
}
| Observations persisted internally joined by “ | ” delimiter; returned as list. |
Returns all entities and relations. Parameters:
Response:
{
"workspaceName": "demo",
"entities": [ {"name":"Alice"}, {"name":"ProjectX"} ],
"relations": [ {"relationType":"works_on"} ]
}
Create or update an entity (matched by name within workspace). Request body shape:
{
"workspaceName": "demo",
"name": "Alice",
"entityType": "Person",
"observations": ["Software engineer"],
"metadata": "{\"dept\":\"Engineering\"}"
}
Response:
{ "success": true, "id": "<guid>", "workspace": "demo", "name": "Alice" }
Failure example:
{ "success": false, "message": "Invalid entity payload. Require workspaceName, name and entityType." }
Creates or updates a relation between two entities. Parameters body:
{
"workspaceName": "demo",
"fromEntityId": "<guid>",
"toEntityId": "<guid>",
"relationType": "works_with",
"metadata": "{\"since\":\"2025\"}"
}
Alternatively supply legacy names:
{
"workspaceName": "demo",
"from": "Alice",
"to": "ProjectX",
"relationType": "works_on"
}
Response:
{ "success": true, "relationId": "<guid>", "workspace": "demo", "fromEntityId": "<guid>", "toEntityId": "<guid>", "relationType": "works_on" }
Errors:
List all relations from a given entity. Parameters:
Response:
{
"success": true,
"workspaceName": "demo",
"entityId": "<guid>",
"relations": [ {"relationType": "works_on", "toEntityId": "<guid>"} ]
}
Failure:
{ "success": false, "message": "Entity 'Alice' not found in workspace 'demo'." }
Errors returned uniformly:
{ "success": false, "message": "<reason>" }
Common types: ValidationError, NotFoundError, ConflictError, StorageError.
search_entities, search_relations, stats, temporal events, batch operations, merge/detect duplicates, user-specific metadata features.
Currently none (trusted dev environment). Add Azure AD / API key layer before external exposure.
Tool set considered v0 (alpha). Additions will be non-breaking by extending responses.