Connect Emma

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:

Open app.agentweb.pro.
Go to Settings → API Keys.
Click Generate.

API keys start with aw_. Keep them secret. Claude.ai uses OAuth and does not require an API key. Codex uses a plugin generated by Plugin Creator.

Add Emma as a connector

Claude.ai (Recommended)
Claude Code
Codex
OpenClaw

Open claude.ai and go to Settings → Connectors.
Click Add custom connector.
Fill in the fields:
- Name: Emma
- MCP server URL: https://api.agentweb.pro/mcp
Click Connect. Claude.ai redirects you to AgentWeb’s authorization screen.
Sign in to AgentWeb if prompted.
Review the scopes being granted, then click Authorize.

The scopes Emma requests:

Use Emma’s MCP tools on your behalf
Read AgentWeb data (campaigns, content, leads, schedules)
Send messages on connected accounts (LinkedIn, Gmail, etc.)
Manage schedules and run workflows

Same connection model Claude.ai uses for Gmail, Notion, and Slack. No CLI to maintain, no key to rotate.

In your terminal:

claude mcp add \
  --transport http \
  emma \
  https://api.agentweb.pro/mcp \
  --header "Authorization: Bearer aw_YOUR_API_KEY_HERE"

Argument	Description
`--transport http`	Emma’s MCP server uses Streamable HTTP.
`emma`	A local alias for the connection. Any name works.
`https://api.agentweb.pro/mcp`	Emma’s MCP endpoint.
`--header`	Your AgentWeb API key as a bearer token.

Verify with claude mcp list — emma should appear.

Claude Code stores your API key in ~/.claude.json. Do not commit this file. If a key leaks, revoke it in Settings → API Keys.

Create an Emma plugin in Codex:

Open Codex.
Open Plugin Creator.
Choose the option to create a plugin from an MCP server.
Fill in the fields:
- Name: Emma
- MCP server URL: https://api.agentweb.pro/mcp
Create the plugin.
Install or enable the generated Emma plugin when Codex prompts you.

Plugin Creator packages the MCP server as a Codex plugin. New Codex threads can then load Emma’s tools from that plugin.

Field	Value
Name	`Emma`
MCP server URL	`https://api.agentweb.pro/mcp`

Start a new Codex thread after installing the plugin. MCP tools are loaded when a thread starts.

Do not add Emma as a raw codex mcp server unless AgentWeb support asks you to. Use Plugin Creator so Codex can package and install the MCP server as a plugin.

Copy your API key from Settings → API Keys in the portal.

Add the key to OpenClaw:

openclaw config set agentweb_api_key aw_YOUR_API_KEY_HERE

Load Emma’s skill file from https://api.agentweb.pro/skill.md.

The skill file declares Emma’s tools. OpenClaw reads it and registers them for use in any channel it’s connected to — Slack, WhatsApp, Telegram, Discord.

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.”

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

Claude.ai: authorization screen fails to load

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.

Claude Code: connection refused or timeout

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.

Claude Code: tools don't appear

Run claude mcp list to confirm the server is registered.
If missing, run claude mcp remove emma and the add command again.
Restart Claude Code. MCP servers load when a session starts.

Codex: tools don't appear

Confirm the Emma plugin is installed and enabled in Codex.
Open the plugin and confirm MCP server URL is https://api.agentweb.pro/mcp.
Start a new Codex thread. MCP tools are loaded when a thread starts.
If the plugin was created with the wrong URL, create it again in Plugin Creator with the values above.

OpenClaw: skill file doesn't load

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.

Revoke a leaked API key

Go to Settings → API Keys in the portal.
Click Revoke on the compromised key.
Click Generate to create a new key.
Update Claude Code (claude mcp remove emma, then add again) or OpenClaw with the new key.

The revoked key stops working immediately.

Next steps

Set up your brand profile before using Emma.
Agent Mode reference for how Emma uses your Knowledge Base.

Onboarding

Reference

Playbooks

Connect Emma

Before you begin

Verify the connection

Troubleshooting

Next steps

​Before you begin

​Verify the connection

​Troubleshooting

​Next steps

Before you begin

Verify the connection

Troubleshooting

Next steps