1
Create a team workspace
Define ownership and keep team access, keys, operators, and connections in one place.
Launch invitation: create your first team and explore 3 months free
EasyBissy MCP
How EasyBissy turns Meta access into an MCP workflow.
The web app handles team ownership, subscription state, Meta OAuth, ad account checks, and logs. Your AI client only needs the MCP endpoint and a team key.
Access, by design
Access modelYour team. Your accounts.
Start with a team key
Each MCP client connects with its own team-scoped key.
Use authorised accounts
Tools can only use the Meta ad accounts enabled for that team.
Keep a clear record
Review tool calls and their results in the audit log.
The launch path follows five practical steps.
Each step corresponds to a real part of the EasyBissy dashboard, so operators can see what is ready and what still needs attention.
2
Activate team access
Redeem the launch code for 90 days without a card, or choose a plan when checkout is available.
3
Connect Meta securely
Use Meta Login for Business to import ad accounts, Pages, Instagram, and Threads identities.
4
Issue an MCP key
Give a scoped key to Claude, ChatGPT, or your own agent runtime without revealing Meta tokens.
5
Run audited tools
Your AI client can list accounts, inspect campaigns, and perform approved operations with logs.
A conversation, continued
Illustrative workflowInstagram comment
Does this bag come in other colours?
Comment-to-DM
Private reply
Thanks for asking! Which colour do you have in mind? We can help you find the right one.
Continue the conversation in your shared inbox when the customer replies.
What happens during a tool call.
EasyBissy performs the boring but important checks before a tool reads or changes Meta data.
The request authenticates with a team MCP API key.
The requested Meta ad account is checked against that team.
The encrypted Meta access token is resolved server-side.
Tool execution and result status are written to the audit log.
Designed around operational boundaries.
The goal is not to make AI tools omnipotent. It is to give them a narrow, observable bridge into the accounts your team explicitly enables.
Tokens stay server-side
AI clients never need the raw Meta access token. The control plane resolves it only after team and account checks.
Keys are scoped to teams
MCP API keys represent a team workspace, not a global operator identity with unrestricted Meta reach.
Calls leave a trail
Each tool call is tied to team, key, account, tool name, and status so operators can review behavior.
EasyBissy
Give every Meta signal a clear next action.
Start with seven days free, connect the assets your team actually needs, and keep every automation and AI tool inside a visible operating boundary.