@cogniahq/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COGNIA_API_KEY | Yes | Your Cognia API key (required) | |
| COGNIA_BASE_URL | No | Base URL for the Cognia API | https://api.cogniahq.tech |
| COGNIA_TIMEOUT_MS | No | Timeout in milliseconds for API requests | 30000 |
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 |
|---|---|
| cognia_searchA | Hybrid (dense + sparse BM25) search across the user's Cognia memories with cross-encoder reranking. Use this whenever the user asks about anything in their workspace, documents, or browsing history. |
| cognia_get_memoryA | Fetch the full content of a single memory by id. Use after cognia_search when you need more than the snippet. |
| cognia_list_memoriesA | Paginated chronological listing of memories. Useful for browsing recent activity. Use cognia_search for semantic queries. |
| cognia_action_planA | Plan a Cognia integration action, such as listing, creating, updating, or deleting Google Calendar events. Returns an action_run_id. Mutating drafts require execution before external systems change unless executionPolicy is auto_execute and the API key permits it. |
| cognia_action_executeB | Execute a previously drafted Cognia action by action_run_id. This may mutate external systems such as Google Calendar. |
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 5 tools
Each tool has a clearly distinct purpose: action planning vs execution, and memory retrieval via different methods (get by ID, list chronologically, search semantically). No overlap.
All tools share the 'cognia_' prefix, but naming patterns vary: two use 'domain_verb' (action_execute, action_plan), two use 'verb_noun' (get_memory, list_memories), and one uses just a verb (cognia_search). Also singular/plural inconsistency (memory vs memories).
With 5 tools covering two distinct domains (actions and memories), the count is well-scoped and not overwhelming or too sparse.
The actions domain covers plan and execute but lacks listing, updating, or canceling actions. The memory domain allows reading (get, list, search) but no create, update, or delete operations, leaving notable gaps for a full lifecycle.