How can we help you?

FROGED MCP connects a compatible AI assistant to your FROGED workspace. You can ask questions about customers, find information and perform supported actions using natural language. The assistant can only work with the workspace and permissions you authorize.

Before you start

• A FROGED account with access to the workspace you want to connect.
• An AI assistant or client that supports remote MCP servers over HTTP and OAuth sign-in. The menus and available features depend on your client.
• The permissions and plan required for the actions you want to perform in FROGED.

Connect with your FROGED account

1. Open your assistant’s settings for connectors, integrations or MCP servers, and add a remote connection.
2. Name the connection FROGED and enter this server URL: https://mcp.froged.com/mcp.
3. Choose OAuth or the sign-in option. Your assistant opens FROGED in your browser.
4. Sign in with your usual FROGED account. If you are already signed in, you may go straight to the authorization screen.
5. Review the requesting application, select the correct workspace and choose the permissions to grant. For a first connection, start with read access if you only need to consult information.
6. Authorize the connection and return to your assistant. Ask it to list the available FROGED actions or try a simple read request.

Each connection is tied to the selected workspace. To work with a different workspace, create a separate connection for it. You do not need to register your assistant in Auth0.

Choose the right permissions

• Read: consult supported information, such as contacts, conversations, articles and reports.
• Write: create or update supported records and drafts.
• Send: perform supported sending or activation actions, including activating automatic messages or behavioral emails. Creating or editing an active automatic message also requires this permission.
• Delete: delete supported items.

MCP permissions do not replace your existing FROGED permissions or plan. An action must be allowed by both. Changes and sending actions can affect real customers: specify the target clearly and review the proposed content before asking the assistant to execute it. Confirmation behavior depends on your assistant; FROGED does not add a separate confirmation screen for every operation.

What can I do?

The current catalog covers contacts, accounts, conversations, knowledge base, inboxes, events, campaigns, metrics, agents, automation, feedback, updates, automatic messages and behavioral emails. Campaign operations use the current campaigns system; legacy campaigns are not exposed.

The server currently provides 223 operations across 14 areas. By default, clients see 28 tools, including tools to discover and execute the wider operation catalog. A tool is an entry point; it does not necessarily represent just one action. Availability can vary with your permissions and workspace features.

Examples to try

• “Find this customer by email and summarize their recent conversations.”
• “Find the help articles about connecting WhatsApp and prepare a reply using them.”
• “Add this note to the contact we just reviewed.”
• “Show me the available campaign reports for this period.”
• “Create an inactive automatic-message draft with this text. Do not activate it.”

Provide exact names, identifiers, dates or filters when possible. Ask the assistant to show the target before making a change if there could be more than one match.

Long lists, including the knowledge-base index, are returned in pages. Ask the assistant to continue through the remaining pages when you need a complete list, and to open a specific article for its full content.

Does the connection renew automatically?

The access token lasts up to 8 hours. Compatible clients renew it automatically using a rotating refresh token, so you do not need to sign in every 8 hours. There is no fixed requirement to reconnect every 30 days if renewal remains active.

The current connection policy requires authorization again after 30 consecutive days without a successful renewal, or 180 days after the original authorization. Revoking the connection, losing workspace access or invalidating the authorization can also require you to reconnect. A client that does not support token renewal may ask you to sign in earlier.

Review or disconnect an assistant

In FROGED, open My Profile → MCP connections, or visit MCP connections. Review your connections and revoke any you no longer use. Revocation stops their access and future renewals. To change the workspace or permissions, connect again and revoke the connection you are replacing.

Alternative: connect with an API key

If your client supports custom HTTP headers, you can authenticate with an existing FROGED API key instead of OAuth. Your workspace must have API access available in its plan. Use the same server URL and configure these headers in the client’s secure credential settings:

• X-Froged-Api-Key: your workspace API key.
• X-Froged-Workspace: your workspace slug.

Do not put an API key in the server URL, prompts or shared screenshots. API keys do not use the OAuth renewal flow; manage or revoke the key through FROGED. OAuth is the recommended option when your client supports it.

Troubleshooting

• The sign-in page does not open: check that the client supports remote HTTP MCP and OAuth, and that the URL ends in /mcp.
• The workspace is missing: confirm that you are signed in with the account that belongs to that workspace.
• Permission denied: check the connection scopes, your agent permissions and workspace plan. Reconnect if you need to authorize different scopes.
• Connection expired or revoked: remove or reconnect it in the assistant and authorize it again in FROGED.
• An action is not listed: ask the assistant to search the operation catalog. If the capability is not supported by the catalog or your client, use the corresponding area in FROGED.
• A send or update times out: check the result in FROGED before retrying, to avoid duplicate actions.

For help, contact FROGED support with the client name, approximate time and error message. Do not include tokens, API keys or confidential customer content.