Emma’s tools are available through MCP (Model Context Protocol). Any MCP-compatible client can connect to them. Three setups are documented below — pick the one that matches where you already work.Documentation Index
Fetch the complete documentation index at: https://docs.agentweb.pro/llms.txt
Use this file to discover all available pages before exploring further.
Before you begin
Sign up for an AgentWeb account at start.agentweb.pro 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.
aw_. Keep them secret.
The Claude.ai connector uses OAuth and does not require an API key.
Add Emma as a connector
- Claude.ai (Recommended)
- Claude Code
- 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
- Name:
- 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.
- 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
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
Troubleshooting
Claude.ai: authorization screen fails to load
Claude.ai: authorization screen fails to load
Claude Code: connection refused or timeout
Claude Code: connection refused or timeout
- Confirm the endpoint URL is
https://api.agentweb.pro/mcpwith no trailing slash. - Test the key by calling the endpoint with
curland 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
Claude Code: tools don't appear
- Run
claude mcp listto confirm the server is registered. - If missing, run
claude mcp remove emmaand the add command again. - Restart Claude Code. MCP servers load when a session starts.
OpenClaw: skill file doesn't load
OpenClaw: skill file doesn't load
- Open
https://api.agentweb.pro/skill.mdin 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
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.
Next steps
- Set up your brand profile before using Emma.
- Agent Mode reference for how Emma uses your Knowledge Base.