Support

Claude Code Setup

Connect Tempreon to Claude Code (Anthropic's CLI) for developer workflows.

Overview

Claude Code is Anthropic's command-line AI tool for software development. Connecting it to Tempreon means your coding AI knows your architecture decisions, coding style preferences, project context, and everything else in your intelligence layer.

Tempreon is listed in Anthropic's Claude connectors directory, but that listing is a click-to-Connect path for Claude on web, desktop, and mobile. Claude Code is configured separately — it reads its own configuration, so use claude mcp add as documented below. Connecting one does not connect the other.

Prerequisites

  • Claude Code installed and configured
  • A Tempreon account with at least one available Bridge slot
  • Your Tempreon connection details (found in your Bridges dashboard)

Step-by-Step Setup

1. Get Your Connection Details

Log into Tempreon and navigate to the Bridges section of your dashboard to find your MCP server URL.

2. Add to Your MCP Configuration

There are two ways to connect — a single CLI command, or a manual config-file entry. Either works; pick whichever you prefer.

One-command option (recommended): from your terminal, run

claude mcp add --transport http tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp

Add --scope user to make Tempreon available across all your projects. Then run /mcp inside Claude Code to complete the OAuth login.

Manual option: Claude Code reads remote MCP servers from a .mcp.json file. Add a Tempreon entry:

{
  "mcpServers": {
    "tempreon": {
      "type": "http",
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

The "type": "http" line tells Claude Code this is a remote (Streamable HTTP) server rather than a local command — it's required for the connection to be recognized.

Scope: .mcp.json is the project-scoped file — put it in a project directory to scope Tempreon to that project. Claude Code treats it as team-shared and will ask you to approve a project's servers the first time it sees them.

To make Tempreon available in every project, don't move this file — run claude mcp add --transport http --scope user tempreon <your URL> instead. User-scoped servers live in ~/.claude.json, and Claude Code does not read ~/.mcp.json, so a config placed there silently never loads.

3. Authorize the Connection

The first time Claude Code connects to Tempreon, it will open a browser window for authorization:

  1. A browser window opens with the Tempreon consent screen
  2. Log in if prompted
  3. Review and approve the connection

After approving, Claude Code will store the authorization token and reconnect automatically in future sessions.

4. Verify the Connection

Start a Claude Code session and try:

"What Tempreon tools do you have access to?"

If Claude Code lists Tempreon's tools (search, remember, tasks, etc.), the Bridge is working.

Developer-Specific Features

Claude Code with Tempreon is particularly powerful for developers because:

  • Architecture decisions persist. "Remember: we chose event-driven architecture for the notification system" stays in your Knowledge Vault and surfaces in future coding sessions.
  • Project context carries over. Domain-scoped knowledge means your AI knows the difference between your work projects and personal projects.
  • Code patterns are learned. Your Instincts capture coding style preferences — naming conventions, error handling approaches, testing philosophy.
  • Task management integrated. "Create a task to refactor the auth middleware, high priority" builds your backlog without leaving the terminal.

Try Saying...

  • "Remember: the API rate limit is 100 requests per minute per user" — Stores technical knowledge for future reference
  • "What do we know about the payment service architecture?" — Searches your Knowledge Vault for relevant records
  • "Create a task to add input validation to the signup endpoint" — Adds to your task queue
  • "Save this migration plan as a spec document" — Stores a file in your File Vault

Common Issues

ProblemSolution
.mcp.json not being picked upEnsure the file is valid JSON and in the correct directory
Browser doesn't open for authCheck that Claude Code can open your default browser
"Connection timeout"Verify your internet connection and that the server URL is correct
Tools not appearingRestart Claude Code after adding the configuration

For more help, see Troubleshooting Connections.

Frequently asked questions

How do I make Tempreon available in every Claude Code project, not just one?
Add --scope user to the setup command: claude mcp add --transport http --scope user tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp. That writes Tempreon to ~/.claude.json, where Claude Code keeps user-scoped servers, so it is available in every project while staying private to your account. Do not place a .mcp.json in your home directory for this — Claude Code does not read ~/.mcp.json. A .mcp.json inside a project folder is the project-scoped file and is shared with anyone who clones that project.
I added Tempreon to .mcp.json but Claude Code doesn't recognize it.
The entry needs a "type": "http" line. That tells Claude Code it's a remote Streamable HTTP server rather than a local command — without it the server is ignored. Confirm the file is valid JSON, then restart Claude Code so it picks up the change.
How do I finish the login after adding the server?
Run /mcp inside Claude Code. The first connection opens a browser for the Tempreon consent screen; approve it and Claude Code stores the token and reconnects automatically in future sessions. If the browser doesn't open, check that Claude Code can reach your default browser.