Every MCP tool call, checked against what each person may use.
Connect your MCP servers to Tempr once. Tool Packs decide which tools each person, group or key can call, guardrails check what goes into a tool and what comes back, and every member signs in as themselves, from Tempr's agents, Claude Code, ChatGPT and Claude.
jira · delete_project: "cleaning up the Q3 sandbox". Waiting for an owner on the Requests tab.Which tools, for whom, under which rules.
Tool Packs
Bundle tools per server: all of them, all except some, or only the ones you pick. Give packs to members, groups, including groups synced from your directory, or keys.
Requests for a tool
A refused call links to a page where the member asks for the tool, with a reason. Owners and admins approve or decline on the Requests tab.
MCP guardrails
Secrets and personal data in a tool call's arguments are flagged or blocked, and tool results are checked on the way back.
Pinned tool definitions
When a server changes a tool's name, description or input schema, the change goes to your audit log and your Gateway webhook.
Each member signs in
A remote server can sign each member in with their own account over OAuth. See who's signed in, and revoke one member or everyone.
Your own descriptions
Rewrite a tool's description for your organization, and every app and agent sees yours.
One set of tools, governed in every app.
One URL for ChatGPT, Claude and Claude Code.
claude.ai, Claude Desktop, ChatGPT and Claude Code can use remote MCP servers as connectors. Paste Tempr's URL and the app signs in to Tempr, not to each server; every tool call then goes through your Tool Packs, guardrails and request log.
- One connector for every server you can reach, or one per server
- See which apps each member has connected
- The same rules as Tempr's own agents
A refusal comes with a way to ask.
When a member's call is refused by Tool Packs, the error carries a link to a page where they ask for the tool. Owners and admins see requests on the Requests tab and approve, decline or revoke.
- The refusal says which tool and why
- One click to ask, with a reason
- Approve, decline or revoke later
Paid tools are refused, never paid.
When an MCP tool asks to be paid before it runs (x402 or MPP), Tempr tells the agent plainly that the tool needs payment and that Tempr doesn't pay for tools, so it stops calling it.
- The price, when the server gives one
- Later calls answered without contacting the server
- Nothing else from the payment request reaches the agent
About MCP governance.
Do I need Tempr's agents to use this?
No. Connectors bring the same Tool Packs, guardrails and logs to claude.ai, Claude Desktop, ChatGPT and Claude Code. Tempr's own agents use them too.
Where are the servers' credentials kept?
In Tempr, on the server side. Shared credentials stay there, and servers that sign each member in hold one sign-in per member, which an owner can revoke.
What happens when a server changes a tool?
Tempr pins each tool's definition. A change to its name, description or input schema is recorded in your audit log and sent to your Gateway webhook.
Connect one MCP server through Tempr today.
Then decide who gets which tools, and watch every call.