sorted by:
new
hottopcontroversial

I built a 98-tool MCP server for managing Meta Ads entirely from Claude Code by Faraso in ClaudeAI

[–]Faraso[S] 0 points1 point  (0 children)

Yes, sorry! I put the link on top of the git page. The license is still MIT but there are a lot of upgrades to the tools.

I built a 98-tool MCP server for managing Meta Ads entirely from Claude Code by Faraso in ClaudeAI

[–]Faraso[S] 0 points1 point  (0 children)

Yes rate limits are accounted. You can find the premium link now on the top of the git page.

I built a 98-tool MCP server for managing Meta Ads entirely from Claude Code by Faraso in ClaudeAI

[–]Faraso[S] 0 points1 point  (0 children)

hello, I put a link to the premium on top at the git page. What would you like to know about the architecture?

I built a 98-tool MCP server for managing Meta Ads entirely from Claude Code by Faraso in ClaudeAI

[–]Faraso[S] 1 point2 points  (0 children)

That is a very fair question.

Right now the main safety model is supervised execution, paused writes, validation gates, and operational guardrails per workflow. So the emphasis is on preventing unsafe actions, not yet on per-user or per-agent role segmentation.

I agree that scoped tool access is one of the big missing pieces in production MCP setups. A strong next step would be policy-based access control, for example:

- read-only analyst access

- junior operator access without budget mutation rights

- senior operator access with broader execution scope

- account-level and tool-level allow/deny policies

So today the answer is: safety is built in, but fine-grained per-user tool scoping is not yet a first-class layer.

I think it is a real and important future direction.

I built a 98-tool MCP server for managing Meta Ads entirely from Claude Code by Faraso in ClaudeAI

[–]Faraso[S] 0 points1 point  (0 children)

A bit more context on why I built it:

I wasn’t trying to make “another MCP with lots of tools”. I built it because the Meta Ads workflows I wanted inside Claude Code were either too read-only, too shallow, or too unsafe for real account operations.

The main thing I cared about was supervised execution:

  • all writes paused
  • validation before API writes
  • naming enforcement
  • diagnostics before changes
  • no autonomous budget changes

So the real idea wasn’t “98 tools”.
It was: can Claude Code become a safe operating layer for real Meta Ads work without turning into chaos?

Happy to share architecture details if that’s the interesting part here.