Connect AI tools

ProjectCtx supports two connection models: automatic local configuration and manual account-side connector setup.

Preview Local Configuration#

Run:

projectctx connect --dry-run

The preview reports detected clients, proposed configuration files, managed instruction blocks, backups, and any manual steps. It does not write files or run client commands.

Apply the same configuration with:

projectctx connect

Rerunning the command is safe. ProjectCtx updates its existing managed blocks and hook entries instead of adding duplicates.

Supported Local Clients#

Claude Code#

The connector registers the hosted project-memory MCP server and installs the managed ProjectCtx instruction block. When the Claude CLI is available, projectctx connect uses its native MCP command.

Restart Claude Code, approve any lifecycle hook prompt, and complete OAuth on the first ProjectCtx memory call.

Cursor#

The connector updates Cursor's MCP configuration and managed instructions while preserving unrelated servers and rules. Restart Cursor after applying the configuration.

Local Cursor sessions can run the shared automatic-memory hook. Hosted Cursor cloud agents cannot access user-machine hooks.

Codex#

The connector updates Codex MCP configuration and the managed ProjectCtx block in the applicable agent instructions. Restart Codex so it loads the new server and instructions.

Hermes / Jarvis#

The connector verifies the existing headless MCP entry without rewriting credential-bearing YAML. Hosted ProjectCtx tools appear with an mcp_project_memory_ prefix.

Test the configured server with:

hermes mcp test project-memory

Hosted And Account-Side Clients#

ChatGPT, claude.ai, and Claude Desktop use connector settings owned by the client account. They are printed as manual steps because ProjectCtx must not edit those settings on your behalf.

Use this MCP URL:

https://projectctx.com/mcp

Add the instruction text printed by projectctx connect, then use the connector once to start OAuth. The client stores its own access and refresh tokens.

Hosted conversations do not run lifecycle hooks on your machine. They rely on the managed instructions to load, search, and save durable context.

Confirm The Connection#

Use:

projectctx doctor

Doctor validates the local runtime and supported configuration files. It does not inspect OAuth credentials owned by an external client.

Finally, ask the client to load ProjectCtx check-in context. A successful answer should be grounded in ProjectCtx records rather than local conversation history.

Remove Or Update Configuration#

Rerun projectctx connect to update managed files and hook entries. The command backs up changed files and preserves unrelated configuration.

To remove only the shared automatic-memory runtime and hooks, follow Automatic memory. ProjectCtx account data and hosted MCP configuration remain intact.