LINKSPREED Plans an MCP Server and an API to Create Social Networks in ATRIUM
Today, a person can launch a social network from a single prompt. Next, software and AI agents will be able to do the same, safely and on behalf of the people who own the network.
Albuquerque, NM, USA, November 2026 — LINKSPREED LLC today announced plans to build a Model Context Protocol (MCP) server and a public API for ATRIUM, its platform and environment for building your own social network. Once released, developers, agencies, companies and AI agents will be able to create, configure and manage community platforms and social networks in ATRIUM through code and through agent conversations. This will be in addition to the building experience ATRIUM already offers to people today.
The announcement shows where LINKSPREED sees the next stage of Social Networks as a Service (SNaaS). Until now, the main way to create a network in ATRIUM has been to open the platform and build. The MCP server and the API are meant to make network creation something that other software can request, automate and repeat. The network itself stays under the control of the person or organization that owns it.
Why this announcement matters
Most online communities today live inside platforms owned by someone else. That platform sets the rules, decides who sees what, keeps the data and can change the terms at any time. A community can grow for years on such a platform and still not own anything it has built. LINKSPREED builds tools for a different model, which it calls Web4. In Web4, the people who run a community also own it.
An idea like this only changes things if it is easy to use. The more simply a person or a business can create a network of their own, the more realistic it becomes to choose that path instead of renting space on a large platform. ATRIUM was built around that goal. The planned MCP server and API continue it by making ATRIUM usable not only by people with a browser, but also by the software and AI assistants that people increasingly work with every day.
What ATRIUM is
ATRIUM is the practical side of the Web4 idea. It is a platform and environment where creators, brands, businesses and communities can build and run their own social network. LINKSPREED describes this approach as Social Networks as a Service. Instead of becoming one account among billions on someone else’s platform, an operator launches a network of their own and shapes it to fit their community.
According to the company, a fully functional network can be launched from a single AI prompt in under 60 seconds, with 100% data ownership and 0% platform fees. Launching is only the beginning. Inside Web4 Studio, ATRIUM’s building environment, operators continue to design and develop the network after it goes live.
ATRIUM also gives operators a choice of starting points. LINKSPREED has introduced two new social network templates, called Vibe and Core. Classic remains the default and recommended template and is going through a major new phase of development. The company has said that Classic will receive an MCP server, a plugin system and a series of further updates. The MCP server announced today is therefore part of a direction that LINKSPREED has already set for ATRIUM.
What LINKSPREED plans to build
The ATRIUM MCP server
The Model Context Protocol is an open standard that lets AI assistants and agents connect to tools and services in a structured way. Without a standard like this, every connection between an assistant and a service has to be built by hand. With it, an assistant can learn what a service offers and use it in a predictable way.
An ATRIUM MCP server would give AI assistants a clear and structured way to work with ATRIUM. Instead of describing a social network in text, an assistant could help create a real one. A person could, for example, ask their assistant to set up a network for a local running club. The assistant would then work with ATRIUM directly to create the network and prepare its basic structure. The result would be a working platform that belongs to the person who asked for it.
This changes who can build. Today, creating a network requires someone to open ATRIUM and make a series of decisions. With an MCP server, the person can stay in the tool they already use and describe what they want. The assistant takes care of the steps in between.
The ATRIUM API
The MCP server is designed for agents. The API is designed for developers and for systems that need predictable, repeatable behavior. LINKSPREED plans to offer an interface that lets other applications create and manage community platforms and social networks in ATRIUM.
An API matters most when something has to happen many times, or automatically, or as part of another product. A person can build one network by hand without difficulty. A business that needs a separate network for each of its customers, products or events cannot reasonably do that by hand each time. With an API, a request from another system can create the network, and the developer decides when that request is made and what it asks for.
Two doors into the same platform
The two parts are meant to complement each other. The API gives developers a stable foundation for building ATRIUM into their own products and workflows. The MCP server gives AI agents the same kind of access in a form they can understand and use. Both are meant to serve one purpose: to make the creation of a social network a capability that can be reached from many places, and not only from one screen.
Social Networks as a Service, one step further
Social Networks as a Service starts from a simple observation. Many organizations and individuals need a community, but very few of them want to build and operate the technology behind it. Servers, user management, moderation tools, privacy settings and updates are all necessary, and none of them is the reason someone wants a community in the first place. SNaaS takes that work away. The operator decides what the network is for and who it is for. The platform takes care of the rest.
The planned MCP server and API extend this model in three directions.
The first is automation. When a network can be created through an interface, it can be created by a script, a workflow or a business system. Setting up a community can become one step in a larger process, instead of a separate task that someone has to remember to do.
The second is scale. A single network is simple to manage. A hundred networks, each with its own purpose, its own members and its own rules, are a different challenge. An API is the natural way to handle that.
The third is reach. As more people work through AI assistants, services that cannot be reached by an assistant risk being left out of how people actually work. An MCP server keeps ATRIUM available in that world.
Ownership stays the same in all three directions. A network created through the API or by an agent is still a network that belongs to its operator. The faster and easier creation becomes, the more important it is that control and data ownership do not become weaker.

Building on what already exists
The planned interfaces are not the first time LINKSPREED has opened its platform to other software. Every LINKSPREED community platform already comes with a built-in Web4 API. Among other things, this API provides an OAuth 2.0 provider, which allows a community to act as an identity provider for other services. An organization can let people sign in to a support portal, a learning platform or an internal tool with the same credentials they use in their community.
This earlier work shows the direction of LINKSPREED’s thinking. The existing Web4 API connects a community to the other services around it. The planned ATRIUM API and MCP server go one step further and make the creation and configuration of the community itself available to other software.
Identity and trust when software builds networks
When software and AI agents can create and manage networks, two questions become important. First, who is making the request? Second, what is that requester allowed to do? A social network is a place where people share information and build relationships. Handing that kind of power to an automated system requires a clear answer to both questions.
LINKSPREED is already working on this problem through UIID, its identity platform for people, organizations and autonomous agents. Each UIID identity is built around a private Core ID. Around it, the owner can create aliases, which are separate identities for different contexts that do not reveal the Core ID. UIID supports passkeys, passphrases and passwords. It includes a Trust Center for verification and an Agent Factory for AI agent identities. With UIID v2.16, people can also sign in with a single alias, which creates a session limited to that alias.
UIID is also moving quickly toward the world of agents. Version 2.17 added a new MCP Marketplace, a Solutions MCP server with 27 tools, enforced OAuth PKCE (S256) and Dynamic Client Registration. AI agents can also register their own identity on UIID. All of this points toward a world in which an agent that acts is not anonymous. It has an identity, it belongs to someone, and it can be held to clear limits.
LINKSPREED has not yet published how the ATRIUM MCP server and API will use these building blocks. The principles are nevertheless clear. An agent that creates a network should be identifiable. It should be able to do only what its owner has allowed. Its actions should be easy to review afterward. These principles are consistent with how LINKSPREED already approaches identity, and they are the right starting point for giving software access to something as personal as a community.
Illustrative examples
The following examples show how the planned capabilities could be used. They are illustrations of the idea and not descriptions of finished features.
A creator with an assistant. A photographer wants a private space for students of an online course. Instead of learning a new platform, the photographer tells an AI assistant what the space is for and who should join. The assistant uses the ATRIUM MCP server to create the network and its basic structure. The photographer reviews the result, makes a few changes in Web4 Studio and invites the first students.
An agency with many clients. A digital agency builds community spaces for the brands it works with. Using the planned API, the agency integrates network creation into its own project workflow. When a new client project starts, the workflow creates a new ATRIUM network for that client. Each network is separate, has its own design and its own rules, and belongs to the client it was made for.
A software company with a community inside its product. A company that sells software wants each of its customers to have a place for discussion, questions and feedback. With an API, the company can create that place automatically when a customer signs up, so the community feels like part of the product and does not need a separate setup process.
A brand with campaign communities. A sports brand runs several campaigns each year and wants a dedicated community for each one. With programmatic access, a new network can be created for each campaign and handled in a way that fits the brand’s existing planning process.
The expected impact
For creators and small communities, the barrier to starting gets lower again. If an assistant can set up a network from a conversation, the question changes from whether someone can afford to build a platform to what they want their community to be. That is a much better question to start with.
For brands and businesses, the main change is scale and flexibility. Networks for customers, partners, events, products or internal teams become something a team can create when needed. Each one can have its own rules and its own data, and none of them depends on the policies of a third-party platform.
For agencies and developers, ATRIUM becomes something they can build on. They can offer communities as part of their own services, with their own design and their own workflows, on top of a platform that already takes care of the infrastructure. This opens a way for them to offer community products without having to build and maintain the technology behind them.
For AI agents and their owners, a real, structured way to create and manage communities removes the gap between talking about a network and having one. Combined with an identity for the agent, it also provides a basis for accountability.
For the wider Web4 idea, this is a step toward more independent networks. When creating a community takes minutes and software can do it on request, more people can run a network of their own instead of depending on one large platform. The result is not one giant network but many smaller ones, each following the rules of the people who belong to it. That is the future LINKSPREED is working toward.

Where this fits in the ATRIUM roadmap
The announcement fits into a clear pattern. LINKSPREED has widened the starting choices in ATRIUM with the Vibe and Core templates, confirmed that Classic is receiving major development including an MCP server and a plugin system, and expanded UIID with features for agents and MCP. The planned MCP server and API connect these lines of work. The company is putting its engineering effort into making ATRIUM a platform that people, developers and AI agents can all work with, while ownership and identity stay with the people who use it.
Availability
The ATRIUM MCP server and API are in planning. LINKSPREED has not announced a release date or a final list of features, and details may change as the work progresses. ATRIUM is available today at https://web4.community, where anyone can start building a social network. More information about UIID and its changelog is available at https://uiid.me.
About LINKSPREED
LINKSPREED LLC is a technology company founded in 2025 and headquartered in Albuquerque, New Mexico. It was previously Linkspreed UG. The company is building Web4, a community-based internet in which users and businesses own their data and control their digital destiny. Its products include ATRIUM, its platform for Social Networks as a Service, and UIID, its identity platform for people, organizations and AI agents.