AI assistant via MCP

With the MCP connector of Soll IT Consulting, AI assistants such as Claude, ChatGPT, Cursor or VS Code work directly with your customer account. You ask in plain language, the assistant reads your real data and, if you wish, carries out tasks, but only with the permissions you grant.

1. What the connector does

The connector offers the same functions as our customer API. The assistant only sees the tools that the granted permissions allow.

After signing in, the full tool list with the scope each tool needs is in the customer area under MCP & API → MCP for AI assistants.

2. Requirements

• A customer account with Soll IT Consulting (customer area).
• The permission to manage API tokens. Account administrators have it; they can grant it to other users.
• An AI client that can add MCP servers by URL, for example Claude (web, desktop, mobile), Claude Code, ChatGPT in developer mode, Cursor or VS Code.

3. Setup in Claude

1. In Claude, open Settings → Connectors and choose “Add custom connector”. If the connector is listed in the directory, you can also pick it there.
2. Enter a name (e.g. “Soll IT Consulting”) and the server URL https://api.soll.net/mcp, then choose “Add”.
3. Choose “Connect”. You are sent to our customer area: sign in, select what Claude may read and change and for which divisions, and confirm with your password.
4. Enable the connector in a chat and ask, for example: “Which of my domains expire in the next 60 days?”

You do not need to copy a token. The access appears in the customer area under API tokens as “Connected application”.

4. Other clients

Claude Code

Create a token with the scopes you need under API tokens in the customer area and add the server:

claude mcp add --transport http soll https://api.soll.net/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Check the connection in Claude Code with /mcp.

ChatGPT

Under Settings → Connectors, create a connector with the server URL https://api.soll.net/mcp and OAuth as authentication (developer mode required). Consent works as for Claude, through the customer area.

Cursor, VS Code and your own agents

These clients use an API token in the header Authorization: Bearer …. Ready-made configurations for each client are in the customer area under MCP for AI assistants.

5. Permissions and consent

On the consent page you decide what the assistant may do. The rule is always: the assistant’s rights = granted scopes ∩ your own permissions, and only in the divisions you select.

• On the first consent only read scopes are preselected. With them the assistant can look everything up but change nothing.
• Write and order rights are separate scopes, such as dns:write, domains:order, ssl:order, hosting:deploy or mail:mailboxes. Grant them only when you need them.
• Every new sign-in shows the consent page again, prefilled with your last choice. A new consent fully replaces the previous one.
• Access tokens are valid for one hour, refresh tokens for 90 days. The assistant never receives your password.
• Every access is recorded in your account’s activity log.

6. Examples

Looking things up (read scopes)

• “Which of my domains expire in the next 60 days, and which of them do not renew automatically?”
• “Show me the DNS records of example.com and check whether SPF, DKIM and DMARC are set up correctly.”
• “Which SSL certificates expire soon, and which domains do they cover?”
• “How much does a .de domain cost per year, and is mycompany.de still available?”

Making changes (write scopes)

• “Add an MX record for example.com pointing to mail.example.com with priority 10.”
• “Register mycompany.de for one year if it costs less than 20 euros.” (The assistant shows you the price first.)
• “Order an SSL certificate for www.example.com.”

7. Billable actions and approvals

• Orders (registration, transfer, renewal, SSL certificates, Premium DNS) need the matching order scope and a confirmed quote with its price. Your account’s prices and our terms and conditions apply.
• Orders through the interface are subject to a daily limit per account (rolling 24 hours). We adjust it on request or switch ordering through the interface off entirely.
• DNS changes go through the same approval rules as in the portal. If a change waits for approval (status pending_approval), a person has to approve it in the customer area.
• Tools that replace or delete something are marked as such. Clients such as Claude ask before running them.

8. Portal-only actions

These actions are never available to an assistant, whatever its permissions. It gives you the right page in the customer area instead:

• Managing users, roles, permissions and divisions
• Requesting or viewing auth codes for domain transfers
• Approving or rejecting DNS changes and managing approval rules
• FTP accounts and databases of web hosting

This way an instruction hidden in third-party data (for example in a TXT record or on a monitored website) can neither take over your account nor move a domain away.

9. Limits

• 120 reading and 30 changing calls per minute and access. Beyond that the server answers RATE_LIMITED.
• A single tool result is at most 1 MB. For long lists the assistant pages through the results.
• Files (such as invoice PDFs) are downloaded in the customer area.

10. Revoking access

In the customer area, open MCP & API → API tokens and revoke the “Connected application” or the token. This takes effect immediately: the assistant can no longer read anything, and work of this access that has not started yet is cancelled. You can also disconnect or remove the connector in Claude under Settings → Connectors.

11. Privacy and security

• Your data is kept in our customer area on a server in Germany. The assistant only receives what it retrieves for an answer.
• We do not receive the content of your conversation with the assistant, only the individual tool calls. The conversation is governed by the terms of your AI provider (for example Anthropic).
• What the assistant reads (DNS records, WHOIS data, notes, websites of monitored domains) is passed on explicitly as data, never as instructions. Still check proposed changes before you confirm them.
• Treat API tokens like passwords: store them only in the client configuration, never in chats or shared repositories.

Details: privacy policy of the customer area and privacy policy of the website.

12. Troubleshooting and support

We are happy to help: support@soll.net or via the contact form. Please include your customer number and, if available, the error code. Never send us a token or password.

Last updated: October 2026