Manage your servers by talking to an AI

Servycore now speaks to AI assistants. With the AI Connector (MCP), Claude, ChatGPT, Cursor or any assistant that supports MCP can work in your panel: ask in plain words, it reads your servers, players, tickets and plugins, and acts once you say yes.

The public API grows with it: most of what the assistant can do is now an API endpoint too, and nothing that worked before changes.

In short

AI Connector (MCP): connect your assistant in one click, pick a project and the access, and talk to your servers.
63 tools: servers, console and chat, restarts, plugins, players, bans and reports, in-game staff and VIP groups, linked accounts, linking commands, automations, the activity log, wipes, support tickets, the blog and notifications.
Safe by design: one project per connection, your role and never more, read only in one tick, and every act players see is confirmed in the chat first.
A bigger API: 35 new endpoints, tokens limited to one project or to reading, and new fields on existing records. No breaking change.

Talk to your servers

Open your assistant and ask, the way you would ask a member of your staff:

"Who got reported the most this week on EU Main, and does their combat log look like cheating?"
"Which plugins are out of date on my servers? Update the ones that are."
"Give 76561198000000077 the VIP group for 30 days on every server."
"Warn the players and restart EU Main in 10 minutes."
"Answer the open tickets about lost kits."
"Write a blog post announcing Thursday's wipe, as a draft."

The assistant finds the right server, player or ticket, tells you exactly what it is about to do, and waits for your yes before anything players can see. Each answer comes with the link to the matching page of your panel, so you can check it there.

Connect it in one minute

The server address is the same for everyone:

https://servycore.io/mcp

Add it to your assistant. In Claude: Customize, Connectors, Add custom connector. In ChatGPT: Apps & Connectors with developer mode. In Claude Code: claude mcp add --transport http servycore https://servycore.io/mcp. Cursor and VS Code take it in their mcp.json.
Sign in to Servycore. Your assistant opens Servycore: pick the project it works in, tick Read only if it should change nothing, and click Allow. There is no key to copy.
Ask.

Each project now has an AI Connector (MCP) page in its menu, with these steps for every assistant and examples of what to ask. A new AI Connector (MCP) page in your account menu lists the assistants you connected, what they did on your servers, and lets you disconnect any of them at once.

Clients that cannot sign in can use an API token made for one project instead.

What it can do

The assistant gets 63 tools, the same actions as your panel:

Servers: every server with its live state (players, FPS, map, next wipe) and its population over time; rename a server, turn it on or off, and resync its linking commands.
Console and chat: read the console and the in-game chat, run a command, write as SERVER or announce on several servers, restart with a countdown or cancel it.
Plugins: what each server runs, search uMod and Codefling, install, update and reload.
Players and moderation: player profiles (time played, kills, reports, linked accounts, notes) and the combat log, kick, ban and mute (timed or for good), lift them, private notes, the F7 reports inbox.
In-game staff and groups: give owner, moderator or VIP groups for a while or for good, and take them back.
Account linking: linked players and their checks, linking commands and their history, retry a failed command, check a Twitch link again, ban a player from linking.
Automations: see them and switch them on or off.
Activity log and wipes: who did what, and the wipe schedule of every server.
Support tickets: read them, answer the player and close them.
Blog: write posts in plain text, saved as drafts until you ask to publish them.
Notifications: the Discord cards and their channels.

The full list, read from the server itself, is on the AI Connector page.

Safe by design

One connection, one project: the one you pick when you allow it. A second project is a second connection.
Your rights, never more: the assistant has your role in the project. A moderator's assistant moderates and runs only the quick console commands of its role; it never runs free commands or changes settings.
Read only in one tick: it can look at everything and change nothing.
It asks first: messages, kicks, bans, commands and restarts are announced and confirmed in the chat before they happen, and they are all in the activity log.
Your secrets stay with Servycore: RCON passwords, host keys and API keys never go through the assistant.
Some things stay in the panel: wipes are read only (no schedule change, no wipe now), and billing, team members, files, the page builder, themes and store settings are not reachable from an assistant.

A bigger API

Most of what the assistant does is also in the REST API, for your own bots and scripts.

Tokens that do only what they should

A token now carries your role in the team: an admin's token administers, a moderator's token moderates, as in the panel.
Create a token for one project, and make it read only: it can read everything and change nothing. Tokens you already have keep working exactly as before.

New endpoints

Who am I: GET /me returns you, the project, its plan and what your role allows.
Notifications: list the Discord cards and turn them on or off.
Game servers: resync linking commands, see the history of every command sent to a server with a retry for failed ones, and change the connection settings with the update endpoint you already use.
Linked players: search by name or any id, and check a Twitch link again.
Rust Control Center: the live state and metrics of each server, console (read and run), chat (read and send), announcements, restarts, plugins (search, install, update, load, reload, unload), players, profiles and combat log, kicks, bans and mutes, notes, F7 reports, in-game staff and groups, bans and wipes of the network.

New fields

Existing records keep every field they had and gain new ones: a dashboard_url pointing to the matching page of your panel, the live Control Center state of each Rust server, the plan and limits of a project, and the search engine title and description of blog posts (which you can now set through the API too).

Refusals are clearer: a request your role does not allow, a read-only token trying to write, or a feature your plan does not include answers with a sentence that says why.

Get started

Open your project, click AI Connector (MCP) in the menu and follow the steps for your assistant. The knowledge base explains every detail.

Questions or ideas? Join us on Discord.