Docs / How-to guides
Manage Sokie from your agent
Connect Sokie's own MCP server with an API key, then check your servers, read logs and redeploy from Claude, ChatGPT or Cursor.
Sokie has its own MCP server, so your agent can look after your servers for you. Ask what's live, why a call failed or how much of the month's usage is left, and have it redeploy or improve a tool's description. It runs on your own API key, so it reaches only the servers that key can, and does only what the key allows.
Connect it
- Make an API key. Start from Agent, which can read everything and change tool descriptions. To let your agent redeploy and restore as well, set Deploys to Read and write.
- Add
https://mcp.sokie.sh/mcpto your agent. Connect an MCP client has the steps for claude.ai, ChatGPT, Claude Code, Cursor and VS Code. - A Sokie page opens and asks for your key. Paste it, then choose what your agent may do: everything, or Read only.
In Claude Code, that's:
claude mcp add --transport http sokie https://mcp.sokie.sh/mcp
Then run /mcp inside Claude Code and choose sokie to connect.
A key works in one workspace, so a connection reaches one workspace. To work in another, connect again with a key from there.
What it can do
| Your agent can | The key needs |
|---|---|
| See your servers and their details | Servers: Read |
| See deploys, and whether one can be restored | Deploys: Read |
| See each server's tools | Tools: Read |
| Read calls, errors and the month's usage | Logs and usage |
| Read the workspace's Activity | Audit trail |
| See secret names, never their values | Secrets: Read |
| Redeploy, or restore an earlier deploy | Deploys: Read and write |
| Change a tool's description | Tools: Read and write |
If the key is missing a permission, the call stops and says which one. A connection on Read only can't change anything, whatever its key allows.
Calls that ask first
Reading runs straight away. Redeploying, restoring and changing a description ask you first. An agent that can ask puts the question in front of you itself. Otherwise it shows a link: open it, paste your key, and choose Allow once or Refuse. Opening a pull request for a description always uses the link. Once you've said yes, your agent makes the same call again. A call waits 10 minutes for your answer.
Changing a description depends on the server. On one linked to a repository, it opens a pull request, and production changes when that merges. On one with no repository, it goes live as soon as you allow it.
What it can't do
Deploying new source, setting a secret and deleting a server stay with the CLI and the app. Billing, members and API keys are out of reach, as they are for any key.
Stop an agent
Your agents page lists the agents you connected. Hold any of them to reading, or disconnect it, and your other agents carry on. To stop them all, revoke the key: every call that uses it is refused from then on.
Read its source
This server runs on Sokie, from a public repository: Abyssinia-Labs/sokie-mcp. You can read what every tool does and what it asks first, and suggest a better description with a pull request.