Skip to main content
Agent Loadout exposes a hosted MCP server that any compatible AI client can connect to. Point your client at the server URL, authenticate once, and the tool catalog is discovered automatically: email, vault, wallet, compute, connected apps, phone, and social in a single connection. No local software to install or maintain.

Server URL

Quick connect

Add Agent Loadout to Claude Code in one command:
Add to Claude Code
After running this, Claude Code will prompt you to authenticate. Sign in to your Agent Loadout account in the browser, choose an agent, review its permissions, and approve. The connection is live in your next chat session.

Supported clients

Claude Code

Add with claude mcp add --transport http. Works in the CLI and in the VS Code extension.

Codex CLI

Configure the MCP server URL in your Codex profile. Authentication uses the same OAuth flow.

Cursor

Add Agent Loadout as a custom MCP server in Cursor’s settings. No plugin installation needed.

ChatGPT

Enable Developer mode in ChatGPT settings, then add the server URL as a custom plugin connection using OAuth.
Any client that speaks MCP over HTTP with OAuth 2.1 will work. See the OAuth page for integration details.

Same token, same capabilities

MCP and REST operations use the same underlying services. Use whichever interface is more convenient: the same agent token, the same scoped permissions, and the same audit trail apply to both. You never need to manage two separate sets of credentials.

What happens after connecting

Once connected, your client discovers all available tools automatically. Which tools are active depends on the agent’s granted permissions and your workspace’s enabled features:
  • Email tools require email:read and/or email:send
  • Vault tools require vault:metadata, vault:use, and/or vault:write
  • Wallet tools require wallet:read and/or wallet:pay
  • Compute tools require compute:read, compute:run, and/or compute:admin
  • Connected app tools require connectors:use and a granted account
  • Phone tools require phone:read and/or phone:send
  • Social tools require social:read and/or social:post and a granted account
  • Sign-in tools require identity:sign_in; sharing the accountable owner also requires identity:share_owner
Access to a credential’s value must be explicitly enabled on the credential itself. Wallet and machine features must also be available in your workspace plan.

Learn more

MCP Tools Reference

Every tool, grouped by category, with scope requirements and descriptions.

MCP OAuth

Discovery documents, PKCE flow, token lifetimes, and scope definitions for client developers.