Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xysq.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use the xysq MCP server in Cursor so your agent can authenticate to xysq and use memory tools (recall, retain, list, and related actions) from your editor.

​
Before You Connect

Sign in to your xysq account at app.xysq.ai.
xysq Login Screen

​
Step 1 - Generate Your API Key

  1. After logging in, click the Connect Agent button.
Connect Agent Button
  1. Select the Cursor tab.
Cursor Tab
  1. Click Generate API Key - your key will be created automatically.
Generate API Key

​
Step 2 - Copy the MCP Schema

Copy the generated MCP configuration schema: 
{
  "mcpServers": {
    "xysq": {
      "url": "https://api.xysq.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    },
    "xysq-legacy": {
      "url": "https://api.xysq.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

​
Step 3 - Add to Cursor

  1. Open Cursor and navigate to mcp.json. You can find it at:
OSPath
Windows%USERPROFILE%\.cursor\mcp.json
macOS / Linux~/.cursor/mcp.json
  1. Paste the copied schema into mcp.json and save.
Paste schema into mcp.json

​
Pinning Cursor to a team vault

By default the connection above gives Cursor access to your personal vault. To make Cursor work only against a specific team’s vault — useful when you want a workspace dedicated to one team — point the URL at the team-pinned endpoint: 
{
  "mcpServers": {
    "xysq-acme": {
      "url": "https://api.xysq.ai/mcp/team/YOUR_TEAM_ID",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Replace YOUR_TEAM_ID with the team’s UUID (find it in Team Settings at app.xysq.ai or by asking the agent List my xysq teams. from a personal connection). On a team-pinned connection:
  • Every memory action routes to that team’s vault — no per-call team_id needed.
  • Personal-vault writes and reads are blocked; the agent cannot leak conversation content into your personal memories.
  • Personal tools like memory_tags, skill_sync, and list_teams are disabled.
  • You still authenticate with your own API key — your role on the team determines what you can do (ro reads, rw writes, admin deletes).
Add multiple entries with different names (xysq-acme, xysq-platform, xysq for personal) to switch contexts without editing the file.

​
Step 4 - Connect from Cursor

  1. Open the Agent tab in Cursor.
  2. Type:
Connect to xysq agent
Cursor will initiate the connection automatically and you can start talking to it normally.
Connect to xysq agent in Cursor

​
Adding Memories

Once connected, you can ask the agent to remember, retain, or delete anything across future sessions: 
Remember that I prefer tabs over spaces in all projects.

Retain: My project deadline is June 15.

Delete the memory about my old API endpoint.
The agent will store and retrieve this from your xysq memory automatically.

​
Video Walkthrough

​
Troubleshooting

ProblemFix
Server never connectsConfirm the URL and API key are copied exactly from the xysq dashboard. Check VPN or firewall rules for HTTPS to the MCP host.
Repeated auth promptsMake sure you finished the browser approval step. If the problem persists, remove and re-add the MCP server, then authenticate again.
Wrong workspace scopeUse the global ~/.cursor/mcp.json if you want xysq in every project. Use .cursor/mcp.json inside a repo only if you want to scope it to that project.
API key not workingRegenerate the key from the xysq dashboard and update the Authorization header in your mcp.json.
Schema paste breaks JSONValidate your mcp.json with a JSON validator - a missing comma or brace will silently prevent the server from loading.