Sokie

Sokie hosts MCP servers. Give it an OpenAPI, Swagger or GraphQL spec, and every endpoint becomes a typed tool on a live server at its own address, with sign-in, secrets and logs already set up. This is Sokie's own MCP server, and it lets Claude look after your servers for you. Ask which servers are live and what each one serves, why a server's calls are failing and whether a deploy started it, or how much of the month's usage is left. Claude can also redeploy a server, put it back on an earlier deploy, or rewrite a tool's description so agents call it better. On a server linked to GitHub, a new description arrives as a pull request for you to merge. It runs on your own Sokie API key, so it reaches only the servers that key can, and does only what the key allows. When you connect, a Sokie page asks for the key, and you choose whether Claude may do everything the key allows or only read. Redeploying, restoring and changing a description ask you first. Billing, members, secret values and API keys stay out of reach of any key. Sokie's logs keep each call's tool, result and time, never what was sent or returned. Your agents page lists every agent you connected: hold any of them to reading, or disconnect it. Sokie sells no AI credits: the AI work is your own agent's. Hobby is free with no card, for 3 servers and 50,000 tool calls a month.