Overview

Quint MCP gives any MCP-compatible AI agent persistent memory, cross-platform identity, and dynamic context. One connection — your agent knows you everywhere.

Connect once. Every new session loads your context automatically. Facts, preferences, decisions, and history follow you across Claude.ai, Claude Desktop, Claude Mobile, and Claude Code.

MCP Endpoint
https://api.getquint.ai/mcp
Auth
OAuth 2.0 + Bearer token
Protocol
MCP (remote, SSE)

Available Tools

get_context get_soul write_context context_checkpoint extraction_commit

Quick Start

Get Quint connected in under two minutes.

Claude Desktop (easiest)

  1. Create your account — Sign up at getquint.ai/start.
  2. Download the extension — Go to your dashboard and click Download for Claude Desktop. You'll get a .dxt file.
  3. Install — Double-click the .dxt file. Claude Desktop installs the extension automatically.
  4. Restart Claude Desktop — A browser window opens for OAuth authorization. Approve access.
  5. Done. Your agent now loads context at the start of every session.

Claude.ai (web)

  1. Go to claude.ai/settings/connectors
  2. Click Add Custom Connector
  3. Name: Quint  |  URL: https://api.getquint.ai/mcp
  4. Click Connect — your browser opens for OAuth authorization.
  5. Approve access. Quint is now connected across all your Claude surfaces.
Cross-platform: Connecting via Claude.ai syncs to Claude Desktop and Claude Mobile automatically — one authorization covers all surfaces linked to your Claude account.

Tools Reference

Quint exposes five MCP tools. They are called by the AI agent, not directly by you — just talk to Claude normally. The triggers below are example phrases that cause Claude to call each tool.

get_context

Loads your current context, memory, and recent events. Called automatically at the start of every session. Use a specific query to retrieve focused context on a topic.

Parameters

NameTypeRequiredDescription
query string optional What context to load. Default: "current context". Use specific topics for focused retrieval, e.g. "Colossal lawsuit".
scope string optional One of: all | professional | personal | sensitive | public. Default: all.
max_tokens integer optional Max tokens to return. Default: 2000.
Returns

A synthesized narrative briefing or topic-focused context based on the query.

Example triggers

"What am I working on?"
"Load my context"
"What do you know about me?"

get_soul

Loads your agent's soul — name, personality, and communication style. Called at session start after get_context. Shapes how Claude talks to you for the rest of the session.

Parameters

NameTypeRequiredDescription
No parameters.
Returns

Soul profile text with agent name, personality instructions, and communication style to apply for the session.

Example triggers

"What's my agent's personality?"
Or called automatically at session start.

write_context

Saves a fact about you to Quint. Call when you share something worth remembering. Facts persist across all sessions and surfaces.

Parameters

NameTypeRequiredDescription
content string required The fact to store.
scope string optional One of: public | professional | personal | sensitive. Default: professional.
fact_type string optional One of: fact | preference | relationship | decision | history. Default: fact.
Returns

Confirmation with context ID.

Example triggers

"Remember that I decided to use PostgreSQL."
"Save this for later."

context_checkpoint

Saves the current conversation thread to Quint. Designed for long sessions — prevents context loss when the context window fills. Can be called manually or triggered automatically.

Parameters

NameTypeRequiredDescription
summary string required Summary of the conversation so far.
key_facts array<string> optional Most important facts from this session to preserve.
Returns

Checkpoint ID.

Example triggers

"Save our conversation so far"
Or called automatically when context window is filling.

extraction_commit

At the end of a substantive session, extracts and permanently stores the most important facts learned. The definitive write operation for session conclusions.

Parameters

NameTypeRequiredDescription
facts array<string> required List of facts to commit to long-term memory.
Returns

Confirmation with count of facts stored.

Example triggers

"Save the key decisions from this session."
Or called automatically at session end.

Authentication

Quint uses OAuth 2.0. When connecting via Claude.ai or Claude Desktop, the OAuth flow completes automatically in your browser — no manual token handling required.

Direct Integration

For developers integrating directly against the MCP endpoint:

Authorization: Bearer <your_token>

Tokens are issued via OAuth 2.0 authorization code flow with PKCE. Dynamic client registration (RFC 7591) is supported.

OAuth Endpoints

PurposeURL
Authorizehttps://api.getquint.ai/oauth/authorize
Tokenhttps://api.getquint.ai/oauth/token
Register clienthttps://api.getquint.ai/oauth/register
Discoveryhttps://api.getquint.ai/.well-known/oauth-authorization-server
MCP clients handle this automatically. Claude.ai and Claude Desktop complete the full OAuth flow in the browser. You only need these endpoints if you're building a custom MCP client or direct API integration.

Connect to Claude.ai

Remote MCP connector — works on Claude.ai web, Claude Mobile, and Claude Desktop (synced via your Claude account).

  1. Go to claude.ai/settings/connectors
  2. Click Add Custom Connector
  3. Set Name to Quint and URL to https://api.getquint.ai/mcp
  4. Click Connect — your browser opens for OAuth authorization
  5. Approve access. Done.

Once connected, Quint loads your context automatically at the start of every new Claude conversation. No prompting required.

Connect to Claude Desktop

Native extension install via .dxt — single click, no config files to edit.

  2. Go to your dashboard → click Download for Claude Desktop
  3. Double-click the downloaded .dxt file to install
  4. Restart Claude Desktop
  5. A browser window opens — authorize Quint via OAuth
  6. Done. Your agent loads context automatically every session.
What's a .dxt file? It's Anthropic's extension format for Claude Desktop. It bundles the MCP server configuration so you don't have to edit claude_desktop_config.json manually.

FAQ

No. Quint stores facts and context you explicitly write — via write_context or extraction_commit. It does not record your conversation transcripts.
Facts and context you've stored, synthesized into a readable briefing. For generic queries it returns a full profile. For specific queries (e.g. "Colossal lawsuit") it returns focused context on that topic only.
Yes. Go to your dashboard → Export. Downloads your full context as JSON.
The MCP server spec and .dxt extension are open. The hosted service backend is proprietary. You can self-host a compatible MCP server using the open spec.
Any platform that supports remote MCP servers: Claude.ai web, Claude Desktop, Claude Mobile, Claude Code, and any MCP-compatible AI client.
No. Connecting once via Claude.ai connectors syncs to all surfaces tied to your Claude account — web, desktop, and mobile. The .dxt install is only needed if you prefer the native desktop extension experience.