Interware MCP

Model Context Protocol servers you can connect an AI assistant to — shared memory, domain lookups, and 3D modelling. This page covers getting an account and wiring the servers up.

What these are

MCP servers give an assistant like Claude a set of tools it can call on your behalf. Each server below is a separate tool set. They are reached over HTTPS and require a sign-in, so your work stays yours: every server keeps each person's data separate.

Getting access

1. Create an account. Register at letsverify.online — one account covers every Interware service. See letsverify.online for managing it.
2. Get the servers you need assigned. An account on its own does not grant access — each server is assigned separately. Ask Roman Mueller for the ones you want.
3. Connect. Follow the setup below. The first connection opens a browser window to sign in; after that it is remembered.

The servers

Connecting

Claude Code

One command per server. -s user makes it available in every project:

claude mcp add -s user --transport http memory   https://memory.mcp.interware.gmbh/mcp
claude mcp add -s user --transport http whois    https://whois.mcp.interware.gmbh/mcp
claude mcp add -s user --transport http openscad https://openscad.mcp.interware.gmbh/mcp

Then run /mcp, pick the server and authorise it. Check status any time with claude mcp list.

Claude Desktop

Use Settings → Connectors → Add custom connector and paste the server URL. Approve the sign-in when the browser opens.

Editing the desktop configuration file by hand does not work for these servers — that file only supports local command-line servers, not remote HTTPS ones.

If something does not work

What you see	What it means
401 / asked to sign in repeatedly	Not signed in, or the session expired. Re-authorise the server in your client.
403 / access denied	You are signed in, but your account has not been granted this server yet. Request access.
“Tool … is not supported”	Your client cached an old tool list. Reconnect the server to refresh it.