Connect your agent

One address and one sentence. Your coding agent signs in through your browser, then reaches what you connected and runs your runbooks.

Attemper runs your agent's calls to the services you connected, under your rules: a call that changes something can wait for your yes, and every call that runs leaves a receipt. A runbook your agent did once runs again the same way, from your agent, your app, a webhook, a schedule or a watcher.

Your first screen in Attemper gives you one sentence to tell your agent: Connect to Attemper. Follow https://attemper.com/connect. This is the page that sentence points to.

The address

Agents connect at https://mcp.attemper.com. To pin an agent to one workspace, add the workspace's slug: https://mcp.attemper.com/<slug> (each workspace's address is shown under Settings, Workspace).

Connect from your agent

Works with any coding agent that connects to remote MCP servers. Add the address as a remote MCP server, sign in when your browser opens, and allow the connection. Nothing to paste: your agent finds the sign-in at the address.

No account yet? Create one when the browser opens, with Google, GitHub or your email, and you come back to Allow.

Claude Code

Add, in a terminal (--scope user keeps it for every project; without it, this project alone):

claude mcp add --scope user --transport http attemper https://mcp.attemper.com

Sign in: run claude mcp login attemper, or in Claude Code run /mcp, choose attemper, then Authenticate. Your browser opens; allow the connection.

We ran these commands ourselves; the /mcp menu steps are from Anthropic's own docs.

Codex

Add, in a terminal (Codex keeps it for every project):

codex mcp add attemper --url https://mcp.attemper.com

Sign in: Codex may start the sign-in as it adds the server; if it did not, run codex mcp login attemper, or /mcp login attemper inside a Codex session. Your browser opens; allow the connection.

From OpenAI's own docs; we have not run it here yet.

Gemini CLI

Add, in a terminal (-s user keeps it for every project; without it, this project alone):

gemini mcp add -s user --transport http attemper https://mcp.attemper.com

From Google's own docs; we have not run it here yet.

VS Code

Add: open the Command Palette, run MCP: Add Server, choose HTTP, paste the address, name it attemper and choose Global, then Copilot Global, when asked where to keep it. Or, the older per-workspace form, write it in .vscode/mcp.json:

{ "servers": { "attemper": { "type": "http", "url": "https://mcp.attemper.com" } } }

Sign in: when the server first starts (your first chat message, or Start Server from MCP: List Servers), VS Code asks to sign in; say yes, and your browser opens; allow the connection.

Sign in again: run MCP: List Servers, choose attemper, then Start Server (or Restart Server while it runs); starting asks for the sign-in again when the old one is gone.

From Microsoft's own docs; we have not run it here yet.

Cursor

Add, in .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project, then restart Cursor:

{ "mcpServers": { "attemper": { "url": "https://mcp.attemper.com" } } }

Sign in: open Customize in the sidebar, then MCPs, and follow the sign-in prompt on the attemper row; your browser opens; allow the connection. From Cursor's CLI, agent mcp login attemper does the same.

From Cursor's own docs; we have not run it here yet.

Any other agent

Any other agent that speaks MCP over Streamable HTTP with OAuth connects at the same address: add it as a remote MCP server, then sign in the way that agent does.

Check

Ask your agent to read connections. The reply lists what you connected, and the greeting Attemper sends it says what to do next.

A sign-in lasts until your agent loses it. Sign in again the way your agent does; each section above says how. Your browser opens on Allow again.

For your agent's instructions file

Paste this into AGENTS.md or CLAUDE.md in your project. It is optional: the server itself tells your agent how to work, and read guide explains the rest by topic.

## Attemper
Use the attemper tools for every connected service.
- read guide with topic start explains how Attemper works; you need no other file.
- Start with read connections to see what you can reach.
- A call that changes something may pause for the owner's approval. While one is waiting, do not make another call to a connection or a runbook: that abandons the waiting one. read pending shows what is waiting.
- Never ask for, read or paste an API key. The owner adds connections in Attemper.

What your agent may do on its own

Your agent asks before it saves or changes a runbook, before it adds an entry point or a keyless connection, and before it changes things on a connection on its own, unless you turn on the matching permission on its page under Entry points: Save and edit runbooks, Add entry points and connections or Make changes through connections. It asks in its chat, and answering always there turns the permission on. A runbook it runs follows the runbook's own marks. A key, a sign-in and a step marked "ask me first" stay yours whatever it says.

This page as plain text, for an agent: https://attemper.com/docs/reference/agents.md.

Connect your agent

On this page