Tempr MCP Connector
One OAuth connector that routes your team's remote MCP servers through Tempr's controls
- Platforms
- API, Web
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Tempr MCP Connector
Tempr MCP Connector is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
Instead of adding each remote MCP server to claude.ai, Claude Desktop, ChatGPT or Claude Code separately, this connector gives one Tempr URL. The app signs you in to Tempr, not to each server, and every tool call then passes through Tempr with your stored credentials, your organization's Tool Packs, MCP guardrails and the request log. Only remote servers can be connectors; local stdio servers stay in your editor.
The all-servers URL exposes every server's tools prefixed by server name, such as github__create_issue, and picks up new servers automatically. A per-server URL keeps tool names and lets you switch one server on or off. Owners and admins can see and disconnect members' apps, restrict which apps may sign in and set Enterprise Managed Auth with an identity provider. Access tokens last an hour and refresh tokens lapse after 30 days unused.
Sign-in follows the MCP authorization spec with OAuth 2.1, PKCE, dynamic client registration and protected resource metadata. Tempr plans are described on its site, but the docs reviewed do not give prices.
Install
Run in a terminal
claude mcp add --transport http connector https://api.temprhq.io/mcp/connectorAdd to Settings → Connectors → Add custom connector
https://api.temprhq.io/mcp/connectorAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"connector": {
"url": "https://api.temprhq.io/mcp/connector"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"connector": {
"type": "http",
"url": "https://api.temprhq.io/mcp/connector"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"connector": {
"serverUrl": "https://api.temprhq.io/mcp/connector"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"connector": {
"type": "http",
"url": "https://api.temprhq.io/mcp/connector"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Single connector URL
- One link reaches all or one of your servers.
- Tool Packs
- Rename and describe tools your team sees.
- Guardrails and logs
- Calls are checked and logged per server.
- Connected app control
- See and disconnect apps instantly.
- Allowed apps list
- Limit sign-ins by publishing site.
- Enterprise Managed Auth
- Identity-provider assertions skip the consent screen.
- Standards-based OAuth
- OAuth 2.1 with PKCE and client metadata documents.
Good for
- Give a whole team one governed set of MCP tools in Claude
- Audit which servers an AI app called
- Restrict which AI apps members may connect
- Roll out SSO-based access to MCP servers
Pricing
Pricing unknown
Prices not published in the connector docs
Prices change. Check temprhq.io before you buy.
Tempr MCP Connector FAQ
Do local servers work?
No. Only remote servers can be connectors.
How are tools named?
With the all-servers URL they are prefixed by server, for example github__create_issue.
How long do tokens last?
Access tokens last an hour; refresh tokens lapse after 30 days unused.
Can admins revoke access?
Yes. Owners and admins can disconnect any member's app, effective at its next call.
How do I add Tempr MCP Connector to Claude Code?
Run this command in your terminal: claude mcp add --transport http connector https://api.temprhq.io/mcp/connector
What are the best alternatives to Tempr MCP Connector?
The closest alternatives to Tempr MCP Connector are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's website.
- Install steps: from the official MCP Registry entry.


