Connect Other MCP client to AEOMCP

Other MCP client: connect to the AEOMCP MCP server with your access token, paste the workflow prompts below, and verify the setup with one prompt.

Connect

// In the shell that launches your MCP client: export AEOMCP_TOKEN=<your token>
// Then add this to your client's MCP server config (often an mcp.json file):
{
  "mcpServers": {
    "aeomcp": {
      "url": "https://mcp.aeomcp.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:AEOMCP_TOKEN}"
      }
    }
  }
}

// Fallback: if your client does not expand ${env:...}, paste the
// token directly and do not commit this file:
{
  "mcpServers": {
    "aeomcp": {
      "url": "https://mcp.aeomcp.ai/mcp",
      "headers": {
        "Authorization": "Bearer <your token>"
      }
    }
  }
}

Docs: https://modelcontextprotocol.io/specification/2025-06-18/basic/transports (verified 2026-09-07)

Verify

Paste this prompt to confirm the connection works:

Get my AEOMCP onboarding status and list the brand workspaces I can access.
Use stored data only. Do not refresh questions, generate paid analysis,
or send any reports.

Install the skills

Other MCP client has no skills folder. Copy the prompts in this guide directly into chat instead of installing a skills bundle.

Downloading is not installing. The bundle only takes effect once its files are extracted to the path above (or, for Other MCP client, once its prompts are actually used) — downloading the zip by itself does nothing.

Test the skill

Using only the AEOMCP tools get_account_context, list_workspaces, get_onboarding_status and get_client_report, tell me which brand workspaces I can access and whether a client report is ready for any of them. Do not call any other tool.

Troubleshooting

• No response / connection refused: confirm the MCP URL is reachable and the token has not been revoked.
• 401 / unauthorized: the header must read exactly Authorization: Bearer <token> — check for stray quotes or whitespace.
• Never commit a config file that contains your real token; prefer the environment-variable form.
• Still stuck? Re-read the client's own docs: https://modelcontextprotocol.io/specification/2025-06-18/basic/transports