Skip to main content

​
Overview

Every’s Admin MCP connection lets compatible AI assistants work with the live records in your Every workspace. After you sign in with Every, you can ask ChatGPT, Claude, Codex, Cursor, and other MCP clients to look up business data or perform supported actions. The connection is for you and your team as business operators. Client self-service happens through Every’s branded client portal and public proposal or invoice pages, not through the Admin MCP.
Model Context Protocol (MCP) is an open standard for connecting an AI client to tools and data. The AI client supplies the conversation; Every supplies authenticated business tools.

​
Connection details

  • Server URL: https://admin-mcp.every.ai/
  • Transport: Streamable HTTP
  • Authentication: Every account through Clerk OAuth 2.0
  • Data scope: Your current Every organization and user permissions

​
Connect ChatGPT

Manual MCP setup requires a ChatGPT plan and workspace configuration that supports Developer mode and custom apps.
  1. Open ChatGPT → Settings → Apps → Advanced settings.
  2. Turn on Developer mode.
  3. Return to Apps and choose Add more.
  4. Enter https://admin-mcp.every.ai.
  5. Choose Add, then Connect.
  6. Sign in with your Every account and select the intended organization.
  7. Start a new chat and invoke the Every app for your request.
ChatGPT displays confirmation UI for Every tools marked as writes. Every’s server-side permission gate still applies independently of the client UI.

​
Connect Claude

​
Claude web and connectors

  1. Open Claude connector settings.
  2. Choose Add Connector.
  3. Enter https://admin-mcp.every.ai/.
  4. Authenticate with your Every account.

​
Claude Desktop with mcp-remote

Claude Desktop configurations that do not support remote HTTP directly can use the mcp-remote bridge:
Save the configuration, restart Claude Desktop, then complete the browser sign-in. This method requires Node.js.

​
Connect developer tools

Prefer one terminal login for scripts and multiple agents? The Every CLI can be used from Claude Code, Codex, Cursor, or an ordinary shell without configuring MCP in each tool.

​
Claude Code

Add the server to your project’s .mcp.json, then run /mcp and authenticate:

​
Codex

Add the same HTTP server to the MCP configuration used by Codex, then complete OAuth when prompted.

​
Cursor

Open Settings → MCP Servers → Add Server, choose HTTP, and enter https://admin-mcp.every.ai/. Cursor needs Agent mode to call MCP tools.

​
Other MCP clients

Use the server URL and Streamable HTTP transport above. The client must support remote OAuth-authenticated MCP servers.

​
What connected assistants can do

The current Admin MCP includes tools across: The exact tool list evolves. Ask the connected client to list Every’s available tools when you need to confirm whether a specific operation is supported.
Start with a read such as “Show my overdue invoices” or “Summarize my pipeline.” After you confirm the right organization and records are visible, try a draft or write.

​
Write and send safety

Every’s MCP server classifies actions before dispatch:
  • Reads run without a write confirmation.
  • Ordinary writes require an exact action-specific confirmation phrase.
  • Higher-risk actions, including external sends and destructive changes, create a short-lived approval request for the signed-in user. The approved request is bound to that organization, requester, tool, and exact normalized arguments, and can be consumed once.
Client behavior varies, so do not rely on an AI assistant’s wording alone. Read the target identifiers, recipient, amount, and other arguments shown in the confirmation or Every approval card.

Email and MCP approval guide

Learn how approvals are bound, expire, retry, and fail safely
A connected AI client can reach live business data. Remove the connector when you no longer use it, and do not approve a write whose target or details are wrong.

​
Google connection bonus for MCP signups

Organizations originally created through an MCP connection can receive the current one-time onboarding credit bonus after connecting Google with Gmail access. Open Agent → Connections to connect the account. Eligibility and the amount shown in the app are authoritative.

​
Frequently asked questions

No. Authentication uses the Every OAuth flow. The AI client receives a scoped connection token, not your password.
A send is a higher-risk action. Every creates an out-of-band approval request for the signed-in user, bound to the exact operation. Review the recipient and invoice before approval.
No. Tools read and write the live Every workspace. Disconnecting the MCP client revokes that access but does not delete the underlying Every records.
The Admin MCP is for business operators. Give customers the branded client portal or the public proposal and invoice links intended for their records.

​
Troubleshooting

Connection fails: Confirm the client supports remote OAuth MCP servers, use the server URL exactly, and allow the browser sign-in window. Tools do not appear: Disconnect and reconnect. Some clients cache tool schemas until a new session starts. Wrong organization: Disconnect, sign in again, and select the intended Every organization. Do not write until a read returns the expected records. Approval expired: Retry the exact action to create a fresh request. Changing the arguments creates a different approval identity. Need help: Contact hello@every.ai.