Meta on October 26, 2026 added six tools to its Social Technologies MCP server that allow AI coding agents to create a Meta app, find or create a Business Portfolio, link the two and attach a use case such as WhatsApp Business messaging, according to a post by Zoë Lieberman on the Meta for Developers blog. Four of the six tools write to a developer's account, and each of those asks for confirmation before it acts. The server launched on June 30, 2026 under the name Developer Tools MCP as a mostly read-only window into app configuration; with this update, it starts doing setup work that until now required a series of visits to Meta's developer dashboard.

In Short

Meta has a connector that lets AI helpers such as Claude, ChatGPT, Codex and Cursor check the settings of apps built on Facebook, Instagram and WhatsApp and help debug them, and it can now create those apps and the business accounts that own them too. This matters to agencies, software vendors and businesses that build on Meta's tools, because setting up an app used to mean clicking through several dashboard screens. The AI helper still has to ask before every change, it never sees the app's secret key, and the new tools are reaching accounts gradually.

What Meta added on October 26

An MCP server is a connector built on the Model Context Protocol, the open standard through which AI applications discover and call outside tools. The October 26 post frames the change as the next step after a launch in which Meta's server could only answer questions. "When we launched Social Technologies MCP, it could answer questions about your Meta app integrations," the post states. "Now, the server can do the setup too, from creating an app to creating a new business, linking them and then adding a new usecase, everything can be done via the MCP."

According to Meta, "Six tools span the app lifecycle." The blog post lists them by function only. Meta's Social Technologies MCP documentation gives the names, all of which keep the devtools_ prefix inherited from the server's original identity:

  • devtools_app_create creates a new app. According to the documentation, the app starts in development mode with no use cases and no Business Portfolio attached, and the tool returns an app ID.
  • devtools_business_list lists the Business Portfolios the developer has granted the server access to, and whether assets can be added to each.
  • devtools_business_create creates a Business Portfolio when none of the existing ones fits. The documentation says it requires the optional business_management permission, and that declining that permission does not affect the other tools.
  • devtools_app_business_manage links an app to a portfolio. Per the documentation, an app already owned by a different portfolio is rejected, because the server does not move apps between owners.
  • devtools_app_use_cases lists the use cases already configured on an app and those still available to add. It only reads.
  • devtools_app_use_cases_manage adds a use case, such as WhatsApp Business messaging. The documentation states that adding a use case grants the privileges that come with it and that the server cannot remove it afterwards.

That accounts for the "four write-tools" the post mentions: app creation, portfolio creation, linking and adding a use case. The two remaining tools only read.

A dashboard sequence turned into one request

Meta illustrates the flow with a short exchange. A developer types: "Set me up with a new app for WhatsApp Business messaging." The agent replies: "I will create an app called 'Support Bot', link it to your 'Acme Co' Business Portfolio, and then add the WhatsApp Business messaging use case. I will ask for confirmation before each enabled write." The developer answers "Go ahead."

"What used to be a sequence of dashboard visits is now a sentence," the post states.

The example lands at a busy moment for WhatsApp integrations. On October 21, 2026, five days before this post, Meta set October 13, 2027 as the date the WhatsApp Cloud API stops delivering marketing messages, pushing promotional templates onto the separate Marketing Messages API. Businesses and software vendors that send WhatsApp marketing templates face that migration over the next year, and app configuration is part of the work. Meta has not said whether the Marketing Messages API, or any specific WhatsApp use case beyond "WhatsApp Business messaging", appears in the list of use cases the new tool can add.

Confirmations and secrets

Every write needs a human yes. "We are introducing four write-tools. Your agent will ask you for confirmation," according to the post. The safeguard matters because an agent acting on instructions it reads from documents, web pages or error messages can be steered by text it should have treated as data, the attack known as prompt injection. A confirmation step puts a person between the agent's plan and the change to the account.

The post also addresses the most sensitive value an app holds. According to Meta, app creation "never returns your app secret". The secret must be retrieved from the App Dashboard. "Secrets will not be shared via an agent conversation," the post states. The documentation adds that the secret stays behind re-authentication in the dashboard.

Limits and rollout

Creation is rationed. The October 26 post says app and Business Portfolio creation "have per-user safety limits" without giving a number. Meta's documentation is more specific: creating an app and creating a Business Portfolio are each limited to 15 calls per day.

Attempts that go nowhere still count. "Failed validation and declined or timed-out confirmations may consume an attempt, so avoid repeated retries and follow the error guidance," the post states. A developer who declines an agent's proposed app three times, in other words, has used three of the day's 15.

Availability is uneven. "These tools are rolling out gradually and might not be available to all users today," according to the post. According to Meta, developers who already have the server connected need to reconnect before the agent can discover the new tools. Meta's documentation goes further than the blog: it labels the six lifecycle tools as coming soon and says they are not available yet and will not appear in an agent's tool list until they reach the account. The same documentation page still describes webhooks as the only area the server can write to. The two Meta sources therefore disagree on whether the tools are live, and Meta has given no date for full availability.

What the server did before October 26

The server first appeared on June 30, 2026, in a post also written by Lieberman. A note added to that post says that "As of August 18, 2026, we are now referring to this MCP as Meta Social Technologies MCP. This was previously known as Developer Tools MCP." The endpoint and the devtools_ prefix did not change with the rename, according to the documentation, so existing configurations kept working.

The June post opened with a description of the problem the server addresses: searching documentation for the right endpoint, checking the developer dashboard for required actions and working out why an API call fails. "This context switching pulls you out of your code," it states.

PPC Land reported on the launch on July 5, 2026, describing a beta remote server at mcp.facebook.com/devtools, built on Streamable HTTP, with 10 tools. All of them read, except two that handled webhooks. The June post describes five capabilities.

Discovery, troubleshooting and app health

API discovery. A developer describes a use case, and the server returns relevant Graph API endpoints, required permissions and code samples in the relevant programming language. Meta's example prompt is "Help me setup an integration for Whatsapp business".

Troubleshooting. A developer pastes an API error into the agent, and the server, according to Meta, "references live platform logic, changelog history, and known error patterns to deliver specific resolution steps."

App status and health. The server exposes app settings, platform details, API usage and health status without a login to the developer dashboard, so a developer can tell whether a problem sits in their code or their platform setup.

Compliance deadlines and webhooks

Required actions. "Data Access Renewal deadlines shouldn't catch you off guard," the June post states. Data Access Renewal is the annual compliance review that Meta announced in August 2024, folding data handling questions, the Data Use Checkup, App Review, the Data Protection Assessment and ongoing reviews into one process, with a phased rollout from October 2024. According to Meta, the server surfaces compliance status, required actions and enforcement timelines, so that the agent "proactively flags what needs attention and when action is required" instead of a developer learning about lost access from a missed email.

Webhook debugging. The agent can inspect webhook subscriptions and troubleshoot delivery problems. Before October 26, webhook subscriptions were the only thing the server could change.

Eleven core tools now listed

The current documentation lists 11 core tools, one more than at launch. The addition is devtools_skill_invocation, which the documentation describes as advisory start and end markers that read and change nothing. Its name lines up with the October 26 post's closing note: "We are adding new skills and plugins to the Github repo to help enable integrations." The repository the post links to is facebook/agentic-tools on GitHub.

Sign-in and supported clients

The June post lists three steps: install the configuration, "Authenticate with your Meta app credentials", then ask the agent what tools exist with list_tools. The documentation describes the sign-in differently. It uses OAuth with a Meta developer account, no App ID or App Secret goes into the client's configuration, and the developer chooses which apps to grant during sign-in. Read scope covers app configuration, App Review, compliance, API usage and webhooks; Manage scope adds webhook writes. The sign-in has to be repeated whenever the client restarts.

The documentation covers setup for Claude Code, Claude Desktop, the OpenAI Codex app, ChatGPT in Developer Mode, and Cursor's app and command-line tool. Clients that only support local servers can use a bridge called mcp-remote. Both posts name the same four families of agents: Claude, Cursor, Codex and ChatGPT. "The availability of tools are limited and subject to change," the June post states.

What Meta's feedback form asks

Both posts link to a feedback form, hosted on Google Forms and marked as created inside Meta. It offers a view of what Meta is measuring and what it is considering building next.

The form asks for an overall rating from 1, "Very frustrating", to 5, "Excellent". It asks which clients people connect through, with seven options: Claude Web, Claude Code, Codex App, Codex CLI, ChatGPT, Cursor App and Cursor CLI. It asks which tools were used, listing ten names from devtools_discovery to devtools_api_changelog. None of the six lifecycle tools appears in that list.

One question points to possible next steps. "Which of these tools would you be more interested in seeing next?" the form asks, offering two answers: "CLI" and "Bring your own app to connect to this MCP". Meta already offers a command-line tool on the advertising side: the Ads CLI it released on April 29, 2026, which wraps the Marketing API for developers and agents. A developer-platform equivalent would be new. The second option suggests Meta is weighing whether developers could connect the server through an app of their own; Meta has not described such a feature publicly.

The form also asks respondents for their role at their company and, optionally, an email address.

One detail in the June post gets no explanation. The sentence introducing the server says it connects "your Service Provider AI coding agent (Claude, Cursor, Codex, ChatGPT)" to Meta developer platform information, and the words "Service Provider" link to the service provider section of Meta's Platform Terms.

That section places obligations on developers, not on Meta. Under the terms, a developer must obtain a service provider's written agreement to use Platform Data only on the developer's behalf and at their direction before using it, must make sure the provider complies with the terms, must have the provider delete the data when the relationship ends, and must supply Meta on request with a list of providers and the data shared with them. Developers are liable for their service providers' acts and omissions. Meta can also prohibit a specific service provider.

Does a developer need a written agreement with Anthropic, OpenAI or Cursor before pointing their agent at an app's data? Neither post says. The link alone signals how Meta classifies these tools under its terms. With the October 26 update, that question carries more weight: the agent now creates apps, creates business entities and grants privileges, rather than only reading settings.

Why this matters for marketers

Business Portfolios, the structure Meta previously called Business Manager, are where companies hold ad accounts, Pages, datasets and apps. An agent that can create a portfolio and attach an app to it is working inside the same ownership layer that governs advertising assets, even though none of the six tools touches campaigns.

That layer already gates Meta's advertising agents. When Meta opened its Ads MCP server to any developer with a Meta app on July 16, 2026, setup ran through a use case in the developer dashboard called "Create and manage ads with ads MCP server", and agencies and partners needed App Review and Advanced Access on the ads_mcp_management permission. Adding use cases to an app is now one of the things the Social Technologies MCP can do. Whether that particular use case can be added through the server, or whether App Review steps can be started from it, Meta has not said.

The October 26 post also points developers to Meta's other servers: Ads MCP, WhatsApp Business Tools MCP and Instagram Business MCP. Meta's MCP overview page lists Ads MCP and WhatsApp Business Tools MCP as remote servers alongside Social Technologies MCP; Instagram Business MCP is not on it. Together they form a growing set of MCP endpoints covering ads, messaging and the developer platform itself.

The scope of Meta's write access differs from the servers other ad platforms have released. Google released an open-source MCP server for its Ads API on October 7, 2025 that was read-only, with tools for search and for listing accessible accounts. Microsoft expanded its Advertising MCP server to an open pilot on June 17, 2026, also read-only. Amazon opened its Ads MCP server to an open beta on February 2, 2026, with examples that included creating advertiser accounts and launching Sponsored Products campaigns. Meta's Ads AI Connectors, launched April 29, 2026, could create and edit campaigns from the first day. Meta now extends write access below the campaign level, to the app and business entities that advertising integrations depend on.

For agencies and martech vendors that build and maintain many Meta apps, the shift is practical. App creation, portfolio linking and use case setup recur with each new integration, and they are the kind of work agentic AI tooling is designed to take over. The 15-a-day cap on creation, the confirmation for every write and the inability to remove a use case once added set the boundaries of that delegation.

Timeline

Summary

Who: Meta, through its Meta for Developers blog and posts by Zoë Lieberman, and the developers, agencies and software vendors that build on Meta's APIs using AI coding agents such as Claude, Cursor, Codex and ChatGPT.

What: Meta added six app lifecycle tools to Social Technologies MCP, the server formerly called Developer Tools MCP. They let an agent create an app, list or create Business Portfolios, link an app to a portfolio, and list or add use cases. Four of the six write and require confirmation; app and portfolio creation are each limited to 15 calls a day, and app secrets are never returned.

When: The update was announced on October 26, 2026. The server launched on June 30, 2026 and was renamed on August 18, 2026. The tools are rolling out gradually, and Meta's documentation still lists them as not yet available.

Where: On Meta's developer platform at developers.facebook.com, through a remote MCP server reached from AI agents and code editors.

Why: Meta says the change turns a sequence of dashboard visits into a single request. For the marketing community, it extends AI agent write access below campaigns to the apps and Business Portfolios that advertising and WhatsApp integrations depend on, while leaving open questions about rollout timing, use case coverage and how Meta's service provider terms apply to AI vendors.