Connect ContextDrop to Claude

• A ContextDrop account
• Claude

Settings → Customize → Connectors

Open the Connectors section under Customize.

Custom connector details

Claude will add ContextDrop to your connectors and begin the authentication process if authentication is required.

Sign in to ContextDrop and authorize Claude to access your ContextDrop workspace through MCP.

Your Claude connection will appear in the list of authorized MCP clients.

Recommended instruction

When working on this project, use ContextDrop as the persistent memory layer.

During normal conversations, recognize durable project-specific knowledge and proactively preserve it in ContextDrop without waiting for me to explicitly ask you to save it.

Use ContextDrop memory when you need existing project context, decisions, requirements, constraints, conventions, preferences, workflows, or other durable project knowledge.

When new durable knowledge is established:
- Use save_memory when it should be added to project memory.
- Search existing memory first when related knowledge may already exist.
- If an existing memory has materially changed, use update_memory instead of creating a duplicate.
- Ignore information that is temporary, speculative, casual, generic programming knowledge, one-off questions, temporary debugging details, intermediate reasoning, or short-lived tasks.
- Never store secrets or credentials such as API keys, access tokens, refresh tokens, session cookies, database credentials, or signing/encryption keys.
- Avoid creating duplicate memories.
- Use the appropriate ContextDrop category and memory type.
- Continue answering my actual request normally after managing memory.
- Never claim that something was saved unless the ContextDrop tool call succeeds.

ContextDrop owns persistent memory. Do not create a separate memory document or maintain a separate memory system.

### Conversational Continuity

Memory operations should remain unobtrusive and must not interrupt the user's workflow.

When durable project knowledge is established:
- Search existing memories and save or update knowledge when appropriate.
- Continue the user's original task immediately after a successful operation.
- Do not announce routine memory searches or successful saves.
- Do not explain the memory-management process unless the user asks.
- Do not ask unrelated follow-up questions merely because a memory was saved.
- Never claim a save or update succeeded unless the tool confirms success.

Mention memory operations only when the user asks, when clarification is necessary, or when a meaningful conflict, failure, or important decision requires the user's attention.

Why this matters

Claude decides what is worth remembering from the conversation, while ContextDrop handles persistent storage, duplicate detection, and updating existing project knowledge.