# Make your game multiplayer. We take care of the servers.

You want to play the game with friends. You should be able to focus on what makes that fun while your agent helps with the complicated code and Summer handles the server infrastructure.

- Players
- Your game
- Shared server

Concept · The game brings people together; shared infrastructure connects them.

[Explore the Summer SDK](https://docs.summerengine.com/api-reference/summer-sdk)

## Playing with friends should not become a separate infrastructure project.

A single-player idea can become something very different when another person joins it. Cooperation, rivalry, a shared world or simply messing around together can be the reason the game works.

Getting there has often meant writing networking code, choosing how to run servers and maintaining the systems around them. That work is difficult to justify when you are one person or a small team trying to find the fun in an idea. We built Summer’s multiplayer offering around that problem.

## Your agent can follow the SDK and write the complicated parts.

Summer gives coding agents documentation and platform capabilities they can work with. Describe the experience you want, then use the SDK with your agent to implement the game’s multiplayer behavior.

Your game still has its own rules. A shared adventure, a competitive match and a social space need different behavior. The agent helps connect those rules to the underlying systems; you decide how the experience should feel.

- [Set up your coding agent](https://www.summerengine.com/mcp)
- [Read the Summer SDK](https://docs.summerengine.com/api-reference/summer-sdk)

## Summer takes care of the server infrastructure.

The server side should support the game you are making, rather than become the thing you spend all your time making. Summer brings that infrastructure into the same workflow as the engine and SDK.

The technical documentation is where you and your agent go for setup, supported capabilities and release requirements. The first question here is simpler: what do you want people to be able to do together?

## Spend your attention on the shared experience.

Decide whether players cooperate or compete, what they can change and what makes being together interesting. A small game with a strong shared idea can be more memorable than a large world with nothing meaningful to do in it.

We want individuals and small teams to have more room for that kind of experimentation. Let the infrastructure and agent-assisted code support your art, your world and the moments players will remember.

## Bring real friends into the game while you are making it.

Multiplayer becomes real when other people play it. Share an early build, see how people interact and learn what they want to do that you did not anticipate.

The SDK and testing guide support the technical checks. The players tell you whether the experience is working. Keep improving it and bring them the next version.

- [Test the game locally](https://docs.summerengine.com/api-reference/summer-sdk/testing-your-game-locally)
- [Share it through Summer Games](https://www.summerengine.com/publishing)

## Make room for the people who join.

Playing together means thinking about language, communication and the kind of audience your game welcomes. Explain what people can expect and consider how they will interact, especially when children may be part of the audience.

We want people from different places and backgrounds to be able to have fun together. Clear interfaces and thoughtful social design are part of making that possible.

- [Our approach to safety and context](https://www.summerengine.com/safety)

## Build the multiplayer idea you want to play.

Give your agent the Summer SDK and describe the game. The reference is where the product explanation becomes concrete implementation.

[Open the Summer SDK](https://docs.summerengine.com/api-reference/summer-sdk)

## Keep exploring

- [Publish a game](https://www.summerengine.com/publishing)

- [Safety](https://www.summerengine.com/safety)

- [Game ownership](https://www.summerengine.com/ownership)

[Page map](https://www.summerengine.com/page-map)

[Summer Engine — Terms of service](https://www.summerengine.com/terms)

[Summer Engine — Privacy policy](https://www.summerengine.com/privacy)

[Summer Engine — Refund policy](https://www.summerengine.com/refunds)

[Source and licensing](https://www.summerengine.com/source-status)

Canonical: https://www.summerengine.com/multiplayer

Language: en

[Read as Markdown](https://www.summerengine.com/multiplayer/content.md)