The OnetSolutions MCP server lets AI agents act on your account — manage VPS instances, domains, billing, and any other resource exposed by the public API — directly from your assistant of choice.Documentation Index
Fetch the complete documentation index at: https://help.onetsolutions.net/llms.txt
Use this file to discover all available pages before exploring further.
Beta — the MCP server is in preview. Endpoints, tool names, and capabilities may evolve. We recommend testing on a non-production organization first.
Prerequisites
- An OnetSolutions account with at least one organization
- An MCP-compatible client (Claude Desktop, Claude Code, Cursor, or any client supporting the Model Context Protocol)
Server endpoint
| URL | https://mcp.onetsolutions.net/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 with PKCE |
| Dynamic Client Registration | Supported (RFC 7591) |
Authentication
The server uses standard OAuth 2.1. You don’t need to create or paste an API key — when you add the server to an MCP client, the client opens a browser, you sign in to OnetSolutions, and you grant access. Tokens are stored by the client and refreshed automatically.Connecting a client
- Claude Desktop
- Claude Code
- Cursor
Add a custom connector
Click Add custom connector, then enter:
- Name:
OnetSolutions - Remote MCP server URL:
https://mcp.onetsolutions.net/mcp
Authenticate
Claude Desktop opens a browser window. Sign in to your OnetSolutions account and approve the requested permissions.
What you can ask
Because the MCP server mirrors the REST API, agents can help with anything covered by the API Reference. A few examples to get you started:- “Reboot my VPS named
web-01.” - “Show me the upcoming renewals on my domains.”
- “Create a snapshot of
db-prodbefore I run the migration.” - “Summarise my last three invoices.”
Revoking access
To disconnect an agent from your account:- Go to Console → Settings → Security (console.onetsolutions.net).
- Find the OAuth application matching your client (e.g.,
Claude Desktop). - Click Revoke.
Troubleshooting
The browser doesn't open during authentication
The browser doesn't open during authentication
Some clients don’t auto-launch a browser. Copy the authorization URL printed in the client logs and open it manually.
`401 Unauthorized` after a long idle period
`401 Unauthorized` after a long idle period
The agent says a tool is missing
The agent says a tool is missing
The MCP server is in beta and the tool catalogue evolves. Restart your client to pick up the latest list, or check the changelog.
An action is refused with `403 Forbidden`
An action is refused with `403 Forbidden`
Your account or the role you used to authenticate does not have permission for that resource. Check your organization role in Console → Organizations.
Related
API Reference
Full list of resources and operations exposed through MCP.
API Keys
Use static API keys instead — useful for CI/CD pipelines or scripts.

