Launch support
Get help connecting Meta, enabling ad accounts, and issuing the first MCP key.
Launch pricing: every plan starts with 7 days free
Compare plansGet help connecting Meta, issuing your first MCP key, reviewing the access model, or troubleshooting billing and operator workflows.
Whether the issue starts in Meta permissions, billing state, an MCP key, or a client configuration, the goal is to get the team to a clean audited workflow.
Get help connecting Meta, enabling ad accounts, and issuing the first MCP key.
Review token storage, team scoping, account checks, and logging behavior before rollout.
Troubleshoot billing, Meta permissions, OAuth refresh, and MCP client configuration.
Send the team name, the account you are working with, and the MCP client you are configuring. Do not send raw access tokens or full API keys.
Share API key prefixes, account names, and timestamps instead of full keys, tokens, or Meta secrets.
Short answers for teams reviewing whether EasyBissy fits their AI operating model.
No. EasyBissy sits between your team, your AI client, and Meta APIs so tool calls are scoped, checked, and logged.
No. AI clients authenticate with an EasyBissy MCP key. Meta access tokens stay encrypted at rest inside the control plane.
Yes. Connected ad accounts belong to a team, and MCP requests must resolve to an allowed account before tool execution.
Teams can sign in and prepare their workspace, but Meta connection, key creation, and tool execution require an active subscription.