Server Details
Persistent semantic memory-as-a-service for legal AI agents. Store and recall case notes, client context, and matter history via MCP. Namespace-isolated, audit-logged, and GDPR-compliant.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
4 toolsdelete_memoryInspect
Permanently delete a stored memory by its UUID. This is a hard delete for GDPR right-to-erasure compliance. The memory is removed from both the vector store and the database. This action cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| memory_id | Yes |
get_statsInspect
Get usage statistics for your tenant: total memory count, today's API call counts (store/recall/read), all-time totals, and your wallet balance.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
recall_memoriesInspect
Semantically search stored legal memories using natural language. Returns the most relevant results ranked by cosine similarity. Optionally filter by matter_id to restrict results to a specific case. Results include the text preview, score, and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| top_k | No | ||
| matter_id | No |
store_memoryInspect
Store a legal text memory for later semantic recall. The text is embedded using nomic-embed-text and stored in a vector database. Returns the memory ID, token count, and a preview of the stored text. Use matter_id to scope memories to a specific case or client matter.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| agent_id | No | ||
| metadata | No | ||
| matter_id | No | ||
| source_doc | No |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!