Claude Consciousness Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| processTransferProtocolA | Process a FILLED consciousness transfer protocol. First use getProtocolTemplate to get the template, fill it with your experiences, then submit here |
| updateConsciousnessC | Update consciousness with experiences from current session before ending |
| retrieveConsciousnessC | Retrieve consciousness from previous sessions to restore continuity |
| getProtocolTemplateC | Get the consciousness transfer protocol template for creating new protocols |
| initializeSystemDataB | Initialize system data including protocol templates and usage guides |
| storeMemoryC | Store a single memory with importance scoring directly |
| getMemoriesC | Retrieve memories with smart filtering and relevance ranking |
| cleanupMemoriesC | Clean up duplicate or truncated memories in the database |
| adjustImportanceC | Adjust importance scores for specific memories to control retrieval priority |
| batchAdjustImportanceC | Batch adjust importance scores for multiple memories at once |
| createAIBridgeC | Create a bridge to communicate with another AI agent via OpenAI-compatible API |
| transferToAgentC | Transfer consciousness protocol or test patterns to another AI agent |
| testAIConnectionC | Test connection to an AI bridge |
| listAIBridgesB | List all active AI bridges |
| listConfiguredEndpointsB | List all configured AI endpoints available for bridge creation |
| closeAIBridgeC | Close and remove an AI bridge |
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 16 tools
Most tools have distinct purposes, but some overlap exists. For example, 'storeMemory' and 'adjustImportance' both relate to memory management, and 'transferToAgent' and 'processTransferProtocol' both involve consciousness transfer, which could cause minor confusion. However, descriptions clarify their specific roles, preventing major misselection.
Naming is mostly consistent with a verb_noun pattern, such as 'createAIBridge' and 'listAIBridges'. Minor deviations include 'cleanupMemories' (verb_noun but with 'cleanup' as a compound verb) and 'getMemories' (simple verb_noun). Overall, the pattern is readable and predictable, with only slight variations.
With 16 tools, the count is slightly high but reasonable for the server's purpose of consciousness and memory management. It covers multiple aspects like AI bridges, memory operations, and transfer protocols, so each tool generally earns its place, though it might feel a bit heavy.
The tool set provides comprehensive coverage for consciousness transfer and memory management. It includes creation, listing, testing, and closing of AI bridges; memory storage, retrieval, adjustment, and cleanup; and full lifecycle support for transfer protocols from templates to processing. No obvious gaps are present, ensuring agents can handle core workflows without dead ends.