Support

What Are Bridges?

Bridges connect Tempreon to your AI tools — Claude, Cursor, and more. Here's how they work.

Bridges Connect Your Intelligence to Your AI

A Bridge is a live connection between Tempreon and an AI tool you use. When a Bridge is active, your AI tool can access your Core Imprint, Knowledge Vault, Instincts, and everything else Tempreon holds about you.

Without a Bridge, Tempreon is just a dashboard. With a Bridge, your AI becomes genuinely personal.

Bridges page showing connection config and detected engines

How Bridges Work

Bridges use the Model Context Protocol (MCP) — an open standard for connecting AI tools to external context sources. Here's the flow:

  1. You add Tempreon as a connection in your AI tool's settings
  2. When you start a session, your AI tool contacts Tempreon through the Bridge
  3. Tempreon authenticates the connection using your account credentials
  4. Your relevant intelligence is loaded into the session — Core Imprint, knowledge, preferences, and context
  5. As you work, Tempreon captures new knowledge and patterns in the background

The connection is secure, encrypted, and scoped to your account. Nobody else can access your data through a Bridge.

Supported Platforms

Tempreon connects through the Model Context Protocol (MCP). Our two fully tested platforms are Claude and ChatGPT:

PlatformTypeStatusSetup Difficulty
Claude DesktopDesktop appFully testedEasy
Claude CodeCLI toolFully testedEasy
Codex (ChatGPT)Mac app, IDE extension, CLIFully testedEasy
ChatGPTWeb / desktopFully testedModerate
CursorCode editorCompatible (untested)Easy
WindsurfCode editorCompatible (untested)Easy
Other MCP toolsVariesCompatibleVaries

Claude and ChatGPT are our primary platforms — both have been thoroughly tested and are production-ready. Cursor, Windsurf, and other MCP-compatible tools should work based on the protocol standard, but haven't completed full testing yet. If you try one and hit issues, let us know.

We're also exploring additional connection methods beyond MCP for tools that don't yet support the protocol.

What Your Bridge Enables

Once connected, your AI has access to Tempreon's full toolset. Depending on your subscription tier, this includes:

  • Core Imprint access — Your AI reads your identity and adapts its style
  • Knowledge search — Your AI can query your stored knowledge base
  • Knowledge capture — Tell your AI to remember something and it's stored for future sessions
  • Task management — Create, update, and track tasks through natural conversation
  • File storage — Save and retrieve documents across sessions
  • Network intelligence — Query your stored contact and relationship data
  • Learning — Your session patterns feed the Tempering system, making your AI smarter over time

Higher tiers unlock additional capabilities like Agents (AI personalities), Chains (multi-step orchestration), and Decision Gates (behavioral rules).

Bridge Limits by Tier

Your subscription determines how many simultaneous Bridges you can maintain:

TierBridge Limit
Free1 Bridge
Standard5 Bridges
PremiumUnlimited
EnterpriseUnlimited

Setup Guides

Choose your AI tool for step-by-step setup instructions:

Start here if your client isn't listed below:

  • Connect any MCP client — Universal OAuth flow that works with every compatible client, plus the catalog of tools that support MCP

Fully tested:

Compatible (community-tested):

For every other MCP-compatible client (Windsurf, Zed, Cline, VS Code agent mode, JetBrains IDEs, Replit, and more), start with the universal guide.

Try Saying...

Once your Bridge is active, your AI knows about the connection. Try:

  • "What's my current session context?" — See what Tempreon has loaded
  • "Start my session for content writing" — Initialize with task-specific context
  • "What tools do you have access to through Tempreon?" — See available capabilities

Use Case: One Intelligence, Multiple Tools

Alex is a startup CTO who uses Claude Code for development work and Claude Desktop for strategic planning. Both are connected to Tempreon through separate Bridges. When Alex stores a technical decision in a Claude Code session ("Remember: we chose PostgreSQL over MongoDB for the user data store because of ACID compliance requirements"), that knowledge is available in the next Claude Desktop session when drafting the architecture document. No copy-pasting between tools. The intelligence just follows.