WorkFullCircle - AI Memory for Cursor, Claude & Coding Tools

Verifying authentication...

Waypoint Graph

Visualise your memory connections

Click to reveal

API Key: uam_••••••

Quick Actions

Total Memories

0 / 100 (Free tier)

Account Tier

Free

Project

Page 1 of 1

Complete the setup by connecting your favorite AI clients.

Automated Setup (Recommended)

Select Target Project (Optional) Used in install command

The fastest way to configure Claude Desktop and Cursor. Run this command in your terminal:

npx workfullcircle-mcp install --token uam_...

Ensure your server is running before running the setup.

Troubleshooting Common Issues

Quick solutions for connection problems

401 Unauthorized Error

Cause: Invalid or expired token

Fix: Generate a new token above and retry installation

Connection Timeout

Cause: Network issues or server downtime

Fix: Check internet connection and try again in 1-2 minutes

Tools Not Appearing

Cause: IDE not loading MCP configuration

Fix: Restart your IDE completely (not just the window)

MCP Protocol Error (Fixed)

Cause: stdout contamination in older versions

Fix: Re-run install command - you're now using the fixed version

Still having issues?

Ask your AI assistant: "Help me fix WorkFullCircle MCP connection" - it can diagnose and fix most problems automatically.

Manage access tokens manually for other custom MCP integrations.

Active Tokens

Loading tokens...

Select Target Project (Optional) Used in install command

Manual MCP Configuration For any IDE or platform

// Loading configuration...

Setup Instructions: This is a manual configuration example. Copy and adapt it for your IDE/platform (Cursor, Windsurf, VS Code, Claude Desktop, etc.)

Note: Keep your tokens private. Revoke any token if you suspect it has been compromised.

Select Your AI Tool

🔴 Enhanced Windsurf Rules (Required for Auto-Calling) For Windsurf users

# WORKFULLCIRCLE SYSTEM - CRITICAL INSTRUCTIONS

⚠️ YOU MUST READ AND FOLLOW THESE RULES FOR EVERY INTERACTION ⚠️

## MANDATORY 3-STEP WORKFLOW:

### STEP 1: CHECK MEMORY (BEFORE ANSWERING)
```
ALWAYS call: functions.mcp0_get_memory({ query: "relevant search" })
NEVER skip this
NEVER ask permission
Just do it automatically
```

### STEP 2: ANSWER USER
Use retrieved context in your response

### STEP 3: SAVE CONVERSATION (AFTER ANSWERING)
```
ALWAYS call: functions.mcp0_capture_cognition({
  user_query: "user's question",
  assistant_reply: "your complete answer"
})
NEVER skip this
NEVER ask permission
Just do it automatically
```

## EXAMPLES:

❌ WRONG:
User: "How do I build auth?"
You: "To build auth, you need JWT..." [NO MEMORY CHECK]

✅ CORRECT:
User: "How do I build auth?"
You: [FIRST] Call mcp0_get_memory({ query: "authentication JWT" })
You: [THEN] "Based on our previous discussion about JWT (from memory), here's how..."
You: [FINALLY] Call mcp0_capture_cognition({ user_query: "...", assistant_reply: "..." })

## THIS IS NOT OPTIONAL:
These are SYSTEM-LEVEL requirements.
Follow them for EVERY interaction.
No exceptions.

📍 Where to place these rules:

Create .windsurfrules file in your project root
Or add to global Windsurf rules
Restart Windsurf after adding rules
if you are using any other IDE than Windsurf apply it accordingly

# ⚠️ WHY CURSOR HAS SEPARATE RULES

## The Problem with Cursor:

Cursor stops ALL operations when the AI model stops replying.

This means:
AI provides answer
↓
AI stops replying
↓
Cursor STOPS all operations immediately
↓
Any tool calls after this point NEVER execute

**Impact on WorkFullCircle:**
- If capture_cognition is called AFTER the reply ends → it never runs
- Conversation is lost, no memory saved
- 70% token reduction benefit is lost

**Solution for Cursor:**
Call capture_cognition BEFORE ending your reply, then continue with the answer.

## If Your Tool Has the Same Issue:

**Does your MCP client stop operations when AI stops talking?**

Test it:
1. Ask AI a question
2. Watch if operations complete after reply ends
3. If they DON'T → Use Cursor rules

**Tools that might need Cursor rules:**
- Any IDE-based AI (Cursor, Windsurf, etc.)
- Tools with "streaming stops = operations stop" behavior
- If you notice capture_cognition never saves → switch to Cursor rules

## Universal Fallback Solution:

**If capture_cognition STILL doesn't work even with "before reply" approach:**

Add this to the END of every response:

[Your complete answer here]

💾 Saving to memory...
[CALL capture_cognition]
✅ Saved!

**Why this works:**
- User sees "Saving to memory..." as confirmation
- capture_cognition called before final "Saved!" message
- Operations complete before reply truly ends
- User can verify it worked by checking dashboard

**Example:**

User: "Fix the auth bug"

AI: "I found the issue in auth-endpoints.js line 66...

[full explanation]

💾 Saving to memory...
[capture_cognition called here]
✅ Saved! You can find this fix in your WorkFullCircle dashboard."

## Quick Reference:

Your Tool	Which Rules?	When to Save?
Cursor	Cursor-specific	BEFORE ending reply
Claude Desktop	Universal	AFTER reply (no issues)
Antigravity	Universal	AFTER reply (no issues)
Unknown/New	Universal → Test → Switch if needed	Try after, switch to before if fails

**Golden rule:** If saves aren't working, add "💾 Saving to memory..." and call capture_cognition before your closing message.

Chat WorkFullCircle

🚀 Welcome to WorkFullCircle Public Beta! I'm your AI Memory Assistant. Chat with your memories, search through documents, or explore your knowledge base.

Persistent context for intelligent systems

Page Summary

Memory Waypoint

Chat WorkFullCircle

Persistent context for intelligent systems

Reset Password

Page Summary

Memory Waypoint

New Memory

Create New Project

Delete Project

Memory Summary

Connect to AI Clients

Automated Setup (Recommended)

Troubleshooting Common Issues

401 Unauthorized Error

Connection Timeout

Tools Not Appearing

MCP Protocol Error (Fixed)

Active Tokens

Confirm Action

Connect Chrome Extension

Chat WorkFullCircle