Lanonasis MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONASIS_SUPABASE_URL | Yes | The URL of the Lanonasis Supabase instance (e.g., https://api.lanonasis.com) | |
| SUPABASE_SSL_CERT_PATH | No | Path to the Supabase SSL certificate file | |
| ONASIS_SUPABASE_ANON_KEY | Yes | The anonymous key for the Supabase project | |
| ONASIS_SUPABASE_SERVICE_KEY | No | Optional service role key for privileged operations |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_memoryB | Create a new memory entry with vector embedding |
| search_memoriesC | Search through memories with semantic vector search |
| get_memoryB | Get a specific memory by ID |
| update_memoryC | Update an existing memory |
| delete_memoryB | Delete a memory by ID |
| list_memoriesC | List memories with pagination and filters |
| create_api_keyC | Create a new API key |
| list_api_keysC | List API keys |
| rotate_api_keyC | Rotate an API key |
| delete_api_keyB | Delete an API key |
| get_health_statusA | Get system health status |
| get_auth_statusD | Get authentication status |
| get_organization_infoB | Get organization information |
| create_projectD | Create a new project |
| list_projectsC | List projects |
| get_configC | Get configuration settings |
| set_configD | Set configuration setting |
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 17 tools
Each tool targets a distinct resource and action. Memory tools clearly separate get (by ID), search (semantic), and list (paginated) operations, while API keys, projects, config, and status tools are uniquely scoped. No two tools overlap significantly.
All 17 tools follow a consistent verb_noun snake_case pattern, using plural nouns for list/search and singular for point operations. Verb choices are clear (create, get, update, delete, list, search, rotate, set). No mixing of conventions.
At 17, the tool count is slightly above the typical 3-15 range, but the breadth of domains (memories, API keys, projects, config, status) justifies the extra tools. It feels well-scoped for a general-purpose backend server.
Memory management is fully covered with CRUD plus search. API key lifecycle is also solid. However, project support only includes create and list—no get, update, or delete—leaving a notable gap in the project resource lifecycle.