Skip to main content
Emma’s tools are available through Model Context Protocol (MCP). Any MCP-compatible client can connect to them. Four setups are documented below. Pick the one that matches where you already work.

Before you begin

Sign up for an AgentWeb account at app.agentweb.pro/register if you don’t have one. For Claude Code and OpenClaw, generate an API key:
  1. Open app.agentweb.pro.
  2. Go to Settings → API Keys.
  3. Click Generate.
API keys start with aw_. Keep them secret. Claude.ai uses OAuth and does not require an API key. Other MCP clients can also use OAuth when they support browser authorization and PKCE. Codex uses a plugin generated by Plugin Creator.
1

Add Emma as a connector

2

Use Emma in any chat

Open a conversation in your connected client. Emma’s tools are available automatically. Try:
  • “Emma, what’s in my brand guidelines?”
  • “Pull my latest Meta campaign performance and tell me what to cut.”
  • “Draft three LinkedIn posts in my founder voice about [topic].”
  • “Search my CRM for leads who haven’t replied in two weeks.”

OAuth from a remote or headless client

Some OAuth-capable MCP clients run on a different machine from your browser. They may print an authorization URL instead of opening a browser automatically.
  1. Start the client’s OAuth connection command in a persistent terminal or PTY. Keep that process and its standard input open.
  2. Open the authorization URL in your browser.
  3. Sign in to AgentWeb, review the requested access, and approve the connection.
  4. AgentWeb redirects the browser to a loopback URL such as http://127.0.0.1:<port>/callback?code=...&state=....
  5. If the browser cannot open that page, copy the complete URL from the address bar. The connection failure is expected when the browser and MCP client are on different machines.
  6. Return the complete callback URL to the original waiting process using the client’s callback-paste or standard-input mechanism.
  7. Complete any tool-selection prompt, then use the client’s connection test or server list to verify that Emma’s tools were discovered.
Do not start a second OAuth command while authorization is in progress. The callback is bound to the state and PKCE verifier held by the original process. Treat the callback URL as a short-lived credential. Do not save it in logs or issue trackers.
If the authorization window expires, start a new OAuth command and use its new authorization URL.

Verify the connection

Paste this prompt into any session with Emma to confirm tools are wired up correctly:

Verify Emma is connected

If Emma returns brand details or names the right tool, the connection is working.

Troubleshooting

  • Make sure you’re signed in to AgentWeb in the same browser. OAuth requires an active session cookie.
  • If you have multiple AgentWeb accounts, sign out and sign in with the account you want connected.
  • If the redirect doesn’t complete, try an incognito window or disable browser extensions.
  • Confirm the endpoint URL is https://api.agentweb.pro/mcp with no trailing slash.
  • Test the key by calling the endpoint with curl and the same authorization header. A 200 response confirms the key works.
  • Some corporate networks block Streamable HTTP. Try a different network to rule this out.
  1. Run claude mcp list to confirm the server is registered.
  2. If missing, run claude mcp remove emma and the add command again.
  3. Restart Claude Code. MCP servers load when a session starts.
  1. Confirm the Emma plugin is installed and enabled in Codex.
  2. Open the plugin and confirm MCP server URL is https://api.agentweb.pro/mcp.
  3. Start a new Codex thread. MCP tools are loaded when a thread starts.
  4. If the plugin was created with the wrong URL, create it again in Plugin Creator with the values above.
  • Open https://api.agentweb.pro/skill.md in a browser to confirm it returns markdown.
  • Confirm the API key in OpenClaw matches the one in the portal. Whitespace counts.
  • “Unknown tool” errors usually mean a stale skill file. Reload it.
  1. Go to Settings → API Keys in the portal.
  2. Click Revoke on the compromised key.
  3. Click Generate to create a new key.
  4. Update Claude Code (claude mcp remove emma, then add again) or OpenClaw with the new key.
The revoked key stops working immediately.

Next steps

Last modified on September 11, 2026