u/Sufficient_Sir_4730

So I was noticing, that for a simple Supabase DB query, the time from when I send the message to my agent and when I receive a response, it’s 4 minutes. Is this normal?

Im sort of dissatisfied with the response time but wanted to know thoughts on whether 4 minutes is ok for a simple Supabase query via MCP. Im using Codex, whatsapp is my surface, and the query involves my main agent routing to specialist agent and reconciling the answer back to me.

The expectation i have now for my agents is to be superhuman and this is kind of a bummer!

I’m trying to connect Meta Ads MCP (`https://mcp.facebook.com/ads\`) in OpenClaw and I’m stuck at what looks like either a product gap or a Meta-side restriction.

What I’ve already verified:

- Meta OAuth / Business Login flow itself works
- I can get a fresh token successfully
- the same token works against Graph API (`/me` returns 200)
- but Meta MCP still returns:

`401 {"title":"This resource is restricted to certain users. Please verify your identity and try again","detail":"Authorization Error","status":401}`

What I found inside OpenClaw:

- MCP server UI/config supports:
- `url`
- `transport`
- `headers`
- `command`
- `args`
- `env`
- for remote MCP, it looks like a static config editor only
- I do *not* see any real OAuth-style “Connect account” / callback / token exchange flow for remote MCP servers
- transport options shown are `sse` and `streamable-http`

So right now it seems like one of these is true:

1. OpenClaw does not yet properly support remote MCP OAuth auth flows
2. Meta Ads MCP is restricted/allowlisted beyond normal Graph/API access
3. both

Questions:
- Has anyone actually made `https://mcp.facebook.com/ads\` work in OpenClaw end-to-end?
- If yes, did you use:
- static headers manually?
- some hidden OAuth connector flow?
- a patched/forked OpenClaw build?
- Is Meta Ads MCP separately allowlisted/restricted even if Graph API access works?
- Is there any OpenClaw version/build where remote MCP OAuth is properly supported in UI/runtime?

Would really appreciate concrete confirmation from anyone who has this working, because right now the docs/UI make it look configurable, but not truly connectable in an OAuth-native way.