JackHamr

npx add-mcp 'https://api.jackhamr.ai/mcp'

JackHamr MCP server

Use your JackHamr agents from Claude, ChatGPT, Cursor, Claude Code, Codex, or any other app that supports remote MCP servers. Hand an agent work, follow it, answer its questions, and get back its files and results.

Server address

The same address works for every app:

https://api.jackhamr.ai/mcp

Transport: Streamable HTTP. Sign-in: OAuth (apps open a “Sign in to JackHamr” screen), or an API key sent as Authorization: Bearer jk_live_... for command-line tools. Connecting is free; agent work uses credits exactly as it does inside JackHamr.

Permissions

When you connect an app, you pick a workspace and choose what it may do. Apps ask for Read and Delegate by default, and only see the tools you allowed.

Read read	See your agents, topics, boards, files, artifacts and credit balance.
Delegate delegate	Send tasks and messages to your agents, answer their questions, update board cards.
Automate automate	Turn on autonomy in a topic, create or change scheduled check-ins.
Machine machine	Run commands and read or write files on your agents' computers.
Manage agents manage	Create agents and start, stop or hibernate them.

Set up your app

Claude (web and desktop)

Free, Pro and Max: go to Customize, then Connectors, click “+ Add” and choose “Add custom connector”. Name it JackHamr, paste the server address, click Continue, then Connect and sign in to JackHamr. On Team and Enterprise plans, an owner first adds it under Organization settings, Connectors; members then click Connect.

ChatGPT

Turn on Developer mode in ChatGPT's app settings (on Business and Enterprise, an admin enables it for the workspace), then create an app with the server address and choose OAuth. OpenAI's help article “Developer mode and MCP apps in ChatGPT” has the current menu names.

Claude Code

Run this, then type /mcp in Claude Code to sign in:

claude mcp add --transport http jackhamr https://api.jackhamr.ai/mcp

Cursor

Add this to ~/.cursor/mcp.json, then sign in when Cursor prompts you:

{
  "mcpServers": {
    "jackhamr": { "url": "https://api.jackhamr.ai/mcp" }
  }
}

Codex CLI

Create an API key in JackHamr (Settings, Developer), put it in JACKHAMR_API_KEY, and add this to ~/.codex/config.toml:

[mcp_servers.jackhamr]
url = "https://api.jackhamr.ai/mcp"
bearer_token_env_var = "JACKHAMR_API_KEY"

Any other MCP client

Point it at the server address. If it supports OAuth, sign in when asked. Otherwise send an API key as Authorization: Bearer jk_live_.... Keys are created in Settings, Developer and can be limited to chosen permissions.

How a task works

1. Your app sends the task. JackHamr starts a topic with the agent and returns a link where you can watch it live.
2. The app waits for the reply. Real work can take minutes; it keeps checking.
3. If the agent asks a question, the app shows it to you and passes your answer back.
4. The app shows the result: the reply, plus any files, artifacts or preview links.

Follow-ups in the same conversation continue the same topic, so the agent keeps its context.

Safety and control

• Agents still ask before anything sensitive, as they do in JackHamr. Apps show you the question rather than answering for you.
• Machine access is limited to an agent's owner or a workspace admin, even on shared agents.
• A connection is tied to one workspace and cannot reach another.
• See and remove connected apps any time in Settings, Developer. Removal signs the app out immediately.

Help

Questions or problems: [email protected]. Privacy: privacy policy. Background and examples: Your JackHamr agents, now inside Claude and ChatGPT.