Claude Code Setup
Connect Tempreon to Claude Code (Anthropic's CLI) for developer workflows, automatically from your claude.ai connectors or with one command.
Ready to connect? Your Bridges page walks you through it step by step.
Open your Bridges pageOverview
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. If you sign in to Claude Code with your claude.ai account, connectors you've added at claude.ai, Tempreon included, show up in Claude Code automatically. Run /mcp to check that it's listed. If you sign in to Claude Code another way (an API key, or a cloud provider such as Amazon Bedrock), or you'd rather set it up in Claude Code directly, use claude mcp add as documented below. If you do both, Claude Code uses the server you added and hides the matching connector, so you won't get duplicates.
Quick path: already connected Tempreon at claude.ai? Sign in to Claude Code with that same account and run /mcp. Tempreon is already there. Otherwise, run claude mcp add --transport http --scope user tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp, then /mcp to approve.
Connect once at claude.ai, use it in Claude Code
If you also use Claude on the web, desktop, or mobile, the simplest setup is to connect Tempreon there once and let Claude Code pick it up:
- Connect Tempreon in Claude, from the Claude connectors directory or at claude.ai/customize/connectors, and approve the sign-in. The Claude setup guide walks through it. On Team and Enterprise plans, an Owner adds the connector for the organization first.
- Sign in to Claude Code with that same claude.ai account. Run
/loginif you're signed in another way. - Run
/mcp. Tempreon appears in the claude.ai section of the list.
That's one connection, and the same memory follows you from chat to terminal.
Claude Code only loads claude.ai connectors when you're signed in with a claude.ai account. If you sign in with an API key, an apiKeyHelper, or a cloud provider such as Amazon Bedrock, or you'd rather keep Tempreon configured in Claude Code itself, use the setup below. If you ever want Claude Code to ignore your claude.ai connectors, set "disableClaudeAiConnectors": true in your Claude Code settings.
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.jsonis 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:
- A browser window opens with the Tempreon consent screen
- Log in if prompted
- Review and approve the connection
After approving, Claude Code will store the authorization token and reconnect automatically in future sessions. If the browser doesn't open, copy the link Claude Code shows and open it yourself. You can also sign in from your terminal with claude mcp login tempreon.
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.
- One connection for chat and terminal. Connect Tempreon once at claude.ai and sign in to Claude Code with the same account. A decision you saved while planning in chat is there when you start coding.
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
| Problem | Solution |
|---|---|
.mcp.json not being picked up | Ensure the file is valid JSON and in the correct directory |
| Browser doesn't open for auth | Copy the link Claude Code shows and open it yourself, or run claude mcp login tempreon from your terminal |
| "Connection timeout" | Verify your internet connection and that the server URL is correct |
| Tools not appearing | Restart Claude Code after adding the configuration |
Connected Tempreon at claude.ai, but it isn't in /mcp | Run /status to check how you're signed in. Claude Code loads claude.ai connectors only when you sign in with a claude.ai account, not with an API key, an apiKeyHelper, or a cloud provider. Switch with /login, or add Tempreon with claude mcp add. Also check the Show unused connectors row at the end of the claude.ai section |
/mcp lists the Tempreon connector as hidden | You also added Tempreon in Claude Code, and the server you added takes precedence over a connector at the same URL. Either one works. If you'd rather use the connector, /mcp shows how to remove the duplicate |
For more help, see Troubleshooting Connections.
Frequently asked questions
- I already connected Tempreon in Claude on the web or desktop. Do I need to set it up again in Claude Code?
- Usually not. If you sign in to Claude Code with the same claude.ai account, connectors you added at claude.ai, Tempreon included, are available in Claude Code automatically. Run /mcp to check that Tempreon is listed in the claude.ai section. Claude Code only loads them under a claude.ai sign-in. If you use an API key, an apiKeyHelper, or a cloud provider such as Amazon Bedrock, add Tempreon with claude mcp add instead. Run /status to see which sign-in is active.
- 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, copy the link Claude Code shows and open it yourself. You can also sign in from your terminal with claude mcp login tempreon.